web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Moving a solution with a reference to an ID in a process

(0) ShareShare
ReportReport
Posted on by 25

I have a solution I'm attempting to move between environments. This solution contains a process which assigns as connection between entities.

When attempting to import the solution I run into an error with missing dependencies

Solution import Failed. Error: Solution manifest import: FAILURE: The following solution cannot be imported: awesomeSolution. Some dependencies are missing. The missing dependencies are : 
<MissingDependencies>
    <MissingDependency>
        <Required key="509" type="63" displayName="Prospect" solution="Active" id="{69cae6e1-a16d-e911-a818-000d3a1cac04}" />
        <Dependent key="510" type="29" displayName="Agency's Student - Create connection" id="{e9fd9819-190c-495d-b023-06cb9c49dda7}" />
    </MissingDependency>
    <MissingDependency>
        <Required key="511" type="63" displayName="Agency" solution="Active" id="{21eb17ba-a16d-e911-a818-000d3a1cac04}" />
        <Dependent key="510" type="29" displayName="Agency's Student - Create connection" id="{e9fd9819-190c-495d-b023-06cb9c49dda7}" />
    </MissingDependency>
</MissingDependencies> 


Fair enough, the connection roles Prospect and Agency don't exist in the production system. So I spun up a little console app and injected the two roles which were missing in the destination environment with the correct ids.

...
var agency = new Entity("connectionrole");
agency.Id = agencyId; //guid from error
agency["connectionroleid"] = agencyId; //guid from error
agency["name"] = "Agency";
agency["category"] = new OptionSetValue(1);
context.AddObject(agency);
context.SaveChanges();
...


I confirmed that the new records actually exist and that they have the appropriate IDs. However I'm still getting the same import errors. Is there some way to have the solution import find those records? Is there some step in creating the records that maybe I'm missing? I'm hoping that there is a solution here which avoids me having to write a custom workflow task which looks up the connection role and does the association. It just feels like I can't be the only person who has ever moved a solution from environment to environment.

*This post is locked for comments

I have the same question (0)
  • Martin Donnelly Profile Picture
    1,030 on at

    have you tried copying the dependencies from the source using the DataMigrationUtility that comes with the SDK download?

  • Simon Timms Profile Picture
    25 on at

    I have tried that also. I'm not keen on using copying between because it means I have to have source environments and not just packages and scripts. It also makes my deployments less granular because everything gets copied over.

  • Verified answer
    Dynamics Objects 365 Profile Picture
    550 on at

    Well, I faced a similar issue when I had to move "some parts" of an entity into a fresh instance.

    I achieved that by adding entity metadata into the solution and then removing all the <missing dependency> tag. ( Do keep the parent <missing dependencies> tag)

    Give it a try.

  • Simon Timms Profile Picture
    25 on at

    I wasn't sure exactly what you meant by adding the entity metadata to the solution. However I did remove the two entries I had in the solution.xml and the import worked correctly and the process looks like it was correctly hooked up. So that "solves" it but it adds a ton of cognitive load on the team that every time they pull the solution they need to remember to remove these two seemingly random entries.

  • Dynamics365 Rocker Profile Picture
    7,755 on at

    Are you able to import solution with out process?

    Add all dependencies in solution.

    Solution never failed due to process. If there is GUID refrence in process then it will be imported as draft but it won't stop solution to import.

  • Simon Timms Profile Picture
    25 on at

    Yes I was able to import the solution without the process. The unsatisfied missing dependency in the solution.xml was blocking the import as a managed solution.  As I mentioned removing that did allow for the import but at the cost of now having to maintain the knowledge that we need to manually remove the elements on every subsequent build. If this truly is the only solution then I'll probably start building up a series of XML transforms which run in the build pipeline.

  • Suggested answer
    Dynamics Objects 365 Profile Picture
    550 on at

    Glad it helped. For our scenario, it was a one time activity.

    If you are planning further subsequent deployments, which will "Always" include the component with missing dependency, then yes this activity will be an extra overhead.

    If possible, use "Clone a Patch" feature to move the changes. By using this , you may probably avoid that one Component with missing dependencies (Most of the times).

    I would also suggest to figure out a way to clean this mess.

    Cheers!!

  • Simon Timms Profile Picture
    25 on at

    I'm intrigued by your suggestion to clean the mess. In my mind this isn't a mess - it is simply how one would go about creating solutions which can be encapsulated and deployed to any environment. I find a lot of the mindset around dynamics is set up for organizations who have just 2 or 3 environments and not for software vendors attempting to set up build processes for deployment to customers. If you have some suggestions I'd love to hear about them.

  • Dynamics Objects 365 Profile Picture
    550 on at

    I am glad my suggestion raised some sort of curiosity. I have been in this "messy" situation.

    Well there is no straight forward answer for a perfect deployment process, but still, have a look at this white paper - www.microsoft.com/.../details.aspx

    Keep spreading the Joy ! ;)

    Cheers!!

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
ScottDurow Profile Picture

ScottDurow 2

#2
GJones Profile Picture

GJones 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans