Forum Discussion
_anomDiebolt_
8 years agoQrew Elite
The "state" of a QuickBase application is scatter all over the place so you would have to do a lot of nuisance work to locate on which pages you could extract the state and more work to restore it. The primary "state" you probably want to save is the forms, followed by reports and the dashboard.
One way to save the state of forms is to use script and the FormData API.
This code will extract all properties of a form to an object which can be further searalized and save externally.
The essence of this technique is to capture all the form properties while it is being edited and to save them externally
One way to save the state of forms is to use script and the FormData API.
This code will extract all properties of a form to an object which can be further searalized and save externally.
var formData = new FormData(mainform);
for(var pair of formData.entries()) {
console.log(pair[0]+ ', '+ pair[1]);
}
The essence of this technique is to capture all the form properties while it is being edited and to save them externally
- JoeAcunzo8 years agoQrew TraineeJust tried your code snippet to save a form. Very nice, thanks for this tip and code. I've done similar things to get a list of forms for a given table for some of the Quick Base add-on products I offer since the API doesn't expose that info.
- _anomDiebolt_8 years agoQrew EliteActually I learned this technique from the future Sam Jones who came back in time to terminate native QuickBase in favor of script.