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

[Romannx]

Same issue here - just created a Support Ticket. I will share the information if we get a solution...

[JeroenPeters]

Any updates on this? Experiencing the same error, it's really blocking us.

[MasterShifu]

We had the same issue and tried to do different methods without any success.

Finally, we did an environment reset and restore our managed solution from the source control, then the import solution started to work. When you will restore solution , please be sure that there is no new MS feature about retention policy 

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

We're encountering the same issue, where multiple entities in different solutions now have dependencies on the solution msft_RetentionEnableConfigurations. Looking at the git history of our solution.xml files and the Entity.xml files of the affected entities, the introduction of the dependency issue coincides with the (AFAICT) unexplained removal of a bunch of metadata from the affected entities' Entity.xml files - the same across all affected entities; namely:

• LocalizedNames
• LocalizedCollectionNames
• Descriptions
• ChangeTrackingEnabled
• CanChangeTrackingBeEnabled
• CanChangeHierarchicalRelationship
• IsCustomizable
• IsRenameable
• IsMappable
• CanModifyAuditSettings
• CanModifyMobileVisibility
• CanModifyMobileClientVisibility
• CanModifyMobileClientReadOnly
• CanModifyMobileClientOffline
• CanModifyConnectionSettings
• CanModifyDuplicateDetectionSettings
• CanModifyMailMergeSettings
• CanModifyQueueSettings
• CanCreateAttributes
• CanCreateForms
• CanCreateCharts
• CanCreateViews
• CanModifyAdditionalSettings
• CanEnableSyncToExternalSearchIndex

And the addition of the following:

<ChangeTrackingEnabled>1</ChangeTrackingEnabled>

[mveronesi]

Same issue for me too

Cannot import solution due to missing dependency msft_RetentionEnableConfigurations

Any news from Microsoft? A ticket is necessary?

[cjbarnaby]

Hi @raphib, @JeroenPeters , @mveronesi  - 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). 

[thomaswintour]

Hi guys,

Same issue here from Poltrona Frau S.p.a company with a ticket opened.

None is replying me from Thrusday, probably huge mistake from microsoft developers...

[mveronesi]

Hi @thomaswintour , opened a new ticket yesterday and not yet a contact. 
(I added a link to this thread to my ticket).