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

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

The dependent component Workflow (Id=9e79d755-6781-4590-a0fc-223e5ff87235) does not exist. Failure trying to associate it with Workflow (Id=b449927c-40a3-4a09-b606-453f6b1f64fd) as a dependency.

(0) ShareShare
ReportReport
Posted on by 150

Hi,

We are facing this starnge error while importing Managed solution. 

"The dependent component Workflow (Id=9e79d755-6781-4590-a0fc-223e5ff87235) does not exist.  Failure trying to associate it with Workflow (Id=b449927c-40a3-4a09-b606-453f6b1f64fd) as a dependency".  

 

Regards,

Tejas

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Marius Agur Pedersen Profile Picture
    1,771 on at

    This means that you have a reference to a workflow in your solution that does not exist in the target system.

    For example, you may have a workflow or dialog which triggers a child workflow.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
SA-08121319-0 Profile Picture

SA-08121319-0 4

#1
Calum MacFarlane Profile Picture

Calum MacFarlane 4

#3
Alex Fun Wei Jie Profile Picture

Alex Fun Wei Jie 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans