Cannot import solution due to missing dependency msft_RetentionEnableConfigurations

[raphib]

Hi

I am using a sandbox environment to set up my solution.

I added some custom entities, which work like they should.
I also included and customized the default power app "Customer Service Hub" with these entities, as we want to start from a basis app.

Now I wanted to import the solution the first time to a prod environment, but I am not able to as I get the message that the import failed due to missing dependencies. I can see my custom entities that should be part of the managed solution "msft_RetentionEnableConfigurations", which I do not know. In the solution history, I can see that this solution has been installed at the weekend, but in BOTH environments.

I also noticed, that the checkbox "Enable Long Term Data Retention" is checked for several tables in the sandbox environment, but not in the production environment (eg. account, case etc.), including my custom entities.

What am I missing?

I do not get these dependency errors when I try to import it to another sandbox I created last week and imported the solution right after the creation. But I get other messages for missing web resources and custom controls (Who knows whom, see screenshot attached). I assume this is because the Sales Hub App is not up to date / is on an older version than in the sandbox environment I set up the main solution. How can I force the update so the apps will have the same version?

BR Raphael

[mabou63]

Workaround: 

Extract the managed solution that you extracted from your Dev environment. 

Open the Solution.XML file using Notepad. 

Search for tag <MissingDependency>

.......
</MissingDependency>

for all the lines related to this error and delete the section (from the start of the tag till the end of the tag). In the error list, I got around 30 missing lines report. I deleted all these sections. 

Save the solution.xml 

Build a new ZIP file including all the extracted files. 

Import this new solution. 

[raphib]

Thank you all for your help and investigation! I also opened a ticket, but did not get a feedback yet.

Nevertheless, Microsoft published a statement that you can see in the Power Platform Admin center or with this URL (https://portal.office.com/adminportal/home/?ref=MessageCenter/:/messages/MC556907😞

Message Summary

We detected that custom solution functionality may be impacted on your production and non-production environments.

Description:
We identified that a code misconfiguration was introduced following a recent service update that contained a new long-term retention feature. This misconfiguration may impact your ability to import custom solutions and modify custom solutions with a custom entity dependency. Non-production environments are affected by this incident, production environments will only be affected when exporting custom solutions from non-production to production.

We have validated mitigation and will be deploying the fix as part of the 9.2.23054 service update.

For more information on service updates and when the fix will reach your region, visit the Released versions of Microsoft Dataverse page.

Action Needed:
To prevent impact, please avoid importing custom solutions to your production environment or modifying custom solutions with a custom entity dependency until deployment of the code fix has concluded. This message will be updated once the deployment is complete.

Please contact Microsoft Support and reference ticket ICM389742188 if you need further assistance.

So it seems that it will be fixed automatically 🙂

[nelson88]

I have the same issue 😕

[raphib · Accepted solution]

@nelson88 as mentioned here: https://powerusers.microsoft.com/t5/Microsoft-Dataverse/Deploying-solution-to-QA-environment-missing...

just open a Microsoft ticket, and send them a link to these two topics. As mentioned before, it will be automatically solved in the next few weeks by a service update, but if you need to fix it asap, try via Microsoft support.

I also opened a ticket and they enabled the solution, which can be deleted afterwards.