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

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

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