- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-02-2015 05:50 AM
I've been looking through the WIKI/community and it seems like there is a bug with reference qualifiers on Lookup Select box variables. Does anyone know if there is a work around besides making the field a reference variable?
I have 3 variables on a form -- each dependent on the last. The first is a lookup select box and I'd like the second to be a lookup select box with a reference qualifier because setting it as a reference variable gives the same information as the third variable. I've tried only showing the columns I want (with attributes), but it still shows too much.
Is there another angle I can take? Building the list with a script? I only want to show unique values. Any ideas/help would be greatly appreciated because I think I've exhausted all the options I can think of. Thanks!
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-03-2015 06:35 AM
Seems like we all have been trolled here Look up select supports reference qualifier but it's not simple as reference field..
Check the wiki page
http://wiki.servicenow.com/index.php?title=Variable_Types#Lookup_Select_Box
We need to use 'ref_qual_elements' attribute to get the updated reference working..
I am able to do the dynamic thing working after adding the attribute...
Sample demo:
Create 2 lookup select variable called 'located_at' and 'user' referring location and user table respectively.
Idea here is to display the user depending on the location selected...
In the user variable, define reference qual as javascript: 'location='+current.variables.located_at; and variable attribute as ref_qual_elements=located_at
This will make the variable to use the updated reference. Try this out and let me know if this works for you as well.
Note: I tried on Fuji instance.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-03-2015 08:59 AM
I don't see a reason why not. Wiki says it works from Calgary
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-03-2015 07:30 AM
Way to go Kalai! I can't believe how many times I have overlooked that one. Nice work!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-03-2015 09:06 AM
I dint notice that either And I have implemented couple of solutions just that way you guys have stated Guess it's time for me to rework those
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-03-2015 10:12 AM
Kalaiarasan,
I am trying this out with little luck. I think it's because I'm having a hard time understanding:
I have 2 lookup select boxes pointing to the same table (is that an issue?). One called 'role_source' and the other called 'role'.
The 'role' variable has this ref qual: javascript:'u_role_source='+current.variables.role_source;
The attributes has: ref_qual_elements=role_source
I am getting values in the drop down, but they aren't dependent on what I select on role_source.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-03-2015 11:05 PM
Variables are pointing to which table? Can you provide a screenshot of the table structure?