Missing dependencies when importing a dev solution to prod - leadhygine

(0) Share

Report

Posted on by MimmiIngrid

We cant import our solution due to the error message below, any suggestions?....

1. MissingDependences: Required type=\"1\"

schemaName= msdyn_duplicatedetectionpluginrun

displayName=Duplicate Detection Plugin Run

solution= msdyn_leadhygiene

package: msdynce_SalesInsightsAnchor (9.0.22015.10011)

2. schemaName:lead\" displayName=\"Lead /></MissingDependency><MissingDependency><Required type=\"1\" schemaName=\"msdyn_duplicateleadmapping\" displayName=\"Duplicate Lead Mapping\" solution=\"msdyn_leadhygiene

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (11)

Answers (1)

moko33 35 on at

Like (0)

Report

Have exactly the same issue. Cannot import our managed Solution because there are these two new dependencies.
Reason is, that the whole Lead entity is part of our managed solution. And the target system doesn't have the msdyn_leadhygiene installed yet.

So should we wait for MS to roll out updates across all systems or should we remove Lead entity from our Solution and readd all custoized components (if possible)?

Was this reply helpful? Yes No
1__Ben 2 on at

Like (0)

Report

I've discovered this issue today too.

I will share my experience:

Export solution from Environment A - this environment is not on the latest wave release

Import solution to Environment B - Solution import fails - This environment is on the latest wave release

Import solution to Environment C - Solution import fails - This environment is on the latest wave release

Import solution to Environment D - Solution import success - This environment is not on the latest wave release.

I have not yet updated the original (Development System) but I suspect if this is updated and then the export is re-done this should fix the issue.

Was this reply helpful? Yes No
meelamri 468 on at

Like (0)

Report

Hi,

I had a very similar issue recently. After contacting Microsoft Support, it turned out that they updated the solution "msdyn_Conversation_Intelligence" only in DEV instance. Microsoft have launched an update on that solution during the weekend in EU region. Some environments were not updated. The solution is to ask Microsoft to align the version of this solution in other environments...

Those who had some troubles to import a #dataverse solution into production today raise their hand ...🤚

"The solution import fails due to missing components. The error message refers to a Microsoft solution: "msdyn_Conversation_Intelligence". 👇👇
— Melamri 🇲🇦 (@Meelamri1) February 15, 2022

Was this reply helpful? Yes No
piyushnandanwar 8 on at

Like (0)

Report

@melamri
Hi,

I am experiencing similar error (dependency on msdyn_leadhygiene and masyn_conversation_intelligence ) while solution import to fresh environment. However, I noticed I do not have these solutions either in source where I am exporting the managed solution from.
What could be the way forward? To talk to MS support?

Was this reply helpful? Yes No
meelamri 468 on at

Like (0)

Report

Hi,
You will need to open a ticket support and ask them to align the version of this solution in other environments.

Was this reply helpful? Yes No
moko33 35 on at

Like (0)

Report

For msdyn_leadhygiene my way to solve it was removing the Lead entity from our managed solution and only adding the components of the Lead entity which were really needed (which are usually those that have an active layer).

Was this reply helpful? Yes No
piyushnandanwar 8 on at

Like (1)

Report

I got in touch with MS support and got it resolved. They aligned the version which resolved this issue.

Was this reply helpful? Yes No
Verified answer

MimmiIngrid 17 on at

Like (1)

Report

sorry for late reply, I found an update in admin center connected to our marketing module. I updated it and then it worked 🙂

Was this reply helpful? Yes No
meelamri 468 on at

Like (0)

Report

Hi,

Thanks for your feedback. In my case, I had a new issue related to 'msdyn_Conversation_Intelligence' while installing a solution in production.
Apparently, the 'msdyn_Conversation_Intelligence' solution causes a lot of issues...

Have a nice day, everyone !!

Was this reply helpful? Yes No
Rahul Rathore 8 on at

Like (0)

Report

Hi We get this error when we import the solution in prod and we cant find the solution in solution how we fix this issue?
We try to create a new solution to give an error solution already existing.

Was this reply helpful? Yes No