Power Dynamics
  • Power Dynamics
  • 🍕My name
  • D365 CE
    • Copilot
      • 🥐Add Copilot into Rich Text Control
    • Sales
      • Copilot in D365 Sales
      • Export record to PDF
    • Customer Experience
      • Contact Center (Omnichannel)
        • 🐚Internal Live Chat in MDA
        • 📢Add Chat Widget to Power Pages - Proactive Chat
      • Attachment Control
      • Case Routing: Basic Routing rule set
      • Custom SLA for any Entity
      • Customer Insight
        • Journey - Custom Trigger - Call Power Automate
    • Field Service
  • Power Platform
    • Analytics
    • Dataverse
      • Use case for the feature of Record ownership across Business Unit
      • 💡Workaround: Change the OOB "Exchange Rate" of a record
      • Using a Virtual Entity to store historical log (sample)
      • Disable Empty Address record
      • Using Adaptive card
      • Block Unmanaged Customizations
      • 🪃Recycle Bin on Dataverse (Preview)
    • Model Driven App
      • 💡Run SSRS report on MDA mobile
      • 💡Tip: Create a Security Role with "App Opener" minimum privileges
      • Tag @person to notify in MDA
      • Auto search on the Lookup field
      • Activities with multiple related records
      • Embedded Power BI - Dashboard
      • Embedded Power BI - Form
      • "Custom Help" - Is it help?
      • New modern Command Bar
      • Tip: Hide the button "Add Existing Record" on subgrid
      • Custom Page - Why not?
      • Hiding sensitive column data
    • Canvas App
    • Fabric & Power BI
      • New Text slicer
      • Dataverse link to Microsoft Fabric
      • 💡Leveraging Interactive Warehouse Floor Maps in Power BI
      • Calculation Group for Time Intelligence
    • Power Automate
      • ✅Sequential Approval
      • 📤Create an Appointment by Outlook Graph API
      • Dowload SSRS Report and Send email
      • Power Automate: Add a table in Email
      • 💡Tips: Get "DisplayName" of the Lookup field on Power Automate
      • E-sign: Power Automate & DocuSign
  • D365 Finance & Operation
    • General
      • 🇻🇳D365 FnO - Virtual entities: Use case
    • Finance
      • Consolidating Customer & Vendor Balances
    • Supply Chain
      • Landed Cost Series
        • Landed Cost- Essential Configuration
        • Landed Cost Scenarios 1
Powered by GitBook
On this page
  • Scenario
  • How to enable & configure it?
  • Assign Security Roles for the User
  • Checking permission of the User
  • How to enable the field "Owning Business Unit" on the form for all entities?

Was this helpful?

  1. Power Platform
  2. Dataverse

Use case for the feature of Record ownership across Business Unit

#configuration, #security, #permission, #crossBU

PreviousDataverseNextWorkaround: Change the OOB "Exchange Rate" of a record

Last updated 8 months ago

Was this helpful?

Today, I would like to share an existing configuration on the Power Platform Admin Center. This feature is regarding record ownership impact on the permission of the user.

Scenario

Firstly, let's see my scenarios as picture here

User A is working for 2 BU: BU1 and BU2. However, as my scenario flows, this User was assigned different roles for each BU.

How to enable & configure it?

Go to the Power Platform Admin Center > select environment > into the Feature area, turning on the feature "Record ownership across Business Unit".

Once enabled:

  • Allows you to assign security roles from different business units to a user.

  • Users can have different roles for each BU assigned.

Assign Security Roles for the User

To assign security role for a User for different BUs, you go to the Power Platform Admin Center. After that, go to User + permission area >> click User >> then select specified User (ex: TEST HS) and click Manage security role, then select BU and assign roles for the user.

Activating the Record ownership across BU feature resulted in the Business Unit field being enabled, whereas it was previously disabled.

Please review the test security roles listed below. Following that, I will present the testing results for this feature. My test role: Salesperson-X and Salesperson-Y

Checking permission of the User

First, I logged in by user Admin and checked the data of Account entity as bellow.

  • Total account records: 33

  • Accounts of BU1: 04

  • Accounts of BU2: 5

Now, my expectation when log-in by user TEST HS:

  • Can see 9 Accounts of Child BU 1 & Child BU 2

  • Can Edit Account of Child BU 1

  • Cannot Edit Account of Child BU 2

... and then my testing Result

Open the account record of each BU for permission testing

How to enable the field "Owning Business Unit" on the form for all entities?

I will now reveal a concealed setting that activates the Owning Business Unit field on the form for all entities. Once this field is enabled, users can create an Account record and then assign it to a different Business Unit to which they are assigned.

Before enabling this hidden setting - the field Owning Business Unit was set Read-Only. So, the user does not assign this record to a different BU.

After installation, navigate to the solution within the configuration area and set the 'RecomputeOwnershipAcrossBusinessUnits' setting to 'true'. This will enable the 'Owning Business Unit' field to be modified and the user can assign account records to a different BU.

Let checking.....

Hoping well and thank you! [NTD]yns.Asia

After that, we will enable the hidden setting of the . You must install a solution - OrgDBSettings tool at the .

Tadaaaa... That's all today.

🎉
Environment Database Setting
link
Scenario
Enable feature
Assign roles for different BUs
Data of Account entity - View by Admin role
Total Accounts = 9 record
Testing Permission result - of TEST HS user
Before - enable hidden feature
Set “RecomputeOwnershipAcrossBusinessUnits” = true
Testing - after enable hidden setting