Answered

Removed column from table, now can't deploy

(0) Share

Report

Posted on by nksse

I have three environments: default, development, and production. I used the default environment to create our 'core' data tables, then deploy those to development as a managed solution. And the build our apps in development, eventually deploying everything to production.

Today, I added a new table to default, with a lookup to a wrong table. And deployed this to development where I realised the mistake of looking up the wrong table. So, in default, I removed the lookup column, and re-added it (with the same name) to lookup the correct table.

But now, when trying to deploy to development, I get this error:

Solution "Data Tables" failed to import: ImportAsHolding failed with exception :EntityRelationship [new_role_Team_new_team] is invalid. The lookup attribute [new_Team] is already associated with an existing relationship.

How do I get past this, so that I can deploy the new version to development, and eventually production?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

a33ik 3,306 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

Hello,

Dataverse is confused in such scenarios like deletion/recreation of the column in the same table with the same schema name but with different metadata.

1. Delete the new column in your default environment.

2. Export the solution from default as managed, and import it to development, so deletion will take place there as well.

3. Create a new relationship/column in default and add it to the solution.

4. Export the solution from default as managed, and import it to development.

Now, after that multistep sequence, everything should start working.

Was this reply helpful? Yes No
nksse 66 on at

Like (0)

Report
Copy link

Link copied!

Thank you @a33ik. That makes sense and it worked.

Was this reply helpful? Yes No