Installation order for Solutions (Patches) in Dynamics 365 Customer Engagement – Nishant Rana’s Weblog
Let us take see a simple example of how the installation order of solution and patch works in case of Dynamics 365 CE.
Suppose we have a Solution A with only Account Number field with display name renamed to Account Number from Solution A.
Now this solution is exported as managed and imported into the target environment
Now let us create a new solution which renames this field as “Account Number from Solution B” and then import this as managed in the target environment.
So as…
Continue Reading Nishant Rana’s Article on their blog
Installation order for Solutions (Patches) in Dynamics 365 Customer Engagement – Nishant Rana’s Weblog
Blog Syndicated with Nishant Rana’s Permission
More About This Author
Array
- Dyn365CE30 April 2024Use Geolocation Settings for Location Tracking and Auditing – Dynamics 365 Field Service
- Dyn365CE29 April 2024Fix the trigger – Microsoft.OData.ODataException: A binary operator with incompatible types was detected. Found operand types ‘Edm.Guid’ and ‘Edm.String’ for operator kind ‘Equal’ (Power Automate / Dataverse)
- Dyn365CE23 April 2024Portal does not load and displays “Server Error” or shows “Getting set up.. This might take a while” message -Portal Startup Issue (PowerApps Portal)
- Dyn365CE22 April 2024Versioning and Drafts for Solution-based Cloud Flows – Power Automate