Does the column say if it will use updates? Integrations will usually tell you if an update is counted or not. If it does say that it uses updates and it hasn’t counted any after applying it, it may be because the builder will not count updates in some cases. (Not sure if that’s the case for integrations or not.) I would say that normally if you have 2000 rows, then yes it will have to run that integration 2000 times and could subsequently count each run as an update. I would definitely expect that to happen with the published app.
Thank you @Jeff_Hager
Yes i would assume the same on a published app.
The integrations Glide have added are amazing… yet their pricing models make it very hard to use them on a large scale.
The coordinates to address feature for example is great for a friendlier UI when looking at a map. But applying it on a 2000 or 5000 table of assets could consume a big portion of our business plan at a glance.
Not to mention that the functionality is not clear, so if one of the rows is updated… does the integration call again to calculate all rows and consume another 5000 updates or just 1 update for the changed row.
Sometimes I wonder if anyone is actually using such integrations on large tables… or is it just something people demo on videos or sell to clients without notifying them of the update consumption they can expect.
It should only call again once on the row that’s been updated. Glide caches a lot of stuff. The only exception I can think of is the CallAPI where Glide only caches the data for up to a month unless otherwise specified.
If you are concerned about updates, then maybe it’s best to use the integrations as actions instead of using them as columns. Set the value once permanently and then change your flow to set or reset the value as necessary through actions.
I have the same concern. However, reverse geocoding can still be done in Google Sheets. What if dealing with dynamic data, like the example: the number of views from YouTube, Jeff?