Disclaimer for Ben Vollmer: We love field service. If it was food, we would eat it at every meal.
That out of the way, sometimes you find yourself with solutions in your environment that you don’t need. Maybe you set up a trial of Dynamics 365 and you accidentally chose the “I want it all” option and wound up with a bunch of managed solutions in your environment. This can be bad, as any solution you develop in this environment will have a dependency on these solutions, requiring you to install them before you can move your solution.
If you find yourself in this situation, you will want to remove these solutions from your environment. But that can be challenging, as many of these apps install multiple solutions in your environment.
In this video tip, I show you how to determine the order in which these solutions should be removed and then successfully uninstall field service from a Dynamics 365 environment.
I did see the Skyline Consulting blog on this topic, but it is outdated as the solutions are now different.
Tips for uninstalling first-party apps:
- Sort solutions in descending order–that generally tells you which solutions to remove first
- Remove patch solutions before removing the main solutions
- When in doubt, go to the components list in classic solution manager, select one of the entities in the app and click “solution layers.” This gives you information about the layers, remove the higher layers first.
- When you hit a dependency notice when deleting the solution, remove the dependency, then delete the solution.
The following is the order of operations from the video:
- Remove Geofencing SDK step
- remove msdyn_/Utils/head.js from user form
- remove msdyn_/Utils/head1.0.3.js from contact form