Hi @JT_Corrin ,
Thank you for posting about this, I have almost forgotten about it.
I had seen a similar issue about 4 years ago when I started working with at the time CRM, which had been rebranded to Dynamics 365 or CDS, depending on the organization type.
During that case I discovered the related entity had its reference set by an attribute mapping and there was some kind of broken metadata for that particular field and we ended up recreating the attribute mapping.
My recommendation is the following:
- go to the relationship you have in place for the two entities where you will link them together and verify if on the left side you have Mappings
- in the mappings section if the Name is present make sure it is not on the first line as this won't allow you to recreate the mapping unless you will recreate the relationship and the relationship recreation will require additional processes to store the data outside the organization during this recreation as otherwise it will be deleted
- try to verify the solution layers for the mappings using a syntax similar with this after you used the Browser Debugger->Dom explorer to get the GUID of the AttributeMap <OrganizationURL>/api/data/v9.1/RetrieveSolutionMetadataForComponent(SolutionComponentName='AttributeMap',ColumnNames=%5b'attributemapid'%5d,ColumnValues=%5b'<AttributeMap_Guid>'%5d)
- Once you have the answer regarding the layers, verify the solution, if you have only one result which is "Active" you can make your deletion and recreation in the affected organization
- otherwise you need to remove that one from each solution introducing it in reverse import order other than the Active one which will be removed during the last layer removal; Keep in mind, this process needs a removal of the Attribute Map from the Development environment and a clone of the solution, after that an import with the default options (Upgrade and Maintain customizations) in the affected environment
- After the mapping will be removed, feel free to recreate it in your development system or in the affected environment, based on your layers.
I hope this will be able to resolve your problem, feel free to raise a ticket to us in case you want to perform the steps together.
Or if you encounter any error during the process please post the error with its timestamp and ActivityId in order for us to be able to trace it.
Thank you for using Microsoft Communities,
Madalina Toma
Support Engineer
Microsoft Dynamics 365 and PowerApps
