Customer Engagement & Dynamics CRM Forum

Expand all | Collapse all

Best Practices for Entity Relationship Behaviors

  • 1.  Best Practices for Entity Relationship Behaviors

    SILVER CONTRIBUTOR
    Posted Apr 16, 2020 11:52 AM

    Hello!

    When it comes to entity relationship behaviors, are there best practices used by any of your companies? I'm thinking some form of Configurable Cascading is best?

    Also, if you are Cascading Active the 1:N relationship of Account to Appointment, for example, and you Assign an Account to a new User, does this mean all Closed (canceled or completed) Appointments would not change ownership, but all Open Appointments would be reassigned to the new User? Or would the Closed Appointments also be reassigned to the new User?

    I don't know why this topic confuses me so much. Has anyone found helpful sites with information on this topic?

    Thank you all for your help!

    Mary Lauren

    #Admin​​​
    #CustomerEngagement

    ------------------------------
    Mary Lauren Hughes
    CRM & Sales Coordinator
    InfoWorks, Inc.
    Nashville, TN
    ------------------------------
    Academy - Online Interactive Learning from Experts


  • 2.  RE: Best Practices for Entity Relationship Behaviors

    TOP CONTRIBUTOR
    Posted Apr 16, 2020 04:07 PM
    We have a lot of configurable cascading relationships set up and I think they're useful and can be modified as needed. Your description of Cascade Active sounds correct. This link is to a resource that describes the configure options in detail: https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/entity-relationship-behavior#configure-entity-relationship-behavior

    ------------------------------
    Andy Arndt
    Minitab, Inc.
    State College PA
    ------------------------------

    Academy - Online Interactive Learning from Experts


  • 3.  RE: Best Practices for Entity Relationship Behaviors

    TOP CONTRIBUTOR
    Posted Apr 17, 2020 02:16 AM
    Hi Mary
    I am all with you that relationships can get confusing. The link from Andy gives you all the knowledge on the different cascading rules. In the end it requires testing to see if the changes do what you expect.
    Once you have figured out what you want to do, save all your relationship changes in a solution (only the relationship changes, no meta data no other fields or forms). You might risk that those changes get overwritten with system updates. This happend to me once.

    ------------------------------
    Axel Girgensohn
    Dynamics CRM Specialist
    Aller Media AB
    ------------------------------

    Academy - Online Interactive Learning from Experts


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