Prevent deletion of records where it is used for a lookup?

(0) Share

Report

Posted on by THowkins96

Hi all,

Is there a way in Dataverse to stop a record being deleted when it is used as a lookup in a child table?

As an example:

Table A contains the row "Business Unit 1"

Table B looks up to table A and creates a record referencing business unit 1

How can I prevent the deletion of the row "Business Unit 1" so that it does not break the hierarchy?

Thanks!

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

MarioRing 541 Super User 2024 Season 1 on at

Like (2)

Report

Yes, it is possible by using the configuration.
Go to make.powerapps.com, go to solutions, and choose your solution. Then find your "protected" table on the list, navigate to the "Relationships" and select the relationship with the second object (if there is no relationship there, please use the "add existing" feature). Click "Advanced options" and set the value "Restrict" in the "Delete" field. Save all and publish.

In this example I used the relationship between Contact and Account (as Primary Contact). If the Contact is used as Primary Contact for any Account (there is a lookup for single Contact on the Account form) it is not possible to delete this Contact:

Read more about this in the documentation here.

Was this reply helpful? Yes No
THowkins96 88 on at

Like (0)

Report

Hi @MarioRing

Thank you so much for that! That's perfect 🙂

Can I just clarify one thing, if a row is deleted by a dataflow rather than manually as a result of enabling the "delete rows no longer in the query output" feature, will this still prevent the deletion of the row if there are dependencies elsewhere in the data?

Thanks
Tom

Was this reply helpful? Yes No
MarioRing 541 Super User 2024 Season 1 on at

Like (0)

Report

Good question. Unfortunately, I've never tried this way. You can verify it on your own and share the outcome with us! In my opinion that situation should throw an error.

Was this reply helpful? Yes No
THowkins96 88 on at

Like (0)

Report

I've just carried out a test to see what would happen and as it turns out it does indeed not delete the row that no longer existst in the output! Success!

It does not however tell you in your dataflow that it was unsuccessful, you get the green tick as per usual dataflow success!

Really nice feature, thanks again for your help @MarioRing

Was this reply helpful? Yes No