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

Community site session details

Session Id :
Microsoft Dynamics CRM (Archived)

Customize Configurable Cascading Relationship

(0) ShareShare
ReportReport
Posted on by

I have a 1:N relationship configured between a Custom entity and Opportunity respectively. by default, it is a referential relationship between these two entities. What I would like to do is to make it a Configurable Cascading so that I can edit the behaviours on the Share and Delete  aspects, specificaly. Now, upon clicking on the Save button after changing these behaviours, I get this error

ppp.png

Now, I do not know what kind of sin I am commiting to get this error, but as it says there is already another relationship, I just cannot find the refered relationship from the error.

How can I achieve making or creating a Configurable Cascading relationshp and actually edit its behviours?

Thanks in Advance.

Victor.

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Amanda_M Profile Picture
    65 on at
    RE: Customize Configurable Cascading Relationship

    Out of the box, Account has a parental relationship to Opportunity.  And an entity can only have 1 parental relationship.  (so in this case, for example, if you delete an account, you delete all of its opportunities.  which would make sense).  If you want, you can change that (I'm not saying that you should, but you can.  If it fits what you're trying to do).  Go to the Opportunity entity's N:1 relationships, and edit the opportunity_customer_accounts relationship, and under Relationship Behaviour, change Type of Behavior from Parental to Configurable Cascading.

    Then you should be able to finish setting up your parental relationship to your other entity.

  • Suggested answer
    Community Member Profile Picture
    on at
    RE: Customize Configurable Cascading Relationship

    Amanda is nearly right. Bear in mind that a parental relationship is one in which anything cascades, not just where the "template" choice says "Parental".

    When you switch to use the "template" called "Configurable Cascading" it sets all the applicable cascade options to "All". If you save at this point, next time you open the screen it recognises this as matching the standard "Parental" template and shows this instead. Basically, the four options are just templates to set standard pre-defined sets of behaviours. This is not saved anywhere; only the individual behaviours are.

    To stop a relationship being Parental, you need to set it to "Referential" or "Referential: restrict Delete", or use Configurable Cascading and change them all to "None".

    And Opportunity has two parental relationships - for Account and Contact (in common with any other system entity that has a "Customer" hybrid lookup). Activities have LOADS!

    Anyway, it's all moot, because there is another rule that says you can't have a parental relationship where a custom entity is the parent over a system entity. So "Referential: restrict delete" is the best option yo ucan use here. Your sharing will have to be done with custom code.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
HR-09070029-0 Profile Picture

HR-09070029-0 2

#1
UllrSki Profile Picture

UllrSki 2

#3
ED-30091530-0 Profile Picture

ED-30091530-0 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans