Reference Qualifier vs auto-populate filtering
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
Hello,
I have this by the look, very simple business requirement, but I do struggle with it.
For one of the catalog item, there's a requirement to show in field "Organization" only those departments, which have parent = empty and code!=obsolete (modified field). However, this filtering is working, except that this variable in the catalog item is still showing "auto-populated" value from settings of the variable (dot walk of department from sys_user table).
So even if the reference qualifier "pass" these values, it always show auto-populated value whether it is obsolete or not.
Can you help me, if I can somehow setup it differently via catalog client scripts/different settings in variable in order to show correct list of valid departments? Auto-populated settings should be still in place.
Currently as it is, field is not auto-populated but it shows all valid fields as list (from Lookup select box).
Thanks in advance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago - last edited 2 hours ago
@martinkruml , You can check the "include none" checkbox from type specification related list tab.
If this solution helped you Please Mark this solution as accepted and helpful as it will be helpful for other users as well.
Best Regards.
Saurabh V.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi @martinkruml , As per my understanding the variable is auto populating some information in the reference field from lookup table in the starting. To tackle this you can use check the "include none" checkbox from type specification of that variable so the default value will be shown as "none" in the beginning. Instead of a random value from lookup table.
Let me know if I have understood it correctly or not.
If this solution helped you Please Mark this solution as accepted and helpful as it will be helpful for others as well.
Best Regards.
Saurabh V.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi,
That is correct and that is how it is working at the moment.
However, before modification of putting "code!=obsolete" there it worked as it should.
Field was "None" and you had to choose from a list (from lookup select box) desired department.
When I put condition parentISEMPTY^code!=Obsolete, the field now showing automatically auto-populated field + only the department, which is parent department of the user, but this department is also =Obsolete, which is wrong.