Development environment
Hello everyone, I would like to create application that populates the quick base table using API. I need some kind of development environment where I can test everything as the original tabl...
Forum Discussion
Hi Rita,
To your question on how to populate QB with external data, one option is to utilize API_AddRecord to populate data into QB.
We are also launching in February a very powerful tool called Quick Base Pipelines. Pipelines will be a full set of integration capabilities built directly into Quick Base. Included will be the ability to integrate with a few other platforms on which you can build custom forms.
Hope that helps, and you're in great hands with other expert builders in the QB community who might be able to provide more detailed answers to your specific situation.
Best,
Chris
------------------------------
Chris Hutchens
------------------------------
To your question on how to populate QB with external data, one option is to utilize API_AddRecord to populate data into QB.
We are also launching in February a very powerful tool called Quick Base Pipelines. Pipelines will be a full set of integration capabilities built directly into Quick Base. Included will be the ability to integrate with a few other platforms on which you can build custom forms.
Hope that helps, and you're in great hands with other expert builders in the QB community who might be able to provide more detailed answers to your specific situation.
Best,
Chris
------------------------------
Chris Hutchens
------------------------------
Chris, One thing I noticed about the new sandbox is you are no longer able to do a table to table import from any other app to the sandbox. Is this intended? Previously when creating sandboxes I would sometimes have to move data over to it and would always just table to table import to make sure I had the right data from production. Now this feature is grayed out when trying to import to the new sandbox.
It still lets you import via clipboard or several other ways however most of those do not work when you need to preserve the record id. When you go to import with a record id via clipboard for example it forces you to pick Record ID# as the merge field, which is fine, until it gives an error because it could not update those records. There is nothing in the table for the sandbox which is why it cannot update them, the records don't currently exist there. I just wish I was able to import the records back into it. There are many times where you want to see how the data behaves with your changes before you push to production and it doesn't seem possible anymore... Previously even in early access for the new sandbox the table to table import was able to be used.
If I am just missing something and someone can tell me how to import a full table into the new sandbox now that the table to table import is grayed out, please let me know. I have not tried the API yet.
It still lets you import via clipboard or several other ways however most of those do not work when you need to preserve the record id. When you go to import with a record id via clipboard for example it forces you to pick Record ID# as the merge field, which is fine, until it gives an error because it could not update those records. There is nothing in the table for the sandbox which is why it cannot update them, the records don't currently exist there. I just wish I was able to import the records back into it. There are many times where you want to see how the data behaves with your changes before you push to production and it doesn't seem possible anymore... Previously even in early access for the new sandbox the table to table import was able to be used.
If I am just missing something and someone can tell me how to import a full table into the new sandbox now that the table to table import is grayed out, please let me know. I have not tried the API yet.
- Hi Austin,
Yes, it is intended that table-to-table imports do not work in a sandbox. The reason is that table-to-table imports automatically bring all of the related applications involved into a thread that shares the same computing power, and creates a situation that is ripe for crashing your app.
That being said, you can copy all of your live data directly into your sandbox when you create the sandbox (just select "all records" in create dialog). The record IDs are maintained, and it's as if you're looking at your live data.
Does that meet your needs?
Best,
Chris
------------------------------
Chris Hutchens
------------------------------- That makes sense and is understandable.
That would work fine for us but our app is above 1GB in size and it only lets us bring over a small set of records, I believe it was 50 records. So bringing over all records is not possible for us with our main app. Do you know if there are plans for lifting or increasing this limitation at any point? - Hey Chris,
So is the final answer for now that this will not work until the app is below 1GB? This is a limitation that I see listed in the help documentation. I wish there was a better workaround available than just being able to import a small portion of records.
Is this something that can be individually adjusted per account/realm by support, kind of like the attached file space?
Thanks- Hi Austin,
Yes, that is the current limitation (1 GB data). We'll keep an eye out for more feedback on this area and take action as necessary.
Thanks for your engagement!
Best,
Chris
------------------------------
Chris Hutchens
------------------------------