Resolving Power Pages dependencies during solution migration

Migrating solutions that contain Power Pages sites can sometimes be a challenging task, especially when you encounter the dreaded “Missing dependencies” error. This error typically occurs when you try to import an existing solution from one environment into another, and in this scenario, it indicates that certain managed solution components from Microsoft are missing. In this blog post, we’ll explore a potential Microsoft cause of this issue and provide a step-by-step guide to resolve it.

Understanding the Issue

When you attempt to import a solution and receive a “Missing dependencies” error, it usually means that the target environment lacks certain components that are present in the source environment. In the case being addressed in this post, the missing managed solutions are “MicrosoftPortalBase”, “MicrosoftIdentity”, and “MicrosoftPortalDependencies”. These solutions are essential for the proper functioning of Power Pages sites.

The Unconventional Solution

Interestingly, the workaround for this issue involves installing a fake customer service template site in the production environment temporarily. This might sound unusual, but it effectively resolves the missing Microsoft Power Pages and CustomerService dependencies. Here’s how you can do it:

1. Navigate to the Customer Portal Setup Guide: Follow the steps outlined in the Install, set up, and update the Customer portal – Supply Chain Management | Dynamics 365 | Microsoft Learn to install a fake customer service site. This guide provides detailed instructions on setting up the site, which will include the necessary managed solutions.
2. Install the Fake Customer Service Site: By installing the fake customer service site, you will, under the hood, be automatically install the missing managed solution components (“MicrosoftPortalBase”, “MicrosoftIdentity”, and “MicrosoftPortalDependencies”) in your production environment.
3. Import Your Solution: Once the fake customer service site is Synced/Published via Power Pages, you can proceed with importing your solution. The previously missing dependencies should now be resolved, allowing the import to complete successfully.
4. Remove the Fake Customer Service Site: After successfully importing your solution, and verifying your custom site operating, you can remove the fake customer service site from your production environment leaving only your custom Power Pages site behind. This step ensures that your environment remains clean and only contains the necessary sites.

Conclusion

Migrating solutions that contain Power Pages sites can be tricky, especially those made during the “Basic” vs “Enhanced” data model rollout, but understanding the root cause of the “Missing dependencies” error and knowing the unconventional workaround can save you a lot of time and frustration. By temporarily installing a fake customer service site via the MSFT provided template, you can ensure that all necessary managed solutions are present in your target environment, allowing for a smooth and successful migration.

If you have any questions or need further assistance, feel free to reach out. Happy migrating!

Get in touch with the Beringer Team today!

At Beringer, we realize that even the small details, can have a big impact, when things unexpectedly go wrong during a solution migration. Our team would be happy to help with any questions you have on Power Platform – no matter how small or large. Give us a call today, to see how our team of experts can help your business keep up with the latest advancements in Microsoft applications and features!

Beringer Technology Group, a Microsoft Solutions Partner for Business Applications, specializing in Microsoft Dynamics 365 and CRM for Distribution also provides expert Managed IT Services, Backup and Disaster Recovery, Cloud Based Computing, Email Security Implementation and Training, Unified Communication Solutions, and Cybersecurity Risk Assessments.