Answered

Cannot delete an entity relationship

(0) Share

Report

Posted on by mariopdemarchi

I wanted to delete an entity relationship 1:N, but I kept getting the same message saying = there are dependencies...you cannot delete it. I deleted all data records on both entities.., refresh browser, etc. etc.) but nothing happened. By mistake I deleted the field in the current entity that involved that relationship (see attachment), so now I have orphan the 1:N relationship on both entities .. This situation is also preventing me to delete the current entity.

Regards.

Mario

Delete_EntityRela...

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (2)

Verified answer

v-bofeng-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @mariopdemarchi :
Could you tell me that the relationship you want to delete is a system-created relationship?
Case1:system-created relationship
I am afraid it cannot be deleted.
Case2:not system-created relationship
I made some tests but didn't encounted the problem you mentioned.
Could you please check wether you have also used this entity as one app's data source?
Perhaps delete all the resources which created based on this entities and then refresh the browser will help you delete it.similar post
I think these links may help you:
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/dependency-tracking-solution-components
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/removing-dependencies
Best Regards,
Bof

Was this reply helpful? Yes No
Verified answer

David Jennaway 716 on at

Like (2)

Report
Copy link

Link copied!

You can use 'Show Dependencies' to determine what dependencies are preventing the deletion. It's most likely that the it is used by a form or view, but could also be processes or rollup fields. For forms or views, the simplest is to remove the field, subgrid or navigation item associated with the relationship. For processes, you may be able to remove the field/relationship, and for any rollup fields you'll need to delete the rollup field. If you need to change forms or views, you'll need to publish the changes before you can delete the relationship

Was this reply helpful? Yes No
mariopdemarchi 20 on at

Like (0)

Report
Copy link

Link copied!

Bof,
Thanks! solved!. The read of your selected article about Dependency tracking for Solutions Components was key.
I had lookup fields in VIEWS and FORMS that I had to delete it (saved & publish) before canceling the entity relationship. As it is said in this article . (My entities are Customs entities under learning process ).

Article: There are three types of solution component dependencies:
Solution Internal
Internal dependencies are managed by Common Data Service. They exist when a particular solution component can’t exist without another solution component.
Published
Published dependencies are created when two solution components are related to each other and then published. To remove this type of dependency, the association must be removed and the entities published again.
Unpublished
Unpublished dependencies apply to the unpublished version of a publishable solution component that is being updated. After the solution component is published, it becomes a published dependency.
Best Regards!
Mario

Was this reply helpful? Yes No
Oztrea 2 on at

Like (0)

Report
Copy link

Link copied!

Don't forget to check if you don't have a plugin using your lookup in the Pre/PostImage, those kind of dependencies are not found by the function RetrieveDependentComponents and then are not shown in the list.

Was this reply helpful? Yes No