Automatically Assign the Owning Business Unit of Child Records Based on Parent Record

(0) Share

Report

Posted on by CS-24071844-0

Hello,

I have a model-driven app with child and grandchild records relating back to the parent record.

For example:

Entity 1: Cases = Parent

Entity 2: Actions = child of "Cases" entity

Entity 3: Measures = child of "Actions" entity

When a new item is created in the Actions entity or Measures entity, I want either the Owning Business Unit of those records to be automatically assigned to the Owning Business Unit of parent record (Cases entity).

I have enabled 'Record ownership across business units' and can manually assign these records a Business Unit.

I have users tied to Business units and attempted to set a business rule to assign the field value of Owning Business Unit to the record Owner's Business Unit but was unable to find Owning Business Unit in the field choices.

I am not strong in Power Automate but am trying to figure out how to do this here as well.

I'm wondering if I can turn off ownership at the individual level and set it to be Business Unit or Team only....?

Any help is greatly appreciated!

Thanks!

@AhmedSalih have you come across this?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (5)

Answers (0)

Sort by

AJ_Z 3,711 Super User 2024 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Make sure in your environments admin centre you have turned on the feature:

Record ownership across business units (Preview)

go to Power Platform admin centre.

click the environment

click settings

click product

click features

I use this feature a lot and use power automate to automate picking the relevant owning business unit. However, be advised this feature is still in preview.

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

Like (0)

Report
Copy link

Link copied!

Please note, the previous post is for a Preview feature, preview is not recommended for Production implementation until they become General Availability.
Not using preview, would usually do this with a Workflow, Plugin or Flow depending on the specifics of your need. Asynchronous/background Workflow, Plugin or Flow if not needed immediately (e.g. could take a couple of minutes), Synchronous/real-time Workflow or Plug-in if needed immediately.
Also, may want to look at the relationship Cascade Rules for scenarios where changing the Owner of the Parent after creation also needs to cascade down to Child records.

Was this reply helpful? Yes No
CS-24071844-0 80 on at

Like (0)

Report
Copy link

Link copied!

Thank you @Fubar - Do you have experience creating a flow that would work asynchronously?

Was this reply helpful? Yes No
CS-24071844-0 80 on at

Like (1)

Report
Copy link

Link copied!

Thanks @AJ_Z - It does work w/ the preview feature but I am concerned about pushing to prod.

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

Like (0)

Report
Copy link

Link copied!

@CarrieSperls wrote:
Thank you @Fubar - Do you have experience creating a flow that would work asynchronously?

The Dataverse trigger in Flow is only asynchronous, to get something synchronous you would need to have the Flow trigger as a HTTP Request and put something together to call it and pass it the record id - a lot easier to just do a real-time Workflow.

Was this reply helpful? Yes No