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)