Deploying solution to QA environment - missing dependency

[rstbastos]

I'm facing an unusual error/dependency when trying to deploy the Dynamics solution from DEV to QA environment.
It's a small solution with just 8 tables and other components.

The problem I'm facing is about a Business Process Flow that was created.

I added to the solution all the required dependencies to this BPF, but it still gives this strange error when deploying.

Does anyone have any idea about this msft_RetentionEnableConfigurations?
It doesn't appear in the list of solutions, but I can see one reference to it in Solution History. 

Thank you.

[raphib]

Hi

Glad I am not alone, as I am facing the same issue (posted my issue in the wrong forum though: https://powerusers.microsoft.com/t5/Building-Power-Apps/Cannot-import-solution-due-to-missing-depend...).

I hope we can find a solution.

BR Raphael 

[KyleNolteLoD]

We have the same problem since few days.

New Business Process Flow for the default Incident entity. Dependency when pushing the solution:

solution="msft_RetentionEnableConfigurations (1.0.0.0)"

[rstbastos]

After trying so many different approaches, and none working, I decided to update the Solution by removing the dependencies in solutions.xml.
It worked!!!

[powerH]

The solution is being applied by Microsoft and is part of this new feature just announced some weeks ago:

Microsoft Dataverse long term data retention | Microsoft Learn

It should be available in all environments over time, but at least should be rolled out to environments in the same location and with the same update frequency at the same time.

[raphib]

@powerH 

And that's the confusing part: this new solution is also available in the target environment, but without the custom tables of course as they were not available at the time of the installation. So it seems that the managed solution needs somehow information about the custom tables..

[ThierryYenSuin]

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.

[cjbarnaby]

Hi @rstbastos @KyleNolteLoD - 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). 

[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 🙂

[rstbastos]

I opened a ticket with Microsoft as soon as the problem was detected.
Finally, they solved it.
The solution "msft_RetentionEnableConfigurations" was causing problems, but it was not appearing in the list of solutions for that environment.
Then to solve the problem, Microsoft did something for the solution to appear, and I had just to remove the solution from the environment.
Doing this I was able to import my custom solution.