For Each Logic In Flow Designer

[ammar_k]

Hello everyone,

I have a field of type List on my Project form that allows selecting multiple managers (users).
What I’d like to achieve is:

• When the project is submitted (or reaches a certain state),

• An approval request is sent to each manager that was selected in this list field.

I’m not sure what is the best way to configure this. for each logic doesn't seem to work

Has anyone implemented something similar, or can share best practices for this scenario?

Thanks in advance!

[Nishant8]

Hello @ammar_k, if you have all the managers already available in a field then you can simply use that field in the 'ask for approval' rule, something like below:

Regards,

Nishant

[Nishant8]

Hello @ammar_k, Yes, if you already have all the users, you can simply add them to your Approval Rule. I'm not sure if you missed my comments where I mentioned the same yesterday.

Regards,

Nishant

[M Iftikhar]

Hi @ammar_k,

If you want a clean way to handle multiple approvers, one approach is to normalize your list field into separate records.

e.g., when the project is submitted, create entries in a “Project Approvers” related list one for each selected manager. Then your approval flow (or even standard approval engine) can trigger off that list.

This avoids the limitations of Flow Designer’s For Each with list fields, and also gives you better tracking and reporting of each manager’s response.

Thanks & Regards,
Muhammad Iftikhar

If my response helped, please mark it as the accepted solution so others can benefit as well.

[ammar_k · Accepted solution]

Hello everyone,
Thank you for your answers.
It seems that you can simply add a list-type field to the approval in Flow Designer, and everyone in that list will be asked to approve.