Hello,

Can you clarify a bit? When you call the split for each, you have a pagelist of objects and you are iterating through them and calling a flow? Is that not the primary page of the flow you call? Is the question about populating the page list or are you seeing some other behavior, or am I misunderstanding your question entirely?

Thanks,

Mike

Hi,

I am iterating split-for-each with pagelist, each page of pagelist considered as primary page of flow. I am interested to utilize page property when flow is getting triggered.

i.e. Pagelist : ProductList

ProductList(1) - prod id: 1, prod name: Router, prod cost: $100

ProductList(2) - prod id: 2, prod name: IPVPN, prod cost: $200

ProductList(3) - prod id: 3, prod name: FireStick, prod cost: $300

When I pass this pagelist as input on Split-For-Each. a primary page on which a new flow which triggered is not having Prod id, prod name, prod cost property and its values.

I believe you are able to relate now. Please let me know if need elaboration on it.

Thank you.

Ah. So the list is not a list of persisted objects, just pages with data? I that case, I would expect the persisted object to continue to be the primary page (though I haven't tested to confirm). If you just want to act on those pages, can you call a utility shape and iterate through them in a data transform or activity? What does the flow that you are trying to call from the split for each do? Does is ultimately created a persisted item/create assignments/etc or can it be called from the utility shape on each page, do its processing and return for the next item in the list?

Thanks,

Mike