We are running into user errors on an application where they claim their edits are not being saved to our tables. This is a newer error and we have attributed it to likely being user error with users not pressing the save button.
As a workaround, we want to update the database when a change in a field is detected. We have it working on a select few fields for testing, but are worried about future updates to this data save process where we would need to make future changes to each field individually.
Is there a better way to save changes to the database on a field's change event that is easy to update in the future? Maybe update the save mechanism in a single place that then applies to all fields?