locked
Publish Workflow Error - Wrong Role Settings? RRS feed

  • Question

  • Hello,

    I am a CRM 4.0 Admin and I have the following situation. Generally, I do not want users to be able to create workflows or edit them. They only need the right to apply them. Now I have an exception to that rule.

    One user needs the right to unpublish, modify and publish one specific workflow. First, CRM told me that only the owner of a workflow can publish/unpublish. That was easy to solve. Second, CRM tells me that the user does not have sufficient rights to publish a workflow. In the security settings of that security role under "customisation" I even tried to put all symbols to the full green dot but it still doesnt work.

    What do I need to change?

    Thanks for your help, guys!

    Peter

    Wednesday, January 5, 2011 3:03 PM

Answers

  • Hi Peter,

    I guess you may be experiencing this error because your user belongs to a custom role and not to a system out-of-the box role such as System Customizer.

    Ther are some privileges included on those system roles that are not available via the Role Editor and hence you will  need to make some tricks in order to 'unhide' them and be able to set them up to users. In particular, for the case of WFs, the missing permission is the AppendTo one. :p).

    Please go over this post from Bill Owens and follow his steps. Please note that the change is unsupported.

    I would also suggest you to grant System Customizer privileges in order to let your user publish the WF and afterwards, remove him that role.

    Hope it helps,

    PP


    Microsoft MVP Dynamics CRM | My Twitter: http://twitter.com/pabloperalta | My blog: http://weblogs.asp.net/pabloperalta
    Wednesday, January 5, 2011 4:28 PM

All replies

  • Hi Peter,

    I guess you may be experiencing this error because your user belongs to a custom role and not to a system out-of-the box role such as System Customizer.

    Ther are some privileges included on those system roles that are not available via the Role Editor and hence you will  need to make some tricks in order to 'unhide' them and be able to set them up to users. In particular, for the case of WFs, the missing permission is the AppendTo one. :p).

    Please go over this post from Bill Owens and follow his steps. Please note that the change is unsupported.

    I would also suggest you to grant System Customizer privileges in order to let your user publish the WF and afterwards, remove him that role.

    Hope it helps,

    PP


    Microsoft MVP Dynamics CRM | My Twitter: http://twitter.com/pabloperalta | My blog: http://weblogs.asp.net/pabloperalta
    Wednesday, January 5, 2011 4:28 PM
  • Hi,

    wow. Thanks for the quick reply! That sounds like one of the "deeper" customizations. I'll do my best.

    By the way, let me quote Bill Owens: "The Microsoft CRM privilege model is complex and the exact combination of privileges to perform a particular action are NOT well documented.  This is probably the single biggest cause of frustration for customizers and users alike."

    True that :-/

    With kinds regards
    Peter S.

     

    Thursday, January 6, 2011 2:44 PM
  • :p) it's true. you are welcome.

    Please let me know if that worked!.

    Regards,

    PP


    Microsoft MVP Dynamics CRM | My Twitter: http://twitter.com/pabloperalta | My blog: http://weblogs.asp.net/pabloperalta
    Friday, January 7, 2011 10:38 AM