Workflow record creation record ownership

[Robert_vbc]

I have inherited a workflow that copies data from one table to another.

The system has a root business unit (in which the process runs) and some child BUs that own the records

Once the process runs the newly created records are owned by the root BU.

Is it possible that when the process runs, it does so as the user/BU that created the original record

and hence the new record keeps the ownership information the same?

[Robert_vbc]

The jpg above shows the scope as being Business Unit, it is actually Organization. I'm just trying everything I can think of to get this to work....

[ChrisPiasecki · Accepted solution]

Hi @Robert_vbc,

Background workflows will run as the owner of the workflow. If you want it to run as the user who triggered the workflow, you can either:

• Change the workflow to a real-time workflow; OR
• Recreate the workflow as a Power Automate workflow and configure the Dataverse trigger to run as the user who triggered the workflow. The flow will still run asynchronously in the background just like your classic workflow behaves now. 

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

[Fubar]

FYI: Scope on the workflow is part of the conditions when the Workflow will run (be applied), based on who owns the record. and who is initiating the trigger for the workflow.

"For user-owned entities, options are Organization, Parent: Child Business Units, Business Unit, or User. For Organization-owned entities the only option is Organization.

If scope is Organization, then the workflow logic can be applied to any record in the organization. Otherwise, the workflow can only be applied to a subset of records that fall within the scope."

[Robert_vbc]

Thanks Chris for the pointer to using power automate and a trigger. this is exactly what I need to do,

unless I duplicate the process in each BU and have it owned by an account within the BU (and that would suck duplicating the process).

[Robert_vbc]

I have found an alternative solution, just setting the Owning Business Unit field to the same as the old record will not work, but if your process sets both the Owner and the Owning Business Unit field to those of the "source" record the newly created record will be created with the Owner and owning BU that you want.  Actually makes total sense that you cannot just set the owning BU.