Hey guys,
Assuming that either of these options would improve load speeds – which would be better? This assumes all things equal on a single page.
If this is too vague please let me know and I’ll elaborate.
Fewer conditionals and data pulls IMO. Unless your content is massive.
The only thing that slows my apps are repeating groups.
Also if you have called data into the app try to pull from on page data instead of multiple Do Search For’s. Seems to speed things up.
Thanks for the insight. This makes a whole lot of sense. I cut down the Do Search For’s and that helped a lot.
Hi! Thank you for sharing this.
However, what do you exactly mean with this:
‘‘Also if you have called data into the app try to pull from on page data instead of multiple Do Search For’s. Seems to speed things up.’’
How can I replace the do search for?
If you have already called the search item into one group, call it from that group instead of searching again.
GROUP A = Search for User
Text A (You want the users email) = Group A’s User’s Email rather than doing a search again.
Also, say you have a repeating group showing a list of grocery items you need to buy.
The Do a Search For way would have you set the data source for the repeating group as Search For, Grocery items, and then you would filter only items that are associated with the current user.
This way the system has to search every saved grocery item, and then display only the relevant ones. Meaning if there are a million data entries, it must search every one before returning a result.
Instead, if you saved the grocery items to the user as a list, you can set the data source for the repeating group as Current User’s Grocery Items List
Now the system only views the relevant grocery items and doesn’t have to search every single grocery item piece of data, resulting in quicker loading times for a repeating group.
Also, like it was mentioned, once you have done a Do a Search for on a page, try to re-use that information instead of doing another search for the same data.
Make sense?
I also found that if you decrease the amount of rows in a repeating group and use EXT Vertical that it can load the page faster.
