As a part of the requirement, I am moving the changes made in one environment (Sandbox) to another environment (UAT).
What I did,
Created a new solution and made the changes to the system in this solution (One of the changes being 'creation of a new Business Process Flow - Lead To Invoice).
Published all customizations and exported it as an unmanaged solution.
Then, I navigate to the UAT environment, and imported the above solution.
Import failed because of the following components are missing from the system and not included in the solution.
please check the below images.
I checked the BPF entity, Lead To Invoice, in Sandbox environment, there were no required components to be added to it.
I am unable to understand what the Managed Solution 'msft_RetentionEnableConfigurations (1.0.0.0)' means.
Can someone throw some light on this and also if I can get to know how to solve this import issue, it will be really helpful.
Any response is much appreciated.
Thank you
Dicha - I logged a ticket with MSFT and was informed that this was a known issue, which requires MSFT support to run a mitigation script on the source environment (and the target environment, if one exists - in our case, the target environment is created and then deleted as part of a CI/CD pipeline, so this didn't apply).
I would suggest you log a ticket with MSFT informing them that you are unable to import your solution due to missing dependencies on the first-party solution msft_RetentionEnableConfigurations, and provide them with the source environment and target environment URLs (as applicable).
Hello Dicha
It looks there are other components depends on your solution which you have not exported , if you do not want to carry in other environments, simply remove it from your unmanaged solution.
Check through customization.xml or solution.xml as well to check dependency of this solution.
Please mark if this works for you.
Hello,
I had the same error and I solved it by manually creating the entity in the target environment with the same Name and Primary field and nothing else, just an empty entity... then importing the solution that was having dependency problem.
Once the entity exists in the target environment, you should be able to import the solution.
I think MS installed a patch that is causing these errors. In the meantime, this should work.
Good luck.
Thierry.
Hi Dicha,
Hope you are well.
From the screenshot, it seems that you have missed dependencies for solution, we can add missing components into solution to resolve the issue.
It is better to import from Power Apps, from that we can exactly know dependencies missed in which solutions.
Click Show dependencies to see the missing component if there is something wrong with solution.
Add missing components into solution and import again.
Here is a reference link: Import of solution fails due to missing components - Dynamics 365 Sales | Microsoft Learn
A related community thread where some options were being talked about: Solution import failed , missing dependencies - Dynamics 365 Sales Forum Community Forum
Best Regards,
Sayen Zhang
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156