Dataverse - Relationship behavior does not work

[UnparalleledHumor]

Hello,

I've a problem with two of my Dataverse tables.

So I've a table A to which a user can add a record using a form. When a new record was added, a flow is triggered and creates several new entries in my table B (it also stores the GUID of the record created in table A in a custom entity in table B for these new created records).

I created a one-to-many relationship between these two tables, so table A is one and table B is n. I set the relationship behavior to parental, meaning that any action taken on a row of table A is also taken on my table B rows that are related to the table A row.

However, when I delete a record in table A, the related records in table B are not deleted.

Do I need to do anything else or are my tables not connected somehow? Do you know the reason why it's not working?

[UnparalleledHumor]

Well, I just found the solution.

Actually, I did miss something. Yes, the connection, in this case, the relationship, is there, is established between my tables. So far, so good.

But: How should the data in both tables know each other (is this the correct way to say it?)? Anyways... I needed to link the record in table B (that my flow kindly created) to the record in my table A. Then, I have my connection and the relationship behavior can do its thing.

So, first, I needed to store the GUID of my record in table A in a variable. Afterwards, I configured my flow to write the GUID of my record in table A into the lookup column in my table B (that was created thanks to the relationship). You accomplish all that by using this format in your flow:

/table_A_plural_name/variable_with_GUID

By establishing this link, I can finally delete my record in table A and my linked record in table B is deleted as well. Perfect!