Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I have an issue. Im trying to import my solution from test to production. I have done that a lot of times before. I export the solution from test as managed solution and import again into production environment.
However im getting an error during import:
Display Name: Lock fields based on selection
Detail: This solution cannot be uninstalled because the processtrigger with id 9a799fa2-dc33-e711-8127-005056b617b4 is required by the CaseSolution. Uninstall the CaseSolution and try again.
I don't understand this error. It's a business rule. And the business rule is allready installed in production environment. How can i proceed? I dont care about the business rule, and it can be deleted if this can solve the problem so i can import the solution.
I managed to solve it. I edited the XML customizations file after i have exported the solution. I deleted the problem area with the processtrigger. Then reimported the edited solution without any problem
You are getting this error because of the same Business Rule is referenced in borth of your solutions. Your current solution that you're trying to import and also in CaseSolution solution.
You can fix this in a few different ways really
If you have the CaseSolution on Test, export that solution as well and import that first and then import your other solution and this might fix the issue.
One other option you could consider is to remove the BR from the Solution on Test and export as managed and import on Prod and this should solve the issue.
I can see you had the same issue Last year: community.dynamics.com/.../266945
It might also be worth taking a look at these links
Business Applications communities