- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-31-2023 04:37 AM
Hi everyone!
I am finding myself into a situation where I have a table with simple fields {name | number | sys_id}.
I created a catalog item that has a Lookup Select Box to get the values from that table.
Moving forwards, I created a flow to handle the submission of this request.
My issue is that when I pull in the variables from the catalog, the variable in question is of type 'choice' but displays no values inside of it? So, on a condition of 'if (get catalog variables -> var1) | is | --none--' , the '--none--' will have no other choices to select.
I tested as well a copy of itself using only a Select Box, but my issue with this is that on the Catalog Item, I can't bring the table where the records are for choice, and therefore I have no choices displayed (unless I create those choices manually onto that variable configuration page). But I don't want this, I need the user to be able to input those new choices via record. And the Lookup Select Box is perfect for this!
But yeah.. I can't get the choices onto the flow.
Any ideas how I can make them appear?
regards,
Darius
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2024 05:57 AM
Lookup Select Box is not supported. https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0962980
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
My workaround is making a flow variable of type String, then returning the lookup select box value to it in a script using the trigger and avoiding Get Catalog Variables. For example, the script to set the flow variable would simply be:
// Substitute "variable_name" with the name of your variable
// This will return whatever the Lookup value field is set to.
return fd_data.trigger.request_item.variables.variable_name + "";