Cascading Lookups need re-work
Currently building cascading lookups is cumbersome and very restrictive in where I can get data from. Having to create separate lists for populate the cascading values is not sustainable. I should be able to populate Form variables to filter and pull data from, also should be able to filter and get choices from unbound choice fields. Also the postback that currently happens is a real deterrent from using the controls. Re loading the form and having to scroll back to where you were at, isn't a very good user experience.
Thanks for your suggestion Dan.
We will certainly be considering how cascading lookups are configured when we rebuild the List Lookup control for Universal Forms.
If you have specific feedback regarding your experience, please provide it in the comments section below.
Rhia Wieclawek commented
I'd like to see the options in the List Lookup to be able to "remove duplicate values". I have a case right now where I have the user choose an item from a dropdown (say, a baseball cap) and then the next lookup populates the size, and maybe another populates the colour. Then, each of these combos determines the item code selected. It's sounding like I'm going to have to create a list for item, and then item description ... would love to be able to also filter on multiple values. Ie, "bring back the item code for when the item "baseball cap" is also "red" and "medium" without having to code.
Yes. My user is complaining on the control's postback. Please improve the experience.
Nicole (Prestby) Vesser commented
I agree! The postback in particular is a very jolting user experience.