Perhaps, in addition to the page setting, a model setting can be made that the unsaved error warning will not show for changes made on that model.
I find that I occasionally use a model for UI rendering purposes which triggers the warning unnecessarily but I don’t want to shut the warning off on that page either.
Yes!!! We have thought of this. But we are also worried about model property bloat. Trying to find the fine line between simplicity and effective functionality. This is “Under Consideration”
Agreed, we are planning to address this in an upcoming release.
If a model setting is too much, maybe allow for an additional argument in model.updateRow that it should not trigger the warning.
