What is the best way to handle Multi Row Variable Set in Flow Designer?

[WaseemM]

Hi Guys,

I have a catalog that includes an MRVS (Multi-Row Variable Set). When I submit the catalog, the values are returned as an array, requiring me to use a foreach loop to process the request. I want to design the flow to handle a single instance, but if the catalog is submitted with multiple rows, the flow should trigger separately for each row. Essentially, I want to move the loop outside of the flow designer, as the flow is intended to operate on individual instances.

Thanks!

[Runjay Patel]

Hi @WaseemM ,

triggering separate flow for each item is not possible but you can create a sub flow and from main flow run a loop to trigger sub flow.

-------------------------------------------------------------------------

If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.

Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay

-------------------------------------------------------------------------

[Ankur Bawiskar]

@WaseemM 

if user submits a request 1 RITM will get generated and it will contain MRVS with 1 row or multiple rows

are you saying if user selects 2 rows then 2 flows should run?

This is not possible OOB and this is not how OOB service catalog runs and behaves

If my response helped please mark it correct and close the thread so that it benefits future readers.

[WaseemM]

@Ankur Bawiskar and @Runjay Patel, Thank you for your response. 

If a user submits a single request with MRVS, I want to create two child requests, each containing all its variables, and allow the flow to trigger separately for each child request (twice). Is this achievable without custom table?

[Ankur Bawiskar]

@WaseemM 

yes it's achievable without custom table

but I would like to understand are you having separate process/logic for each ROW of MRVS?

If yes then why not use single flow and based on value present in each ROW of MRVS have different logic in the same flow?