Hi,
I’ve created an app and used button blocks for navigation by writing to a column in the user profile row.
That then links to the visibility of various containers and so most of the app is on one page. It’s wroking really well however, I seem to be using a ton of edit updates. Could this be because each time a user hits my navigation method, it is infact being counted as an edit row update?
Thanks
If your buttons are setting column values in a table, then yes that is considered an edit because you are changing (editing) data in a table.
It sounds like your user table is not a Glide table. Are you using some sort of external data source? Glide tables will not count updates under the current plan pricing, but external data sources will, so it can save on a lot of updates if you convert your user table into a Glide table.
Another alternative is to not use the user table, but create a single row table with a bunch of user specific columns to serve as the source table for your screen.
There are no external data sources, only glide tables.
No one has actually used it yet, I’m still doing my own testing and I’ve managed to use 469 updates.
Do you know if it possible to get a breakdown of what componements are triggering the update.
Seeing the public and private users in your usage screen proves to me that you are not on a current plan. It appears that you are on a legacy plan. Legacy plans do not provide free updates with Glide tables. You would have to upgrade your plan if you want to take advantage of that. So yes, under your current plan you will incure updates every time a button is pressed. If you switched your buttons to open different screens instead of setting column values in the table, then you wouldn’t have to worry as much about updates, but it’s a complete redesign of your app which would not relay as much on visibility conditions on a single screen.
Got you, it’s just a small community app so my plan was to upgrade to the Maker plan once ready to launch. Presumably that would then sort it?
Thanks
Yes, upgrading to the Maker plan should definitely resolve the issue. That would put you on a new plan, and edits to the Glide tables would not be counted as updates.
I recommend creating a new free team, duplicate you app, and transfer the duplicate to the new team. That way you can at least play around with a new plan and make sure it will work out for you before upgrading to the Maker plan. This still leaves your old legacy plan if you still need it.
Great thank you
