Microsoft Dynamics 365 | Integration, Dataverse...

Error: dependent component Workflow does not exist, but workflows do exist in the solution

(0) Share

Report

Posted on by anthony56

We are trying to import an update to a D365 managed solution to our UAT environment, and the import failed. The import last week of that exact same solution zip file worked fine in a lower environment. But, today in UAT, the failure says "the dependent component Workflow (id=x) does not exist. Failure trying to associate with Workflow (id=y) as a dependency. Missing dependency lookup type = PrimaryKeyLookup". Both workflows (id=x and id=y) are present in the solution (and have been for many years), and workflow "x" is of type "Process (Action)", while workflow "y" is of type "Process (Workflow)". Any ideas on what could be going on? Any suggestions on how to resolve the issue?

Categories:

Dynamics 365 general

Power Platform integration

I have the same question (0)

All responses (3)

Answers (0)

Suggested answer

ManoVerse 884 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
First , can you please check the workflow id's in both the environment , you can check easily in metadata browser in xrmtoolbox , this usually happens if your UAT skipped any intermediate version , might have someone recreated the workflow in source. check below if that will point out something which you might missed with it.

Ensure UAT has the same base managed solution and all intermediate versions installed before applying the update.

create a patch or clone solution that explicitly includes both workflows and import that first.

If the dependency is no longer needed, remove the reference in source, re-export, and re-import

Was this reply helpful? Yes No
anthony56 25 on at

Like (1)

Report
Copy link

Link copied!

Thank you for the reply @#ManoVerse. I found that the first workflow had an unmanaged solution layer, and once we deleted that layer, then we were able to import the solution. I can't explain why that would have been the case, especially since this workflow has been untouched for several years and the dependent workflow has been modified several times over that period, and we never ran into this issue. However, I know that Microsoft has been making changes to the solution import process, so maybe this has been recently introduced.

Was this reply helpful? Yes No
ManoVerse 884 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

glad to see your issue has been resolved and thanks for sharing the insights, It’s interesting that the unmanaged layer was the root cause. MS recent updates have introduced stricter checks on layering and dependencies, which could explain why this issue surfaced now.

Was this reply helpful? Yes No