With the release of Dynamics 365 (online), version 9.0, there are a lot of changes in our developer resources. One of the biggest changes though, is that the Microsoft Dynamics CRM SDK will no longer be available as a download. The new name of the SDK, as it was known will be the Microsoft Dynamics 365 Customer Engagement Developer Guide.
This is probably a request that has been required many times, but recently, one of our customers had a request to open an OnBase document based on some data that was available in a subgrid. Since OnBase has a web to query the database using a query string in their web application, this seemed to be an easy enough solution.
Recenly we received requests from clients and some questions from Dynamics Community members on how to Clone records. Although there are some available solutions out there, and the various possibilities on how to implement this, we would like to demonstrate here one possibly and not to complicated way on how to implement this. This implementation involved using Ribbon Workbench to create the Clone button and a Command that will execute a JavaScript function, which will call an action and execute Plugin/Action code to copy the record.
When choosing to execute webapi functions, that are various methods that are available. The first option of course is to use the default GET, POST and PATCH required to Retrieve and Update data in CRM using the Web API.
This blog post will demonstrate how to create a simple button using Ribbon Workbench which will execute a JavaScript function on the client. In order to do this make sure that you have Ribbon Workbench installed in your CRM environment, or you can use the Ribbon Workbench that is available with XRMToolbox.
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.
