Forum Discussion
_anomDiebolt_
10 years agoQrew Elite
As Eric describes the DoSave() function was prominent in the source code of the old UX so people started using it. Now with the new UX that function is deeply nested inside a JavaScript file and is not visible in the HTML source. Moreover, additional functionality exists in the new UX that influence what happens when a Save Button is clicked that occur before DoSave() is even called. The bottom line is that you should not use DoSave() as you may well be sidestepping some of the functionality QuickBase implements to verify that can be saved (validation, distinct field values, conflict resolution etc).
Also, the Do in QuickBase's DoSave() simply meant execute or call the Save functionality. It did not mean do something extra after the save - That was a concept I introduced with various forms of the so call "Save and Do" Technique.
Also, the Do in QuickBase's DoSave() simply meant execute or call the Save functionality. It did not mean do something extra after the save - That was a concept I introduced with various forms of the so call "Save and Do" Technique.