Thank you! Iāll check it out now.ā¦
Interesting. It will take me a few tries to dissect what you did there! I have one question.
I see that your RG has the Data Source as Drag It Aā RG Sync Source instead of Drag It Aās Updated List. Is this because Listopia now has the updated list (syncād to the Drag It) and the source changes based on whether the list is filtered or not?
Iām just trying to understand whatās going on so I can repeat this both now and in the future.
Thank you.
New questions.
Your primary source in the example is a RG. Does it have to be?
- I have my primary source stored as a sorted field in the DB, which I access through a related field on the current user:
Current users's Sortedlists' Actions
Can I just substitute this everywhere you used the RG?
- On the Keeper, you have a condition to use the Keeperās List Two when a state indicates the list is filtered. Do I have to use the filtered list from the Keeper List Two, or can I useā¦
Current users's Sortedlists' Actions:filtered
ā¦directly in the condition? In other words, I will check the state and when the state is true, change List Oneās Data Source to the filtered list.
The reason I as this question is because I have at least eight different filters that can be applied in all combinations. Iām hoping I can just keep the filtered list as a dynamic source.
If thatās not going to work, can I use more than one Keeper, or will I be tied to just one per Drag It/RG combination?
Iām asking all of this before trying it because Iāll need to restructure a lot to try it out and I donāt want to have to undo all of it if I know it wonāt be correct.
Thank you!
Update: I think I know a way to have a single filtered RG to cover all combinations of filtering. If this works, I will be able to follow the demo created.
Does anyone know of a good way to account for eight different filters that can be applied in all combinations? I really donāt want to create 255 conditions to cover all possible combinations. 
My first thought is to create a hidden RG for each filter. Make the source for each RG the previous RGās List. Then, using states, each RG will either filter or not. The last RG in the chain will have the final filtered list.
Is there a better way than keeping all of these extra RGās in memory?
If a list can be expected to have 400-500 items in it (it wonāt always, but itās certainly possible, hence the need for filtering!), will this become a memory or performance problem?
Iām just looking for the best way to apply multiple filters to a list when I donāt know how many, or if any, will be used at any time.
Thanks!