Unanswered

Create large numbers of child records when a parent record is created

(0) Share

Report

Posted on by tkmcooper

Hi,

I am looking to build an app which will be used as a Task Management Checklist for Transactions. When a Parent record is created in a dataverse table (a Transaction), I would like approx 50 related child records to be created in a dataverse table (Checklist Items). These would have a number of columns pre-populated (e.g. Phase and Step - a Transaction has 8-9 phases, and each phase has several steps). I plan to store these in Choice fields which would have each combination pre populated in a distinct child record (e.g Phase 1 Step 1, Phase 1 Step 2 etc). Other columns would then be edited manually by the Transaction owner to assign a Checklist item to a specific user, a start date, comments, progress etc.

Is this approach possible? If so, how would this be achieved? I'm guessing an extensive Power Automate Flow or is there structurally a better way of approaching the build?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (1)

All responses (2)

Answers (0)

IanJB 93 on at

Like (0)

Report
Copy link

Link copied!

You could try creating a set of child records to act as a template set that you'll just copy through a flow, rather than making all ~50 from scratch as individual steps in a flow. Depending on how your security groups are set up it would be nice if the template records could be hidden from general users. Then when they create a parent record your flow triggers to simply pull and copy the children template-records. Then you could just do a loop to change the lookup field of the newly created records to the triggering parent (any maybe change owning business unit if you're doing that for access/visibility).

Was this reply helpful? Yes No
Fubar 8,487 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

I would go the Template route as suggested by Ian. Makes it easier for copying as you have a base "header' record to start from, and also allows you to have different templates without having to change the logic.

Because you are doing lots of records your best option is probably Flow (with workflow or plugin you would need to watch out for the 2min timeout).

Also, I would avoid using choices, do a lookup instead - reason for this is over time someone will want to remove a choice or add a new one and removing a choice is more involved than just deactivating a record in the table the lookup uses (and you can't just delete the choice as it will leave blanks in existing data), also adding a value to the choice requires a configuration change (and publishing/solution move) vs just adding a new record to the table the lookup is to.

Was this reply helpful? Yes No