I have an app where I am using form components to do searches on a custom collection.
My problem is: everytime the user changes the information of one component it is considered as one update, which is draining my update counts very quickly.
I do not need for the search to be registered, I want to take the information from screen.
Any solutions to reduce the amount of updates for this type of search?
Assuming you are writing to user specific columns, the only way it would not count as an update is if you are not signed in. In that case user specific columns are kept local and not synced to the database because they can’t be linked and saved to a specific user.
Otherwise, if you are changing data in a table, which includes using form components on a detail screen, then yes it’s going to count as an update because you are updating the database. You could try using the in-app filtering on the collection as an alternative.
Thanks for the suggestion.
The problem with making it public is that the information shown is sensitive, we don’t want everyone to have access to it.
And the problem of the current in-app filter is that it is not user-friendly at all. When I try to add the fields that I want to be filtered it becomes a huge list, since it does not recognize each item saved on the same field.
Sorry, I don’t have any really good suggestions, but one thing you could do is move the components to an edit form that is opened with a slide in overlay. When a user wants to change the filters they would click a button to open the edit form, make their changes, and submit the form. This wouldn’t eliminate updates but it would reduce them a little bit.
I know this is something a lot of us have asked for because we use user specific columns a lot just for navigation, custom forms, filtering, or just general temporary local storage. This is a request that I created a while back that I would love to see happen, but I don’t know if it ever will.
Thanks! I added my vote for this request.
