Hi Everyone,

Coming back on @lottemint.md reply, I wanted to clarify something on my side. I just encountered huge performance issues by having a very large record inside a Client record, causing the entire client page to be slow and querying really slow.

I switched to Do a search for Billing Records, instead of Current Page’s Client Billing Records, the billing records has 11,000 records in it.

Targetting current user took about 2/3 minutes, doing a search for took me about 1/2 seconds with extended vertical scrolling :axe:

From now on the best method will be to do a search for very big lists of data while at the same time targetting Current User’s data only when that data is not a list. Also inside each data table, I will remove all association to the data type Billing record to avoid performance issue.

@lottemint.md Thanks man, you were a hundred percent right and I was wrong on this. Strangely enough, I tried to replicate this on another app with a lot more records and haven’t seen any issues. I guess it’s becaused I’ve stacked Billing record inside multiple data types, causing a major pile of data loaded on the page.

4 Likes