We’ve been working with Glide to automate our internal processes for the last few months. A couple of elements use Big Tables - hour logging and ticket updates. When we started to work on a client-facing app, we discovered that these can’t be linked across apps like standard Glide Tables.
We’re exploring the option of transferring the data to Google Sheets - which has a 5 million row limit rather than Glide Tables’ 25k limit - but I’m concerned about potential performance limitations.
Has anyone here tried to run a large database like this from Google Sheets? We’re logging about a thousand rows per month on ticket updates at present, so this will build up pretty quickly.
An alternative that occurred was to use the API to request data from these tables in the client app via a webhook, which might be more efficient, but will definitely be slower to build. Again, it’d be great to hear from anyone in the community with experience of this.
Well - on ticket updates, we’re going through around 500 rows per month but this is likely to rise as adoption of the system increases. We could do a data clean-up every two years, I suppose. For hour logging, we typically log around 60-90 entries a day, so perhaps 1,500 per month; this is likely to fill up pretty quickly on a standard table.
Thanks again for your assistance on this, by the way - it’s appreciated.
You do? I don’t: they don’t show up in the ‘Link Tables’ menu at all.
Although, strangely, the Worklog Run Log and Worklog Step Logs do show up from the original app, along with another big table from a test app. So maybe I’m missing something here! Thanks for the heads-up, Lewis.
