Friday, June 01, 2012 5:57 PM
We upgraded from CRM 4 to CRM 2011. I'm in the process of moving a solution containing all of our customizations to a new CRM server and am getting an error below
The dependent component Workflow (Id=128ac0f0-811f-4268-a9a0-7418066cce79) does not exist. Failure trying to associate it with Workflow (Id=bb20ca81-f107-487e-b248-39fa24ac5403) as a dependency. Missing dependency lookup type = PrimaryKeyLookup.
I've traced this to a problem in a Template Workflow which has a pointer to a workflow which was deleted a long time ago. So, I attempted to de-activate the template so I could remove the pointer, but I get the same dependency error in return. I cannot deactivate the workflow so that I can edit it. So, I decided to delete the template - same result - it can't be deleted because of the dependency error.
How do I get around this dependency error so I can fix or delete this template workflow?
Sunday, June 03, 2012 2:00 PM
Are you exporting the default solution and then import into another CRM deployment? try create a new solution, add all components except this template workflow component, then export solution and import into the other CRM deployment.
- Proposed As Answer by Jehanzeb.Javeed Monday, June 04, 2012 3:55 PM
Monday, June 04, 2012 1:40 PMThat does work, but I'm trying to keep that template as well - it has a lot of complex logic in there I'd rather not rebuild if possible.
Monday, June 04, 2012 3:55 PM
Try save workflow template as Workflow and then try export and import back into other system or you may need to remove the ParentWorkflowId value manually from the database Workflow table (direct database modifcations are not reocemmended, supported and may cause problems in CRM system)