and what about if we could use the Favorite list as the choice component’s source of data?
If Favorites relies on per user data, each user will have his own list or options when a choice component is used.
In my case, I have a customer with 15+ vendors and 1500+ products (he will use a Pro plan of course). When a vendor generates a PO, he is going to use a choice component to select the right product and obviosly, to dig through a list with 1500+ products is something useless but, I can tell each vendor that at the begining, select his top 20 best products and put them to Favorite List and later, when he will load the drop-down list associated to choice component, he will choose only his top 20 products.
If the same vendor visits another customer later and the new order will involve other products not saved/listed in your Favorite List, he could add new products or eliminate old ones and create a dynamic list.
The 1500+ products could be the hard disk and the Favorite List the cache to work fast with any choice component.
The problem now is to find and work with that data marked as “Favorite List” which I think it’s saved as a cookie or on Glide’s servers.
If this data could be put/saved as a virtual tab in the DATA section of the Glide Editor, it will be fantastic and I could celebrate!
Who do we need to call to see if this tip makes some sense and could be implemented without traumas? I think it’s a feature easy to create
Well, these are my 2 cents to help to fix it!.
Saludos a todos @yinon_raviv @Jeff_Hager