Blogs September 2017

Many times we are asked by our customers to disable Bulk Edit to certain users or groups of users/teams within the system. That requirement is pretty straight forward and can easily be understood. The resolution to this of course is also easy, and can easily be accomplished by changed the Bulk Edit privilege for a particular security role. What happens though when the requirement is to disable bulk edit from a user only on a particular entity. This becomes a little more complicated.

Starting with the upcoming release of the July 2017 update for Dynamics 365 (online), Microsoft will require connections to utilize TLS 1.2 (or better) security. This aligns with updated Microsoft and industry security policies and best practices, and certain actions might be required to maintain connectivity to the Dynamics 365 Customer Engagement applications.

In a recent email from Microsoft Insider Program, Microsoft provided an advanced notice that the plan is to deploy the July 2017 Update for Dynamics 365 to General Availability (GA) in the first week of October 2017. The released version of the product will be available soon after, and a 30-day trial of the new release will be available via the Microsoft Dynamics web site.

Microsoft Dynamics CRM and Microsoft Dynamics 365 provide indicators throughout the application to help us know whether the records that we are seeking are available to work on or have already been deactivated (resolved, won, cancelled or no longer needed). These indicators are set using the Status and Status Reason fields, which are also linked together.

Brite Global released their AutoNumber solution in 2011 together with the release of Microsoft Dynamics CRM 2011. At the time the solution provided simple autonumbering with the ability to create AutoNumber on numeric or text fields with additional formatting settings. As Dynamics CRM and the releases evolved, the AutoNumber solution options continued to evolve and we are now providing various AutoNumbering options, including getting data from Optionsets, Lookups and related entities to generate the numbering sequences.

We recently had a requirement to enable us to see the Date Won field of the Quote entity which appears when an Order is created (Quote is closed as Won), and although that field can be seen when the Order is created, the field was not located.