Skip to main content

Notifications

Microsoft Dynamics 365 | Integration, Dataverse...
Suggested answer

Cannot change relationship behavior from Referential to Configurable Cascading

Posted on by 45

Hi All,

We have one custom entity to that entity we have 1:N relationship to Opportunity (custom entity - Opportunity) , by default the relationship behavior is Referential. When i try to change the relationship behavior from Referential to Configurable Cascading getting below error.

Error Message: The related entity has already been configured with a cascading or parental relationship.

I have cross checked the error message on this two entities but there is no relationship exist either with cascading or parental. Any leads on resolving this issue. Please post here.

pastedimage1617626807129v1.png
Thanks,

Krishna Reddy Yeruva

  • Suggested answer
    Nya Profile Picture
    Nya 29,056 on at
    RE: Cannot change relationship behavior from Referential to Configurable Cascading

    Hi,

    There is a message in the error log saying that “Opportunity is parented to Entity with id: ……”.

    The “parented” here means one in which anything cascades, not just the parental type relationship.

    Here is a documentation on cascading behavior which you can refer to know more about how the actions of the entities governed by this relationship interact with each other:

    https://docs.microsoft.com/en-us/previous-versions/dynamicscrm-2016/developers-guide/gg309412(v=crm.8)?redirectedfrom=MSDN#cascading-behavior

     

    Opportunity has this relationship with two entities by default – Contact and Account.

     pastedimage1617678582938v1.png

    Also, you can find a Note which says that:

    A custom entity cannot be the primary entity in a relationship with a related system entity that cascades.

    in the following documentation.

    https://docs.microsoft.com/en-us/previous-versions/dynamicscrm-2016/administering-dynamics-365/dn531171(v=crm.8)#create-or-edit-1n-relationships-between-entities

     4278.png

    So "Referential: restrict delete" is the best option for you.

     

    If this helped you, I'd appreciate it if you'd mark this as a Verified Answer, which may in turn help others as well.

    Best Regards,

    Nya

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Product updates

Dynamics 365 release plans