Hi,
I have created 3 entities : Project, Consultant and ProjetConsultant
The Project Entity properties : Name, Start Date, End Date
The Consultant Entity Properties : Name
The ProjetConsultant Entity Properties : Name, Name (from the Projet Entity), Name (from the consultant Entity)
There is a Many to One Relationship between ProjectConsultant and Project Entities.
There is a Many to One Relationship between ProjectConsultant and Consultant Entities.
Therefore, there is a Many to Many Relationship between Project and Consultant Entities.
In the event I delete (add or update) a record on the ProjetConsultant Entity, is it possible to trigger a Flow on Its related Project Entity Record ?
Thanks,
Arioule
Hi @shavora,
Not sure if you solve this or not, but you can find the relationship name in Maker portal --> Dataverse --> Tables --> pick your parent table --> Columns --> pick the lookup column --> Expand "Advanced Options" and you'll find the relationship name. Hope this helps and suggest to open a seperate thread to try to get more assistance from the community 🙂
@EricRegnier here I mean the relationship that's created between the tables, maybe using the action unrelate rows or relate rows... I have been trying to solve this for a long time and so I'm trying to explore everything. But I realize now that I'm thinking backwards about child/parent tables. I am reading now that the table that has the lookup column is the child record. So my flow is triggered on the deletion of the child record. Which in of itself is an annoying way to find related records from. But the basic issue I am trying to solve is that I am not able to re-activate a bpf, and so we can't send out the welcome email again.
Hi @shavora, can you ellobarate a little on this? What is meant by find the relationship? Cheers
Do you know what the plugin is called? It's not for cascading delete, it's to reset a BPF from closed to first stage for the related child. So it's quite complex. But it makes sense, an employee can be booked for a training course but many need to be re-booked. So when the booking is deleted the journey should reset.
I managed to find the related child record from making a flow compare employees who existed in a booking and employees having Status booked. Then I could single out which which records that is effected but it was sadly quite complex. A plugin sounds much less hassle.
Need to take into account that a dataverse Flow is asynchronous (background, except for a HTTP trigger), hence the the record is deleted before the Flow is triggered (so you will not be able to find child records based on the Lookup value as it will be empty as the record is deleted). If you need to do something like update child records when parent is deleted then you would need to write and register a Plugin that triggers on delete in the PreOperation stage (i.e. triggers when a delete is initiated but runs before the actual delete occurs). If you just need to cascade the delete (i.e. parent deleted, delete all children), then you can configure the Lookup relationship to do this.
@EricRegnier can we find the relationship if we delete the parent record as the trigger?
Hi @Arioule,
Yes you can. Create your flow from a solution in make.powerapps.com, use the Common Data Service (current environment) connector, user the when a record is created/updated/deleted trigger step on the parent record, and then you can perform different actions of your child records. Or as you questioned, you can invoke a child flow, but you child flows needs to be configured to be consumed by a parent flow, here's more details on child and parent flows:
Build a child flow: https://docs.microsoft.com/en-us/power-platform-release-plan/2019wave2/power-automate/call-child-flows#building-the-child-flow
Call a child flow from a parent flow: https://docs.microsoft.com/en-us/power-platform-release-plan/2019wave2/power-automate/call-child-flows#building-the-parent-flow
Hope this helps!
WarrenBelz
791
Most Valuable Professional
MS.Ragavendar
410
Super User 2025 Season 2
mmbr1606
275
Super User 2025 Season 2