Getting dropdown to load faster - dynamic values

domreg · 2024-10-15T11:08:40.242Z

Hi,

I am having a problem with the dynamic dropdown field. I have a total of over 8,000 records in my repeating group.

I am getting my dropdown values from my repeating group, as shown in the image below.

image817×721 63.1 KB

When I load the live site, it takes a long time for the dropdown field to display the values.

image554×838 43.5 KB

Is there a way for me to display the first 50 records initially, and then subsequently load the rest of the values? This would allow my users to start searching for quotation titles instead of waiting for the field to populate.

I really need help with this, as my app has 8 years’ worth of data and counting.

Thank you!

Alvin.

ihsanzainal84 · 2024-10-15T11:14:14.436Z

I store lists into states. What i usually do is load the search item until#xx and then schedule a custom workflow that will load the rest and then merge them into the state. Schedule a custom workflow is the closest thing to clientside synchronous functions.

Run the grouping operator outside of the dropdown as that will also incur a processing time cost.

domreg · 2024-10-15T11:19:21.502Z

Hi @ihsanzainal84

Thank you for the helpful information! I appreciate your guidance on storing lists in states and scheduling a custom workflow. However, I could use a bit more assistance to fully understand how to implement this.

Could you please provide more details or examples on how to set this up? Your expertise would be greatly appreciated!

Thank you again!

kirsnvartem · 2024-10-15T14:59:16.975Z

Hi @domreg,

What I usually do in this situation is exactly what you mentioned—load an initial set of items (e.g., 50) and allow the user to load more. Here’s how I approach it:

I set up a group containing a repeating group and a “Load More” button. I also use a scroll plugin—personally, I use the ScrollActions plugin from Thimo, but there are other options available as well.

The idea is to set a custom state on the repeating group, naming it something like showTo. This state will be updated when the user clicks the “Load More” button. The button itself will only become visible when ScrollActions detects that the user has reached the end of the container (essentially when they’ve scrolled to the bottom of container). This way, the scroll position triggers the visibility of the button.

It works like a charm for me. Let me know if you need more help setting it up!

Best,

Artem

domreg · 2024-10-16T05:52:40.382Z

Hi @kirsnvartem
Thanks a lot for the guidance. I’ve done it, but using a different approach.

image833×877 31.6 KB

Thanks so much! I couldn’t have done it if you hadn’t replied to my post.

Thanks again!

system · 2024-12-24T11:08:50.045Z

This topic was automatically closed after 70 days. New replies are no longer allowed.