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

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) / Workflow triggered by ...
Microsoft Dynamics CRM (Archived)

Workflow triggered by Change will not run for some users

(0) ShareShare
ReportReport
Posted on by samalex 355

I'm at a loss on this one and need some advise.  We have a service account that updates the Status change of a Record and when we have a workflow set to run on status change as an admin account to do some other work.  This workflow runs fine when a CRM user updates the record in CRM, but when the service account updates it through the SDK the workflow does not run.  The service account has slimmed permissions to just do what needs, but apparently it's too slim since the Workflow isn't firing.  I just don't know why.  I can make the service account a system admin in CRM and it runs fine so I know it's not a code issue.

Is there anything I need to add or setup on a CRM user that would prevent a workflow that fires as another user on status change to not run?  No errors are logged, not even on the server it's like the workflow just doesn't fire.  The workflow is setup as Organization and just Run in the background and a CRM Administrator account is the owner.  And it starts when Record Status Changes.  The service account changes the status via SDK and nothing runs though any CRM user can change the status (when permission allows) and the workflow runs fine.

Thanks in advance for any suggestions or help on this, I'm at a loss.  

Sam

*This post is locked for comments

  • Suggested answer
    Nuno Profile Picture
    Nuno 2,005 on at

    Hi,

    Under the Microsoft Dynamics CRM Security Role, Customization tab, there is a "Workflow" entity to set security privileges on.

    This setting controls the Workflow privileges for CRM Users assigned to this security role.

    Check if the user have the required privileges to run the workflow.

    Regards

  • Suggested answer
    Drew Poggemann Profile Picture
    Drew Poggemann 4 on at

    Hi Samalex,

    Make sure your workflow is setup to run at Organization level so it will execute for all users.  Hopefully that is the problem.

    Thanks much,

  • Verified answer
    samalex Profile Picture
    samalex 355 on at

    The fix was that I had to give User level Read, Create, and Write access to the System Job entity for the Role the user was running with.  If the process ran under almost any circumstance the workflow ran without issue, but for processes ran from the SDK using impersonation where I set the CallerID  the workflow failed with missing Read and Create permissions to System Job.  Adding these permissions to the role allowed it to run without issue.

    As to why there's a difference between processes running with Impersonation verses those without I'm still not sure.  I've researched this, but I can't find anything saying why this would be so.  If anyone knows I'd love to know, but just note any SDK call using Impersonation (setting CallerID) that could cause a workflow to fire it will need these permissions on System Job entity.

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the September Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
TNJ_CRM_Team Profile Picture

TNJ_CRM_Team 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans