I’ve created a UI Only field called “Running Balance”. Works great except that I have to save the model on page load as the custom field updates the rows in order to display the values.
I’d like the option to exclude the field from registering as a model change.
I tried a combination of setting the field to read only and when I update that UI only field via javascript (javascript processing and updateRows after the model has loaded) I then immediately cancel all changes on the model. It seems to work when doing it this way, and prevents issues that might arise from “fake” unsaved changes on the model.
Still, why do we have to go through this crazy workaround for something that should just be an inherent feature? There’s no reason a UI only field that cannot be written to the database should cause the model to think it has unsaved changes.