I have built a pretty heavy app for our company with data stored in Glide Tables. Having an issue where a page that gives a significant amount of information keeps reloading at random when our staff members are trying to enter in notes. It is becoming a problem as the notes get cleared every refresh. The refreshes are happening every 30 seconds or so. I know that there can be performance improvements in the tables, but is there a way to stop the page from reloading at random?
It is actually a page displaying information about a single row in a table. There are some list components filtering other tables, but they only display at max 5 rows.
I have seen this cause similar issues to those you have described in the past.
The thing is, in Glide the “Now” value changes every 10 seconds, so any columns that reference this value will be recalculated every 10 seconds. Easy way to test is to make sure no components that are displayed on the screen are referencing any such columns, and then see if that resolves the issue.
Wow - I never would have thought of that! I’ll make that change and see if it works.
Do you know if there is any other way to use only today’s date in a Math column instead of using the now value?
The only other way I can think of now is to create a “Today” table with a single Date “Today” column, schedule a daily Write webhook every day at midnight to write the date into that column, and reference that as a Single Value throughout the app. I just don’t know if a Math column will be able to read it in a similar way to the now value.
If you’re only interested in the current date (and not the time), then I would convert it to an integer in YYYYMMDD format, eg with:
Year(Now)*10^4
+Month(Now)*10^2
+Day(Now)
The returned value will only change once every 24 hours.
I should say that under most circumstances referencing the Now value should be perfectly safe and should not have any significant performance impact. And it may not necessarily be the culprit in your case. I just offered it up because I have seen it at least once. I can’t recall the exact circumstances, except that the 10 second update was triggering a chain of computed columns to be recalculated on a large number of rows, which resulted in a visible impact on the user experience.
One follow-up question: do you know if using the “Current time” selection in a Template column would yield the same refresh behavior as using Now in a Math column? It seems like I am using the former for a couple instances when I truly need the actual time by the minute.