Hello Glide users ^^
I have a question about the updates / changes.
I have created an app that myself and about 20 people use every day.
With the app you can calculate the following things:
Pipe dimensions by medium and pipe type.
Axial distances according to pipe and insulation type.
Air velocity by ventilation duct cross-section, etc.
The settings for calculating one of the applications mentioned above are made in a detail tab.
This is true. Basically any change to your data, in this case, happens in the details view, will be registered directly to the database, and thus incur updates.
The only possible way to reduce this, I think, is to use a form instead, and have calculated columns to calculate the outcome. You will only have to use 1 update (form submission) that way, but it will also take 1 row from your row quota.
Thank you for the quick reply.
Redesigning the app so that everything is calculated via a form is very time-consuming and entering the values for the calculation is not very user-friendly.
Maybe creating an Excel is a better alternative.
Due to the limited updates, the use of Glide decreases dramatically.
Ten times more could be enough, but updating to the amount of updates costs too much.
The app has been built with glidetables.
Except for “Kevin”, which is a link to ChatGPT which, as far as I know, is only possible via Google sheets at the moment.
Have you tried seeing how mamy updates are incurred if you switch all your inputs to USC and not require your 20 users to sign in? Could register 1 or no updates
All entries of values necessary for a calculation are written into a USC.
However, I have not yet tried this without registration.
Thank you for the hint.
Any changes in tool (Data Editor, Layout Editor) made during the building process do not affect the updates quota.
Actions that do not affect data in the tables such as navigation actions do not affect the updates quota.
Multiple changes on add and edit screens count as a single update when the form is submitted.
Working with data in a Glide Table, as opposed to other sources of data such as Google Sheets or Airtable, will have an incidence on the sync quota, not the updates quota.