Is it possible to export entire app ?
Originally posted: Asked by Shihad a month ago What to do if we want to export a table with layout, dynamic rules and each and every property. other than sharing?
Forum Discussion
Unfortunately, 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...
http://www.quickbase.com/developer/knowledge-base/how-would-i-automatically-download-quickbase-table...
- Thanks 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.
- Dan, 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? - The system won't allow for Cross-Realm App relationships. The apps would have to be all on the same Realm.
- OK, good to know that limitation.
Can you move tables from one app to another and maintain the relationships? ie could you take two apps connected by cross app relationships and make it be 1 larger app so that it could then be transferred to a new Realm? - I have moved tables from copies of a live app, back to the original app, that retain the relationship after the move, provided the Key and reference fields; on the Parent to Child setup, remain the same. I have not done this with every table in a cross app.
It should be possible to move the tables one at a time, and as each child table that is brought over, it should recognize the parent Key to the child reference field, and re-associate the relationship. But only one way to find out is to try it.
You can pretty much extract a data representation of anything in QuickBase by using the FormData API:
https://developer.mozilla.org/en-US/docs/Web/API/FormData
The general idea is that using script you navigate to each page where you edit information and extract the FormData representation. Then when you want to "restore" the same data you read the external representation and merge it into the edit form and resubmit it. Conceptually is is not difficult to do and I use this technique to move forms between application but there are a lot of low level mappings to perform and it takes some experimentation to get it working correctly.
