Customer Engagement & Dynamics CRM Forum

Expand all | Collapse all

Security Role settings for Opportunity Relationship

  • 1.  Security Role settings for Opportunity Relationship

    TOP CONTRIBUTOR
    Posted Jan 14, 2019 09:27 AM
    ​We are nearing our go live with v9, and I've got an open issue I'm trying to get more information about.

    I have a specific team of users who are permitted to merge accounts. They're merging is working fine in production with the security settings they have. However, when testing v9 in our sandbox, they receive an insufficient permissions error when trying to merge accounts. We've determined that we can prevent the error by giving them Read access on 'Opportunity Relationship' on the Core Records tab. This setting/access has not been required in v8.2.

    My questions:
    1) What is different with v9 that is now requiring Read access here?

    2) What does "Opportunity Relationship" control in the system? If I give them read access here, what else am I giving them access to do?

    Thanks for helping me learn!


    ------------------------------
    Julie Reynolds
    Enterprise Information Steward II
    Brotherhood Mutual Insurance
    Fort Wayne IN
    ------------------------------


  • 2.  RE: Security Role settings for Opportunity Relationship

    TOP CONTRIBUTOR
    Posted Jan 16, 2019 08:31 AM
    Hi Julie,

    I think that this is cause by relationship behavior. I think that merging the accounts cascade into the opportunities which cascade into opportunity relationship. Compare the 1:N relationships between Account and Opportunity in both systems and see if there is a difference between them.

    ------------------------------
    Gus Gonzalez
    7x Microsoft MVP, CRMUG All-Star
    CEO, Elev8 Solutions
    ------------------------------



  • 3.  RE: Security Role settings for Opportunity Relationship

    TOP CONTRIBUTOR
    Posted Jan 16, 2019 09:13 AM

    ​Gus,

    Thanks for the idea. I just checked the settings and they're same in our production and test environments. It's set to Referential with Delete being Remove Link and Merge being Cascade All. Otherwise they're all Cascade None.



    ------------------------------
    Julie Reynolds
    Enterprise Information Steward II
    Brotherhood Mutual Insurance
    Fort Wayne IN
    ------------------------------



  • 4.  RE: Security Role settings for Opportunity Relationship

    TOP CONTRIBUTOR
    Posted Jan 16, 2019 02:06 PM
    Julie,

    I think the opportunity relationship was older functionality that has pretty much been replaced by connections.

    There used to be (back in the 2011 or earlier days) relationship roles for Accounts, Contacts and Opportunities.  But this was kind of limiting, as you might want to have relationships with other entity types. So Connections was introduced.

    I found this article from PowerObjects that goes into some interesting detail on this:  https://www.powerobjects.com/2013/04/25/replace-relationship-roles-with-connections-in-dynamics-crm/    Perhaps there are still relationships that exist in this legacy Role Relationship entity that is impacting this?



    ------------------------------
    Patrick O'Donnell | VP - Business Development, the Americas
    mscrm-addons.com
    Patrick.ODonnell@mscrm-addons.com
    Atlanta GA
    770 781 8260 Cell
    ------------------------------



If you've found this thread useful, dive deeper into User Group community content by role