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 CRM (Archived) / Dynamics CRM Bug? Unab...
Microsoft Dynamics CRM (Archived)

Dynamics CRM Bug? Unable to import solution when customer lookup has two "Cascading" relationships

(0) ShareShare
ReportReport
Posted on by HarryZang 240

Dear All,

Recently we found a issue in Dynamics CRM (2016/365) ( appears in all versions since 8.1 to latest 8.2.1)

As from CRM 2016 8.1, Microsoft introduced customer lookup support for custom entities.

(customer lookup have many to 1 relationship to Account/Contact

Which is great,

However, when you configure the customer lookup like this:

have both "cascade/parental" relationship with account/contact.


CRM will allow you export the solution , but will throw error when importing

TwoCascadeRelationship.jpg

However, if you set the relationship to one "cascade/parental", one "referential", the

error will gone.

The most strange is, if you are updating an existing solution with that customer lookup already,

you can import the solution with two "cascade/parental" without error.

Just ask if it is a Microsoft bug or as design?

Is there any solution for it?

Many Thanks

Harry

*This post is locked for comments

I have the same question (0)
  • HarryZang Profile Picture
    HarryZang 240 on at

  • Suggested answer
    prt33k Profile Picture
    prt33k 6,907 on at

    Hi Harry,

    You can have only a single parental relationship in CRM - multiple parents are not a valid scenario.

    In your case, there is already a OOB field parentcustomerid thus when you are trying to create a new field with parental relationship, it is throwing error.

    I think if you change the behavior of relationship contact_customer_accounts and  contact_customer_contacts from parental to configurable cascading then it will work.

    Thanks.

    Prateek

  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    Hi,

    Agree with Prateek. There can only be one parental relationship present between two entities at a time. You can change the relationship behavior and try importing the solution.

    [If you find any helpful answer(s) of your question, please mark the answer(s) as verified answer(s).]

  • HarryZang Profile Picture
    HarryZang 240 on at

    Thanks for reply,

    Just correct, as  I am using the custom entity, there is no OOB "parentcustomerid" field.

    The reason for import failure is this customer lookup cannot have "account", "contact" relationship both have "configurable cascade" or "parental" relationships.

    I have already tried setting two relationship as configurable cascading (with both delete set as "cascade all"), but was failed when importing. As you have mentioned CRM does not allow multiple parents , I guess it iscaused by account/contact can not have the same parental behavior at the same time, such as "Cascade All" for delete operation.  

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!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics CRM (Archived)

#1
AS-17030037-0 Profile Picture

AS-17030037-0 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans