You’re offline. This is a read only version of the page.
5
Hello,
I have a really annoying issue when I try to import a solution from a development environment to a production environment. The import gives the error that the bna_primarycontactname column is not in the solution in the Opportunities table. When I check the Opportunities table on either the solution or the regular Dataverse tables, the column is not in either.
However, If I go to create a bna_primarycontactname column in the solution, then it gives an error saying "The table could not be updated: An attribute with the specified name bna_primarycontactname already exists for entity Opportunity."
Both the solution table and regular Dataverse tables have a bna_primarycontact column, but not a bna_primarycontactname column. I do not know if maybe the bna_primarycontactname column is automatically created with the customer type bna_primarycontact column or something and just isn't shown on any table or if this is really a bigger bug in the system.
Also, I can't delete the Primary Contact column from the solution or the regular Dataverse table to test this connected columns idea because it throws this error: "The table could not be updated: Sql error: Generic SQL error. CRM ErrorCode: -2147204784 Sql ErrorCode: -2146232060 Sql Number: 547."
Thanks,
Share
Report
All responses (
Answers (
