DEV Community

Cover image for Dynamics 365 Solution Import Error: Missing Dependency from Sales App – How I Resolved It
Nikhil Sarpatwari
Nikhil Sarpatwari

Posted on

Dynamics 365 Solution Import Error: Missing Dependency from Sales App – How I Resolved It

#powerplatform #alm #dynamicssales

During a recent managed solution deployment in a Dynamics 365 CE sales environment, I encountered an unexpected import failure due to a missing dependency. The solution didn’t appear to rely on anything custom or uncommon, yet the deployment threw this error.

Error Details

Solution manifest import: FAILURE: The following solution cannot be imported. Some dependencies are missing.

Missing dependency:

<Required type="61" schemaName="Sales/_imgs/SiteMap/AICommandCenterIcon.svg" ... solution="msdyn_SalesApp (9.0.25065.10005)"> <package appName="msdynce_SalesInsights" version="9.0.25065.10002" ... applicationName="Dynamics Sales Embedded Package" /> ... Error: The async operation completed with a statuscode of Failed.
Enter fullscreen mode Exit fullscreen mode

This was triggered using the Power Platform CLI (PAC CLI). The missing dependency pointed to a Sales Hub sitemap icon introduced in a newer version of the msdyn_SalesApp.

Root Cause

The solution included references to the Sales Hub sitemap. Although the solution itself did not directly use this icon, the sitemap referenced a file that existed only in a newer version of the Dynamics 365 Sales app. This led to an implicit dependency failure during import.

The source environment had a newer version of the msdyn_SalesApp that included these updated assets, while the target environment did not.

Error description

Resolution Steps

To fix the issue:

  1. Open Power Platform Admin Center
  2. Go to Environments > select your target environment
  3. Navigate to Resources > Dynamics 365 apps
  4. Locate Dynamics 365 Sales and verify its version
  5. Compare this with the version in your source environment
  6. If the target version is older, choose Update
  7. After the update completes, reattempt the solution import

Key Takeaways

  • Always ensure that first-party Dynamics 365 apps like Sales, Customer Service, or Field Service are on the same version in both source and target environments.
  • Even if your solution does not directly reference specific components, app modules or sitemaps may contain implicit dependencies.
  • Keeping app versions aligned helps avoid import failures caused by missing or outdated assets.
  • Reviewing app versions in Power Platform Admin Center should be part of your deployment checklist.

Final Thoughts

Solution import errors related to first-party app dependencies can be hard to trace if you’re not expecting them. In this case, a simple sitemap reference to a missing SVG file blocked deployment. Matching the Dynamics 365 app versions across environments resolved the issue without needing to change the solution itself.

Top comments (0)