Yes, T2T imports don't convert nicely but it's pretty easy to convert them manually.
Just use a Quickbase "Make Request"
Here is an example
For the URL do this:
https://mycompany.quickbase.com/db/xxxxxxxx?a=API_RunImport&id=11
So its really just a copy and paste of the table URL and suffix it with the API_RunImport and you get the ID by editing the Saved T2T import and observing the URL.
Then just select Method of POST and you are done!
------------------------------
Mark Shnier (Your Quickbase Coach)
mark.shnier@gmail.com------------------------------
Original Message:
Sent: 09-11-2023 12:04
From: Les Kimbler
Subject: Pipelines - Functional or Not
Quickbase has always advertised itself as a Low-Code/No Code system. But with Pipelines, it seems that you have to be able to code to get it to do anything you want it to do.
I loved Automations. I could build a pretty complicated one in like 5 minutes to do what I need it to do. After months of trying, and even trying to duplicate Migrated Automations, I have yet to successfully build a working functional Pipeline.
On top of that, The migration tool does not always work with the Automations. I have multiple ones I have tried to migrate, and the tool fails everytime. So I literally have multiple jobs that the automations did every morning that I am having to physically do manually because I can't make a pipeline do it.
And come to find out searching through this community, the migration tool was not set to correctly migrate Table to Table imports, so that has become another manual process.
If someone has any options of how to create a pipeline to run a Table to Table import on a daily basis, that is not impossible to build, please help.
------------------------------
Les Kimbler
------------------------------