I've got a support request open with Microsoft support - but they haven't made any progress in 3 weeks. Has anyone encountered this issue and found a solution?
This is complete block on progress for the project I'm working on.
The tables already exist in the target environment from a previous version of the managed solution, I'm trying to import an update including an N:N (Many-to-Many) relationship between the 2 tables.
Steps to reproduce:
- Export Solution as managed from source environment
- Import Solution to target environment
- Import fails with error "Entity [tableName] cannot be in a custom entity association"
This is the error displayed as a notification in the target environment, and also the error shown in the full Error log XML file (I know sometimes the notification error can be misleading).
Using the API service to view the metadata, indicates I should not encounter this error as I see this in the metadata regarding the tables in both the source and the target environment:
"CanBeInManyToMany":
{ "Value": true, "CanBeChanged": false, "ManagedPropertyLogicalName": "canbeinmanytomany" },
"CanBeInCustomEntityAssociation":
{ "Value": true, "CanBeChanged": false, "ManagedPropertyLogicalName": "canbeincustomentityassociation" }
Another symptom is that I am unable to create the N:N relationship directly in the Target environment (using an Unmanged solution layer) - I get the same error message pop up in the UI.
Can anyone help?
Thanks.
