Members Count field not getting updated on converting Dynamic Marketing List to Static Marketing List – issue in Dynamics 365 July 2017 Update


While trying out few things in July 2017 update of Dynamics 365, we encountered a strange issue.

The members count field was properly in case of Static Marketing List, however, while converting the Dynamic Marketing List to Static (using Copy To Static), this field was not getting populated.

And also, the field was getting unlocked in case of Update Form for both Static and Dynamic Marketing list, unlike earlier version where this field was always locked on Form.

The field properly calculating count and locked in case of earlier versions.

Hope it helps..

A validation error occurred. The value of ‘membercount’ on record of type ‘list’ is outside the valid range exception in Dynamics 365 (CRM)


We were getting the below error while trying to delete one of the marketing list members from a static marketing list.

This occurs if the Members Count field has value 0 in it, even if there are members associated to it. (due to some exception)

Updating that field to correct value fixes this issue (customize the form to add the field on form). and we can then delete the members from it.

Hope it helps..

“Does not contain data” filter in Advanced Find in Dynamics 365 July 2017 Update


With July 2017 Update in Dynamics 365, Advanced Find view now supports Does Not Contain Data filter for related record.

So basically, we can now write a query like “Find all the lead records which doesn’t contain any related task”. However, we cannot define any filter conditions for the related record though.

The other interesting thing that we observed that in the case of N – N relationships it throws exception.

For e.g. if we want to find all the contacts that are not associated to marketing list

We get the following exception à

Also,

The does not contain data filter isn’t available while defining marketing list members in marketing list.

Hope it helps..

Fixed – Incorrect attribute value type System.String in Dynamics 365 (CRM)


We were getting the below error while creating an entity record through a C# Console Application.

This occurred because the code was trying to set string value to one of the decimal type field.

Parsing the string value to decimal and then setting it fixed it.

Hope it helps

MultiSelect Option Set in Dynamics 365


Also read – Limitations

https://nishantrana.me/2018/04/27/limitations-of-multi-select-option-sets-in-dynamics-365-ce/

With July 2017 update, we can now finally create multi-select option set in Dynamics 365.

We can also use Existing Global Option Set while defining our Multi Select Option set.

This is how control looks within the form.

Within Advanced Find View

We can use the existing option set client-side methods on Multi Select Option Set.

https://msdn.microsoft.com/en-us/library/gg334409.aspx#Anchor_1

getSelectedOption() – for new_weekday multiselect option-set with value Thursday and Friday selected –

Hope it helps..

Unified Interface – Dynamics 365


Unified Interface – Dynamics 365 July 2017 Update

Matthew Webb's avatarMatthew Webb's Dynamics 365 Blog

This is my second blog relating to new features with the Spring Release of Dynamics 365 (July 2017).

Please note any pictures are taken from the Dynamics 365 Preview Executive Briefing which can be found at the following link (by CRM Innovation). All information contained in this blog is a summary of two presentations across the three days of the briefing – there is still a lot of unknowns at this point so please bear with me!

Accessing Dynamics 365 – the current Interfaces

Dynamics 365 as we currently know it – Microsoft allows us to access our Dynamics 365 data via the following (out of the box) methods:

View original post 835 more words