As with other permissions in Dynamics CRM, you can grant a role “User,” “Business Unit,” “Parent/Child Business Unit,” and “Organization” level security permissions for both append and append to. The next consideration is what permission level the users should have. I think of it this way-I’m APPENDING the opportunity, and I’m APPENDING it TO the account. In this example, a user must have “Append” permissions on Opportunities (child) and “Append To” permissions on Accounts (parent). Say a user needs to be able to relate Opportunities to Accounts, either through the Potential Customer lookup field on the Opportunity, or through the “Opportunities” navigation bar area on an account. There are multiple Opportunities per Account. In this relationship, “Accounts” is the parent and “Opportunities” is the child.
Let’s take the example of Accounts and Opportunities. I find this confusion comes from the similar sounding names of these permissions, and also because configuration of relationship security requires permissions to be applied to two separate entities-both sides of the relationship. This post is CRM security 101, but I get asked this question fairly often, so it seems that there is some confusion about what the difference is between “Append” and “Append To” security permissions. Today’s guest blogger is CRM MVP Joel Lindstrom who blogs at CustomerEffective.
0 kommentar(er)
