‘Solution Failed to Import’
If you’ve ever tried to import an updated solution in Dataverse only to run into frustrating dependency conflicts, you’re not alone. In many scenarios, these conflicts occur when certain components are locked into place by other parts of your system. Dependency Management serves an incredibly important role in ensuring Developers can’t burn down the building accidentally, but it also can be overzealous in not letting go of things that are meant to be let go of.
Until recently, getting hit with the above error message meant painfully going through the solution layers to figure out how to roll-back / revert the change and pray that it’d be reconciled on import. That is, until I ran into the feature to ‘remove dependency’ that didn’t require me to do anything besides re-import the solution. It’s really rather simple!
Example – Removing a Form from a Model-Driven App
In this case, the error was related to me trying to delete a form from a Model-Driven app and the dependency was being stubborn on the production environment.
First, you need to navigate to the target environment and identify the component that is causing the conflict.
Navigate to the component > click the ellipsis > Advanced > Show Dependencies. This will pull up the dependency screen where you can see what is blocking deletion, as well as what components it references. Identify the component blocking deletion or currently in use, and click the ellipsis.
You’ll now see an option to ‘remove dependency’.
Click the option to open a pop-up that confirms the component stays intact and removes only the dependency block. Once you confirm, you’ll see that it is no longer in the dependency list. At this point, you can try importing the solution again and it should work!
There is also an ‘open documentation’ link which funny enough, doesn’t mention anything about this feature (yet). Removing dependencies overview (Microsoft Dataverse) – Power Platform | Microsoft Learn
0 Comments