Answered

Why is No Cascade enforced for virtual table relationships and how to fix

(0) Share

Report

Posted on by camer314

173

I have a custom table in a 1:N relationship with a virtual table and I noticed that when I deleted the row from the custom table the references to its GUID were not removed from my virtual table. I then noticed that the relationship for delete was Cascade.None

So I tried to create the relationship again setting Delete to 'Remove Link' and got the error:

For Relationships referencing Virtual Entites, Cascade link type must be No Cascade

Why is that? How am I supposed to maintain referential integrity otherwise with a virtual table?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

Michael E. Gernaey 53,429 Super User 2025 Season 2 on at

Like (1)

Report

Hi @camer314

The answer is because Virtual Tables are not storing data in the physical dataverse database. So there is no way for it to be treated as such.

It has always been this way. You would need to create a plugin, or a workflow, so that when you delete the record on the other side, it can delete the Virtual Table Data.

If I have helped you, I would really appreciate if you please Mark my answer as Resolved/Answered, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Was this reply helpful? Yes No
camer314 173 on at

Like (0)

Report

Thanks @FLMike

I would argue though that the Dataverse is entirely capable of putting the reference GUID into the virtual table so logically it should be equally capable of removing it but I guess if that's the way it works then yes will have to create a plugin, or just live with it.

Was this reply helpful? Yes No