
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2019 04:29 AM
Hi
I have a Flow Designer Flow that uses the Service Catalog plugin and in that gets Catalog variables one of which is of type List Collector and contains sys_user records. When - in a Flow Designer ForEach Loop - trying to reference the email attribute on each sys_user record iteration, I cannot expand it, and it's titled "Item" while being greyed out as well. At some point during my fiddling around the record was suddenly recognized as a user object though that did revert after a Test run that failed at the specific step where I expand the ForEach user object reference.
Can anyone share any insight on the matter?
Thanks,
Anders
Solved! Go to Solution.
- Labels:
-
flow designer
- 16,857 Views

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2019 11:57 PM
No problem, I'm still a newbie so if this doesn't work, apologies!
So my example is, I have a Service Request that captures multiple accounts within the list collector. We then use this to generate flows and processes for each value in the list collector, so need to be able to select values from the accounts table.
Mine goes (screenshot attached too):
Trigger - Service Catalog
Action 1 - Get Catalog Variables from [Request Item] (pulls in List Collector field)
Action 2 - Look Up [Account] Records where Sys ID = [List Collector Field (from Action 1)]
Action 3 - For Each [Account Record] (from Action 2)
For me, this kept the 'For Each' record as the Account Record, that I could expand and take the data pills from when needed.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2019 12:17 AM
Hi - I had the problem where my For Each Record kept reverting to 'Item' and not letting me expand to the record fields.
Do you have a 'Look Up Records' action within your flow? If not, you need to create this action against the sys_user table using the list collector shown. The collector is selecting the accounts you use, so you'll then need to get the records from the relevant table.
You'll also need to add a condition to your action to pick up the records, for example sys_id = [name of list collector variable] to retrieve the records you need, which should then progress through your 'For Each' actions.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2019 07:23 AM
Hi Natalie
Thank you for commenting this!
"Do you have a 'Look Up Records' action within your flow? If not, you need to create this action against the sys_user table using the list collector shown. The collector is selecting the accounts you use, so you'll then need to get the records from the relevant table."
I didn't have a "Look up Records" action within my flow, so I tried a lot of different approaches none of which worked. I must confess that I am not entirely sure that I get your instructions.
I have an active HI-case and they see the same behaviour, though they themselves can't figure out why the list Collecotr variable sometimes expands and sometimes dont (we can't reproduce it).
Could you please point out exactly the steps (screenshot maybe?).
Thank you!
-Anders

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2019 11:57 PM
No problem, I'm still a newbie so if this doesn't work, apologies!
So my example is, I have a Service Request that captures multiple accounts within the list collector. We then use this to generate flows and processes for each value in the list collector, so need to be able to select values from the accounts table.
Mine goes (screenshot attached too):
Trigger - Service Catalog
Action 1 - Get Catalog Variables from [Request Item] (pulls in List Collector field)
Action 2 - Look Up [Account] Records where Sys ID = [List Collector Field (from Action 1)]
Action 3 - For Each [Account Record] (from Action 2)
For me, this kept the 'For Each' record as the Account Record, that I could expand and take the data pills from when needed.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2019 02:31 AM
Hi Natalie
The screenshot you passed instantly helped me understand how you thought the logic (sys_id "is one of" <Collector List variable>). I never noticed the "is one of" choice during my research.
Thank you for your time spend - you're an angel 🙂
-Anders