locked
Assigning records CRM 4.0 RRS feed

  • Question

  • Hi,

    I want a user to be able to see only his own Accounts, but to be able to assign it to anyone in the organisation, even outside his business unit, if necessary.

    So in the security roles, I set his Access Levels on ACCOUNTS as follows:

    Account Create, Read, Write, Delete:  USER only

    but for Account Assign: ORGANISATION.

    But it does not work! If this user tries assigning one of his accounts to someone else, he gets a 404 error message, not enough privileges. 

    As I entered  "organisation" for the Assign privilege in the security role, as I said above, it should work .. !! So where is the problem?

    Can anyone help me with this, please?

    Thanks.

    Monday, February 13, 2012 4:01 PM

Answers

  • I think you also need to set the Append and AppendTo rights - I think it should be User level Append on the account entity, and Organisation level AppendTo on the user entity

    The other thing to check is if there are any cascading assignments set on the account relationships. If so, CRM will also try assigning the related records, and the user will need permissions to assign these records.

    If you enable CRM tracing, then ntify the particular privilege (by privilegeid) that the user is lacking

    You should only need User level for the assign permissions. The level applies to the ownership of the record that the user is trying to perform the action on - i.e. the user is assigning records they own


    Microsoft CRM MVP - http://mscrmuk.blogspot.com  http://www.excitation.co.uk


    Monday, February 13, 2012 4:52 PM
    Moderator

All replies

  • Give Assign To Permission also.

    Also try changing write permissions because when we assign a record the ownerid field get updated.


    Regards Faisal

    Monday, February 13, 2012 4:12 PM
  • I think you also need to set the Append and AppendTo rights - I think it should be User level Append on the account entity, and Organisation level AppendTo on the user entity

    The other thing to check is if there are any cascading assignments set on the account relationships. If so, CRM will also try assigning the related records, and the user will need permissions to assign these records.

    If you enable CRM tracing, then ntify the particular privilege (by privilegeid) that the user is lacking

    You should only need User level for the assign permissions. The level applies to the ownership of the record that the user is trying to perform the action on - i.e. the user is assigning records they own


    Microsoft CRM MVP - http://mscrmuk.blogspot.com  http://www.excitation.co.uk


    Monday, February 13, 2012 4:52 PM
    Moderator