I have an app that is currently suffering from extremely high update counts since I’m using the user record to store user-specific information pertaining to the state of a dropdown. There are about 1,000 users, & so you can imagine how quickly the number of updates skyrockets during heavy usage since every change to the dropdown value is counting as an update.
@DarrenHumphries suggested that I leverage a user-specific column to do the same within a Glide table other than the users table (thanks Darren!).
Before I were to go with that approach, I was hoping someone could confirm for me that updates to user-specific columns do NOT count as an update for billing purposes?
Apologies for the late reply here, but thank you everyone for your input!
In my case, all users are signed in users. Does that mean I’m out of luck & there’s no way around persisting drop down selections (to allow for per user preferences to persist) from counting toward updates?
Any additional confirmation would be greatly appreciated!
Im 99% sure USCs updated by signed in users will count towards your updates. You can always test yourself using both signed in and non signed in users. Sometimes it takes a few minutes for your update count to sync.
It is not a simple task to implement a strategy to save updates in an application that consumes many. The only way I know of, in my experience, is to organize your application more into edit and form screens, not custom screens.
In Glide’s edit and form screens you can change the contents of the fields as many times as you want and be sure that you will consume 1 update only after you submit the form; this happens because the content of the fields is not immediately synchronized with Glide, but remains temporary in the device until it is sent.
The problem is that in edit/form screens you can’t do the same nice things you can do in custom screens.
Any action that generates a change in the backend counts as an upgrade, even if using user specific columns this happens if it is a logged in user.
A DSC (device specific) column would solve a lot of problems, but unfortunately it doesn’t exist and seems to be only in my fantasies.