Skip to main content

Notifications

Power Apps - Microsoft Dataverse
Answered

Default Owning Business Unit to that of parent table

(0) ShareShare
ReportReport
Posted on by 13

Suppose I have two tables: Project and its child Issue. The relationship is one to many.

 

I want the records in Issue to have the same Owning Business Unit as that of its parent Project, instead of the business unit of the user who created the issue. How can I achieve that?

Categories:
  • kazut Profile Picture
    kazut 13 on at
    Re: Default Owning Business Unit to that of parent table

    Got it! Thanks again so much.

  • Fubar Profile Picture
    Fubar 7,637 on at
    Re: Default Owning Business Unit to that of parent table

    @kazut wrote:

    We don't really assume any changes of owning business unit, but wonder if "Parental" behavior works instead of your third bullet?

     


    Parental has them all set to Cascade All except for Rollup.  Unfortunately the new interface doesn't display all the individual relationship behaviors like the Classic interface does (except for when you have chosen Custom)..

  • kazut Profile Picture
    kazut 13 on at
    Re: Default Owning Business Unit to that of parent table

    Thanks! I was able to use the Table Mapping (your second bullet) to make it work.
    https://learn.microsoft.com/en-us/power-apps/maker/data-platform/map-entity-fields

    We don't really assume any changes of owning business unit, but wonder if "Parental" behavior works instead of your third bullet?

     

     

  • Verified answer
    Fubar Profile Picture
    Fubar 7,637 on at
    Re: Default Owning Business Unit to that of parent table

    First question is do you need to maintain it over time or just when it is created?

    • 'server-side' For on create, create a Plugin, Workflow, or Flow and on create copy from the parent (plugin or workflow if needs to be realtime).
    • If only need 'client-side' in model driven app, Switch to Classic and update the relationships' Relationship  Mappings and map the ownerid.
    • For changes that may occur later, Edit the Relationship and under Advanced set its 'Assign' Cascade Rule to cascade e..g. Cascade All (note the cascade does not apply to the initial create, just subsequent owner changes on the parent)

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

End of Year Newsletter…

End of Year Community Newsletter…

Tuesday Tip #12 Start your Super User…

Welcome to a brand new series, Tuesday Tips…

Tuesday Tip #11 New Opportunities…

Welcome to a brand new series, Tuesday Tips…

Leaderboard

#1
WarrenBelz Profile Picture

WarrenBelz 144,609

#2
RandyHayes Profile Picture

RandyHayes 76,287

#3
Pstork1 Profile Picture

Pstork1 64,420

Leaderboard

Featured topics