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

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics CRM (Archived) / Record Creation on Wor...
Microsoft Dynamics CRM (Archived)

Record Creation on Workflow A not triggering on-create-listening Workflow B in CRM 365 9.0.1.459

(0) ShareShare
ReportReport
Posted on by Fred McGraw 85

Hello Everyone,

So I have a workflow that is listening to the status reason change of entity A. When entity A's workflow runs it creates zero or many of a completely different entity -- entity B. I have second workflow listening for the creation of entity B records. Looking at System Jobs its not triggering. Why might it not be triggering the second workflow?

The second workflow is running in the background. Its trying to make a Task pointing to the record that was just created, but as mentioned in System Jobs, it doesn't even show that it ran.

Any help would be really appreciated. Thank you.

*This post is locked for comments

I have the same question (0)
  • Fred McGraw Profile Picture
    Fred McGraw 85 on at

    Also worth mentioning manually creating a record of entity B causes Workflow B to run. Just not the create from Workflow A.

  • a33ik Profile Picture
    a33ik 84,331 Most Valuable Professional on at

    Hello,

    Can you please post a screenshot of workflow B?

  • Suggested answer
    RaviKashyap Profile Picture
    RaviKashyap 55,410 Moderator on at

    Hi Fred,

    If you don't see system jobs them it doesn't mean the the workflow hasn't ran. If you have slected the option "automatically delete completed workflow jobs" then it is possible that the workflow has ran successfully and the job got deleted.

    Also, it is unlikely that the workflow which is marked to trigger on create doesn't trigger on create of record.

    I would suggest to check if you have the above option to automatically delete the jobs configured or not. If configured, remove that option and try again.

    You can also verify if the workflow has ran or not by doing an advance find for the expected records so in your case check if the are entity records created.

    Hope this helps.

  • Verified answer
    Fred McGraw Profile Picture
    Fred McGraw 85 on at

    Hey Andrew,

    Thank you for offering to look into this for me. I figured it out this morning. Both workflows' scope were set to user. In workflow A during the create I would make the owner of the new records a different user. Once I set workflow B's scope to Business Unit it worked. I guess I need to read up a little on scopes.

  • Fred McGraw Profile Picture
    Fred McGraw 85 on at

    Hi Ravi,

    The issue ended up being scopes of the workflows. I wanted to thank you for reaching out and giving me something to look into and brainstorm against.

  • a33ik Profile Picture
    a33ik 84,331 Most Valuable Professional on at

    Fred,

    This is was my assumption - that's why I asked for a screenshot. Great that you resolved that issue.

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…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

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