Looks Up Records not pulling records from List Collector

[Michael Graden]

I have a Catalog Item with a List Collector for the cmdb_ci_server table. Within the Flow, I have created a Look Up Records for this table with the condition Sys ID is one of server_configuration_items (List Collector data pill from the Get Catalog Variables step) > Sys ID. Though results are coming up 0. From searching other posts this appears to be the correct way, so not sure why I'm getting 0 results. We are also on Australia. 

 

 

 

Edit: Looks like there is an issue with the Look Up Records and List Collector variables. KB3146837 "Using a List Collector Catalog Variable as a Data Pill Results in "List is not allowed here" Error."

Resolution
☞ Until the permanent fix for the PRB is provided, please use the following temporary workaround:

☞ Disable the new predicate builder component.

Steps:

1. Create the following system property on the affected instance:

Property Name

Value

sn_flow_designer.predicate_builder_enabled

false

2. Save the property.

3. Refresh Flow Designer.

Note: This is considered a temporary workaround only.

[Vishal Jaswal]

Hello @Michael Graden 

The catalog variables stores the values of CIs, therefore you need to use Action "Get Catalog Variables" before the Look up records as shown below:

Validation Results:

[Michael Graden]

I guess I should have specified that I do have the "Get Catalog Variables" as the first step. Hence why I was able to select the List Collector variable within the Look Up Records action.

[anamariatam]

Hi @Michael Graden,

Since you already have Get Catalog Variables in place, I would check two things:

1. Remove the "> Sys ID" dot-walk from the pill. A List Collector variable already stores a comma-separated list of sys_ids, and the "is one of" operator works with that list directly. Build the condition as:

Sys ID | is one of | [Get Catalog Variables > server_configuration_items]

dragging the variable pill itself, without expanding it to Sys ID.

2. Check the flow's Run As setting. Open the flow properties and look at Run As. If the flow runs as the user who initiates the session, Look Up Records runs under the requester's ACLs, and a typical end user has no read access to cmdb_ci_server. I tested this on a PDI: a user with no roles querying cmdb_ci_server with ACLs applied gets 0 of 3 servers, while an admin gets all 3. If that is your case, set the flow to run as System User, or grant the appropriate read access, depending on your security requirements.

To confirm which one it is, open the flow execution details for a RITM where servers were selected. In the Look Up Records step you can see the condition as it was resolved. If the sys_ids are not there, it is the pill (point 1). If the sys_ids are there and the result is still 0, it is the ACLs (point 2).

Hope this helps!
https://www.linkedin.com/in/anatamayoservicenow/

[Michael Graden]

Thanks for the reply. I did try point 2 yesterday but had no luck. For point 1, the flow does not allow me to only select the list collector variable itself. It is greyed out and won't let me drag the data pill to the Enter values field. The flow only allows me to drill down into the variable, which the only logical attribute to choose from would be the Sys_ID. If I'm not missing something else, then this feels like a bug.