Forum Discussion
- DanSupport_Quickbase Staff1 comment
What would be the purpose behind the export?
- Blake Harrison - DataBlender
- 25 days ago
AnswerSurprisingly in the early days of QuickBase there was a command to do this:
?act=doexport&filetype=oif
I think oif stood for "OneBase Interchange Format" where OneBase was the predecessor product name for what became QuickBase. If you try that command today the response is "OIF format is no longer supported."
That said there is a relatively easy way to get an external structural representation of forms and form rules. However, I am not going to reveal it without understanding what your purpose is. There is a good chance your proposed usage may violate QuickBase's terms of service.
Was this answer helpful?
Answered by:
dandiebolt_QB_Pirate , Pres. of Service Worker Union
QuickBase Pro 24 days ago
1 comment
ok..i understand
- Shihad
- 22 days ago
- LeslieGQrew CadetI am interested in doing the same thing. Our company is closing, so it's not as though we are moving to another competitor. I would like to export the app structure/dynamic form rules so that I can someday re-launch a Quickbase account for a similar business and not have to start from scratch. Is this possible?
- QuickBaseCoachDQrew CaptainYou would need to make a copy of the app and "Park it" with someone how has a Quick Base Account. Feel free to contact me and speak directly via my gmail account on the contact page of my website QuickBaseCoach.com
- _anomDiebolt_Qrew EliteIf you have only one application I would follow Mark's advice and park the application. If you have many applications there probably is a way to extract the form definitions and restore it using script but there are going to be other aspects of the application that would be difficult to export and no guarantee they would re-import later if QuickBase changed its structure.
- QuickBaseCoachDQrew CaptainExport to where?
- JoeAcunzoQrew TraineeI have a similar situation as Leslie G, a client closing their business. They have stated the possibilty of opening another business in the coming months, and may want to use the same set of apps. So Dan G, how about sharing the "relatively easy way to get an external structural representation of forms and form rules." For that matter, is there a way to get all schema elements (other than API_GetSchema) that allows for easy creation of the app in a new Quick Base account?
The biggest issue is preserving cross-app relationships, which there are many. - DanSupport_Quickbase StaffUnfortunately, there is no easy way to export an entire App. CSV files per table is the long way. The API GetSchema is the way I know to pull the App setup. The last option is using QB desktop to pull the full App data into MS Access. This will only work to pull the data into MS Access, it won't import back into Quick Base as a new App, but it will at least have the entire app setup in Access: (see steps)
http://www.quickbase.com/developer/knowledge-base/how-would-i-automatically-download-quickbase-table...- JoeAcunzoQrew TraineeThanks Dan. It's those cross-app relationships that are a killer to have to recreate as there are so many of them. Even if Copy Application preserved those, it would be helpful.
- QuickBaseCoachDQrew CaptainDan, while we have your expertise.
If there is a need to park and app into another Realm and it is in fact a set of apps connected by Cross App relationships, can that be done? ie will the system prevent the situation where during the transfer process, some of the apps will have different Owners? - DanSupport_Quickbase StaffThe system won't allow for Cross-Realm App relationships. The apps would have to be all on the same Realm.
- MelissaDoranQrew CadetSounds like a feature that should be voiced to Quickbase. For example, what would happen if you just stopped paying your bill? All information disappears? Yikes that would suck if you were a one man business and went into a coma for a few months. There goes all your information. Ouch.
- DanSupport_Quickbase StaffWe do retain the App data on the servers for a 6 month period after the deletion or cancellation of an account, before we fully purge all app data. So hopefully they wake up before the six months are up
; ) - _anomDiebolt_Qrew EliteThe "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.
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- JoeAcunzoQrew 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_Qrew EliteActually I learned this technique from the future Sam Jones who came back in time to terminate native QuickBase in favor of script.