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.
The preview version of SSDT for Visual Studio 2017 (15.3.0 preview) is now available. This release introduces a standalone web installation experience for SQL Server Database, Analysis Services, Reporting Services, and Integration Services projects in Visual Studio 2017 15.3 or later.
On August 24, Microsoft release the Microsoft Dynamics 365 Customer Engagement Portals Source Code. The download contains the self-hosted Portals which are available for Dynamics 365 On-Premise. This will allow your to customize the portals per your requirements and deploy then to Dynamics 365 (On-Premise) as well as Dynamics 365 (Online).
Recently somebody asked, why does the KB Article home page view does not have an option to Email a Link to multiple records like a lot of the other entities do, In looking at the Ribbon Xml, we notice that is true and there is no Email a Link split button to display that, so we were looking at the best approach to implement this.
The purpose of the original post (Part I), was to demonstrate how to add a button to a read only entity record, in order to create a new child record. This is a complex scenario that requires a lot of customization to the Ribbon/Command Bar. A much easier solution exists, if all you are looking for is to add the capability of adding child records to a read only record, as we discussed in the first part of this article.
Recently someone asked if there is a way to add a child record to a Contract Line (contractdetail) entity for a record that has already been saved (and is set to read only/existing). We found that there are two parts to this solution. The first part of this article will focus on creating a button on the Contract Line entity, and calling logic to create a new record.