- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2016 08:42 AM
I created a UI Page that asks two CIs. In a regular record I would give them the attributes
- ref_auto_completer=AJAXReferenceChoice
- tree_picker=true
Now, I want to do the same on a UI Page. I have looked a bit for this, and cannot get any further than two regular reference fields. I cannot get them to behave like a dropdown or tree-picker. So I was wondering whether this is even possible?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2016 09:47 AM
Hi Peter,
Fields on UI pages may not support all attributes supported by the built in counterparts. For best information, take a look at the comments section on the UI macro corresponding to that field. For example ui_reference

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2016 09:47 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2016 11:14 PM
Yeah I already did, but was hoping for an alternative I guess there was none. I'll try to find a workaround then, thanks.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-21-2016 06:22 AM
Such is the fun of UI pages and UI macros.
If I have answered your question, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.
If you are viewing this from the community inbox you will not see the correct answer button. If so, please review How to Mark Answers Correct From Inbox View.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-05-2019 05:45 AM
It seems that after few years the problem is still not solved. I think ServiceNow doesn't support Jelly anymore, that's why.
But... Is there any workaround? Perhaps there is a way to force changing the target attribute autocomplete="off" to "on" (by modifying DOM directly, after processing UI Page with <g:ui_reference> tag).