Populate values in drop downs based on previous user selections

komalc3

A Score Level 1

over 7 years ago

Hi

I am working on version 16.2.

I have the below requirement to be fulfilled.
1st user selects a country from a drop down (whose values are being populated from a constant).
Now based on user's country selection, a list of regions should be fetched from backend and this should be displayed in a new drop down called "Regions" under the "Country" drop down.
Next when user selects a region, then based on the combination of country and region selected in above drop downs, a list of products should be fetched from the backend and this should be displayed in a new drop down called "Products".

Here I am desriing only 3 drop downs, actually there are more than 10 such drop downs, wherein based on selection of one or more drop downs the values in the next drop down is populated.

The traditional way is using expresssion or query rules but it will adve...

Discussion posts and replies are publicly visible

Parents

0 sikhivahans over 7 years ago

@komalc In the some of the comments, it was being suggested that the data should be maintained in load. If the datasets are huge, I would suggest refraining from doing so as there is a chance of performance degradation again if we keep on placing lots of data in the load(). Let's take an example as per your scenario - Invoking 10 query rules in the load() at a time versus on-demand querying(that too one query rule) per one interaction(that is in the saveInto). As per my knowledge, obviously the earlier one shows a significant impact during the form load and I don't think it's worth doing so. I opine that opting for load()/with() has to be done by analysing the situation rather than going for load() unthinkingly . But again, let's see what others opine on this.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 sikhivahans over 7 years ago

@komalc In the some of the comments, it was being suggested that the data should be maintained in load. If the datasets are huge, I would suggest refraining from doing so as there is a chance of performance degradation again if we keep on placing lots of data in the load(). Let's take an example as per your scenario - Invoking 10 query rules in the load() at a time versus on-demand querying(that too one query rule) per one interaction(that is in the saveInto). As per my knowledge, obviously the earlier one shows a significant impact during the form load and I don't think it's worth doing so. I opine that opting for load()/with() has to be done by analysing the situation rather than going for load() unthinkingly . But again, let's see what others opine on this.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data