3 ms·
Have you thought about auto-installing https://developers.google.com/apps-script/guides/triggers https://developers.google.com/apps-script/guides/triggers into
by btown 3y ago
Have you thought about auto-installing https://developers.google.com/apps-script/guides/triggers https://developers.google.com/apps-script/guides/triggers into the connected sheet, and maintaining a cache of the data that you invalidate onEdit? Would likely improve read latency dramatically, though it would make reads eventually-consistent.
To others seeing this - has anyone else ever tried this approach? Are there players out there who do this and have SOC II etc. data security measures?
- jpgvm 3y agoDisclaimer: I work at Glide but not on Google Sheets integration. Triggers/AppScript - not that I am aware of right now... Everyone I know doing stuff with GSheets (including Glide) is using a full-sync approach with an optimistic write layer of some sort. GSheets API frequently reports being unable to do things, sometimes because it's calculating (common for huge sheets), sometimes just because it's down, other-times because rate limits My impression is it's not a great API to build on directly. A trigger based system that captured writes and wrote them to an outbox sheet could drastically speed up the sync process however. The reason why we don't use that approach is there isn't APIs sufficient to setup this sort of thing automatically (last time I checked at least) and it makes changes to the users sheets which isn't impossible to live with but is distasteful.