Some ideas/comments for your consideration:
- Create a popup that you never open and call it “hidden popup for data”; add RGs and call them “data - things1”, “data - things2”, etc. As least RGs as possible of course in order to avoid unnecessary searches (… RG vs "Search for" (performance questions) - #6 by cmarchan)
- Populate your page RGs with the hidden popup “data things”. The reason for this is multifold but in short … your searches will be ready to go on page load as popups are always loaded on the page no matter what and you have the ability to add conditions to limit the number of items loaded.
- Always remember that whatever you place on an RG is going to multiply by the nr of loaded items. Example: If you have a dB model where a project has a list of milestones and you have an RG searching for projects … then every project you load is going to load all of its milestones. Each one with their multiple milestones.
- Structure your dB avoiding list fields as much as possible and rather relate things indirectly (example: project and milestone; milestone is related to the project only and the project does not have a list of milestones). If you make your objects “light” your searches will be fast.
- Depending on how you structure your data you can do things pretty performing. Example: Project with no list of milestones and no list of tasks, Milestone with a reference to its project and no list of tasks, Task with a reference to its milestone and to its project.
For further reference to why I laid out the above please refer to this resource (paid) created by a very experienced Bubbler @petter which is full of gold nuggets, and to this other great post by @lottemint.md also full of excellent suggestions and an active and experienced contributor to this forum as well:
Hope this sparks some ideas 