I want to see if there is a better way to do this WF to show that an input value was saved when auto binding.
I noticed that the auto biding allow me to set up an alert but I am not sure how to do that. So I have been using the Alert Plugin.
There really is no difference, but if there is a built in alert based on use of autobinding, just use that since it is easier. Keep in mind autobinding costs 1.62 WUs per autobind.
I actually cannot find how to use that built in alert. So having trouble there.
And ohh. So I assume it cost less to just have the user hit a button to save the data? If so I might just go back to having the data being saved with a click.
yes, because that will save at one time all values in your make changes to thing workflow action, rather than relying on them to be saved individually using autobinding, so if user were to have autobinding enabled and made just one change it costs them same as them having to press a button, but if they change say 10 fields, than that is around 10x more expensive than pressing a button.
I personally do not use autobinding, so I’m not 100% sure there is a built in alert, but the approach of using the ‘when input value is changed’ workflow action is sufficient to then show an alert.
In my apps I build using my plugin Data Jedi, which it enables me to build out functionality for spreadsheet entries like in your app with some advanced functionality and feature sets, as well as reducing the overall cost of operating the app (enables scaling on Bubble).
Some of those things include use of Local Storage. This lets me when the user makes a change to a single field, to update my local storage of that entries values so as to keep it safely stored without interacting with DB, which if the user for whatever reason closes the browser, next time they open it is still in local storage. This lets me create a feature to prompt the user to ‘pick up where they left off’ or cancel changes.
I also have an element in the plugin that compares two things to see which fields are different. This allows me to build features into the spreadsheet to highlight fields or inputs that are different from original (ie: have been changed), and be able to show what the original value was and it’s current value. This allows me to build out features to enable a user to save just the updates to that single entry (ie: that one cell of the repeating group), or the entire list of things in repeating group, or the entire object (I have one setup with 4 different data types on one main screen all related to each other, all of which may have lists of things related as well).
I’ve built this for the client in order to allow the client to work with their data the way most comfortable for their workflow.
After discussing with client it was obvious their workflow necessitated the creation of multiple lines in a single repeating group (ie: multiple entries of a data type to display), just for the ‘setup’ before they ever get to enter any values, since they are basically templated and have just a few values that may differ from one entry to the other. So, for that, we create all the entries in the clients device (ie: without ever touching bubble DB and incurring WU costs) and it is only after the user decides to save one entry, all entries or everything do we ever actual save those entries into the DB.
So for some use cases this approach is optimal and for some it might not be, it just depends on how you see the best approach for your apps users and how they may interact with the data during a session.