Answered

Table relationships - Delete Parent without deleting child lookup value

(0) Share

Report

Posted on by RTB_10

Is it possible to set the custom settings of the Table Relationships so that the parent row can be deleted without removing the lookup value in the related rows?

From what I can tell I can only chose from the three options;

Cascade All (delete both the child row and lookup value, not what I want),
Remove Link (remove the lookup value for all related rows, not what I want because I want to keep this intact), or
Restrict (prevent the primary table row from being deleted when related table rows exist, again not what I want because I don't mind if this is deleted as long as the lookup value stays intact).

Seems like I need a fourth options that doesn't exist. Does anyone have an idea if this is possible?

If not, any helpful workarounds? I'm thinking I could always save the lookup value that I need into a separate text column. And then make sure that if the lookup value is removed (ie blank) that the text column keeps its orginal value.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

Drew Poggemann 9,287 Most Valuable Professional on at

Like (1)

Report

Hi @RTB_10 ,

What type of relationship do you have? Is it Referential? If it is then you will have the ability to Remove Link which I assume is what you want to do since this will keep the child records but remove the lookup value on that table to the Parent record.

You can't keep the Lookup value on the child record because the parent doesn't exist (basically this will create an invalid referential integrity situation). You could have a business rule that will set another field value on your record (Text field) to the "Primary Name" of the related entity so if you do remove then it will show what it was set at from a text value perspective.

Was this reply helpful? Yes No
RTB_10 89 on at

Like (1)

Report

Hi @dpoggemann,

Thanks for your help!

Yes, the relationship is Referential. And your point about creating an invalid referential integrity makes sense, so creating a rule to set the value as text seems like a good option.

Was this reply helpful? Yes No