Unanswered

Solution import has missing dependencies related to a Dynamics 365 add-in app I did not download

(3) Share

Report

Posted on by Carls Sagan

When exporting my unmanaged solution called "arb_customComponents" from a development environment into a production environment as managed, my import fails because of missing dependencies involving solutions and packages i did not create or install from the AppSource marketplace.

It is looking for objects like leads and opportunities that are being used in an application called Dynamics 365 Core Sales (msdynce_Sales). These missing dependencies related to an add-in app (msdyn_activitymapping and msdyn_SalesCopilot) not included in the solution. Appears to be automatically added by Microsoft during an update.
I believe these are Microsoft products that are related to copilot for sales. I have experienced something similar in the past where Microsoft would add packages or solutions to my tenant environments from an update or feature change and this feels similar.

I use power platform build tools and the xml exception message returned when the import from my D365 Development environment into my D365 Production environment The applicationName property in the xml exception is for "Dynamics 365 Core Sales" and the appName property is for msdynce_Sales, both of which I did not install myself. The components seem to be tables for leads, opportunities, etc.

Snippet of power platform build tools error message

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Michael E. Gernaey 53,963 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @Carls Sagan

Are you able to go into your solution, and have it tell you what Dependencies you have please. Also, you should be able to check individual parts of your solution to see what they are depending on, so we can figure out for sure what's causing that. It does make sense that its CoPilot.

When you look at the items in your Solution and click the ... you should be able to click Advanced and Show Dependencies for all of them.

Try to narrow down for sure where/what is using that.

For your Apps

Was this reply helpful? Yes No
CS-22051916-0 4 on at

Like (0)

Report
Copy link

Link copied!
Update 05/22/25 at 1615 hrs:

So there are two ways we are handling this. One short term way and one long term.
Sort term to have the import succeed if you're in an emergency like we were.

msdyn_SalesCopilot components will have to be removed from the .xml export.

To do this export the affected solution.

Open the zip go to the solution.xml file.

Find and Delete any dependencies associated with “msdyn_SalesCopilot” between the <missingDependency> brackets.

Long term
You need to contact your Microsoft representative through a support ticket to have them push the MS solution components to your environment.

Original post

Our agency has the same error as we move through our ALM cycle. It is preventing a critical release and there is zero reference to it in it in the updates under the resources section. The Link actually takes us to another error message. (super helpful). We've had continual issues with the Microsoft updates under Resources/Dynamics 365 apps. The product team is unresponsive. There is no information about what is in the release, why some are automatic in certain environments or not in others, when the update was made available or what tables will be put into the environment. It has been a crap shoot from MS about these background updates.

Was this reply helpful? Yes No