Microsoft Dynamics 365 | Integration, Dataverse...

On-demand flow running on the same records

(0) Share

Report

Posted on by SBeal

I have an on-demand flow that is set up to allow users to resolve incidents in bulk, by performing a bound action.

The flow works as intended when I or another System Admin use it, however when a user with lower privileges uses the flow, they appear to only be able to run it on the same records as when they first ran the flow. When they select different records, the flow "runs" but I can see from the run history that it is not using the GUIDs that were selected by the user (and is instead running on the previous GUIDs).

I assume that because Sys Admins can use it as intended, it is a permissions issue.
The user in question has the following permissions on the Process entity:

Can anyone tell me what needs to be changed?

Thanks in advance,

Simon

I have the same question (0)

All responses (6)

Answers (0)

Nya 29,060 on at

Like (0)

Report

Hi Simon,

If these low privileged users can indeed reprocess the previous records once when running this flow, the issue should not be related to privileges of Process.

It's mostly likely to do with the specific steps in your flow.

As your flow is performing a bound action, it is likely that these low privilege users do not have Append or Append to permissions for this entity, and the previously processed records look like they have been reprocessed because they have been bound.

If it's convenient, you can share the steps in your flow, the Entities involved and the permissions low-privileged users have for those Entities.

Or you can share the run history of some low-privileged users in this Flow to analyze whether records that have already been processed are actually being processed in duplicates.

Was this reply helpful? Yes No
SBeal 50 on at

Like (0)

Report

Hi Nya,

Thanks for your reply.

The users have full (excluding delete) privileges on the Incident entity, which is where the bound action is.

The users also have Append and Append to (business unit) permissions on the related entities (e.g. Note).

I originally thought it was related to the flow steps, however I looked at the GUID that the TriggerOutput was passing to the rest of the flow, and it appears that the flow run is repeated rather than an action in the flow acting on the wrong GUID. (i.e. the GUID in the trigger output is the same, not the newly selected records).

Simon

Was this reply helpful? Yes No
SBeal 50 on at

Like (0)

Report

I've just got a colleague to run it on a basic flow that just composes some details from the selected records.

You can see the user did 3 records with the first "run", then selected a different 3 records for the second "run" - but the flow ran 6 times instead of 3 (repeating the first 3 runs).

Was this reply helpful? Yes No
Nya 29,060 on at

Like (0)

Report

Hi Simon,

Here is my test result:

With a low-privileged user, the records will not be run again.

Here is my flow. It is simply getting the GUID of the selected records.

Would you please try to adjust the flow into the above way to locate whether the problem is caused by steps in the flow or not?

Was this reply helpful? Yes No
SBeal 50 on at

Like (0)

Report

Hi Nya,

This is the flow I got my user to run this morning:

Which produced the success/failure results in my previous post.

Thanks,

Simon

Was this reply helpful? Yes No
Suggested answer

SBeal 50 on at

Like (0)

Report

This issue apparently resolved itself after I opened a ticket with Microsoft, helpfully!

Was this reply helpful? Yes No