web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics 365 | Integration, Dataverse... / Cannot change relation...
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested Answer

Cannot change relationship behavior from Referential to Configurable Cascading

(0) ShareShare
ReportReport
Posted on by KrishnaReddy95 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

I have the same question (0)
  • Suggested answer
    Nya Profile Picture
    Nya 29,064 on at

    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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Congratulations to our 2025 Community Spotlights

Thanks to all of our 2025 Community Spotlight stars!

Congratulations to the February Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
11manish Profile Picture

11manish 156

#2
Pallavi Phade Profile Picture

Pallavi Phade 102 Super User 2026 Season 1

#3
Abhilash Warrier Profile Picture

Abhilash Warrier 55 Super User 2026 Season 1

Last 30 days Overall leaderboard

Featured topics

Welcome to the Microsoft Dynamics 365 forum!
Identifying an Org as CDS or Dynamics
Get batch job history log from D365 FO to Power Automate
Gross and Net Weight of Shipments feeding back into Sales Order (from External Source)

Product updates

Dynamics 365 release plans