Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
How reusable is a security role RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Can I copy one from one org to another?  More specifically, since the set of custom entities don't match, am I creating a problem or opportunity for collision by copying a security role from one org to another?  Are custom entities managed by guid or entityTypeCode within the security role?
    Wednesday, April 22, 2015 7:30 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    I've just done a test and managed to import a role that was controlling access to an entity present on the origin CRM but not present on the destination CRM. the import went though without errors. the role was created on the destination, but the role's settings for the custom entity disappear. So, even if that may not break the system, it Can cause confusion. Specially if you are moving across DEV, TEAST and PROD systems. Not a good practice.

    I Hope I could help. If I have answered please mark as 'Answer'. If was just helpful, please vote. Thanks and happy coding! Bruno Lucas, http://dynamicday.wordpress.com/

    • Marked as answer by mardukes Thursday, April 23, 2015 4:02 PM
    Thursday, April 23, 2015 2:07 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Mardukes,

    You can transfer a security role from one CRM org to another but if this role has permissions that control an entity that is not common to both environments, than you will probably get a "dependency" error when you try to import the solution.

    I Hope I could help. If I have answered please mark as 'Answer'. If was just helpful, please vote. Thanks and happy coding! Bruno Lucas, http://dynamicday.wordpress.com/

    Thursday, April 23, 2015 1:50 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I've just done a test and managed to import a role that was controlling access to an entity present on the origin CRM but not present on the destination CRM. the import went though without errors. the role was created on the destination, but the role's settings for the custom entity disappear. So, even if that may not break the system, it Can cause confusion. Specially if you are moving across DEV, TEAST and PROD systems. Not a good practice.

    I Hope I could help. If I have answered please mark as 'Answer'. If was just helpful, please vote. Thanks and happy coding! Bruno Lucas, http://dynamicday.wordpress.com/

    • Marked as answer by mardukes Thursday, April 23, 2015 4:02 PM
    Thursday, April 23, 2015 2:07 AM