There may be situations when you need to transfer relatively big amounts of records (over 1000, or maybe as many as tens and hundreds of thousands) across your Quickbase apps and tables. This transfer must be guaranteed to be transactional in the sense that while you are doing the copying, the source data can be changing and the copy needs to take a consistent view of the source data and transfer that view to the destination table in a reliable and performant manner.
When you use Bulk Record Sets in the Quickbase channel you take advantage of a more efficient transfer of large numbers of records. When you batch the records you allow bulk operations to make fewer calls rather than one call per record.
Using Copy Records
In your Pipeline, add a Quickbase channel Bulk records Copy Records step. In this step, you can copy records from one Quickbase table to another using batch CSV export/import APIs.
Note: If the data in the apps in this step cannot contain non-ASCII characters. This step requires that UTF-8 is enabled on the Realm level. Enabling it only on the App level is not enough to transfer data correctly.
When you select the Copy Record step:
|Quickbase account||Select the account you want to use for this copy transaction.|
|Source table||Select the source table from which we will export the records.|
|Source table export fields||Select the fields you want to export into the CSV.|
|Source table advanced query||Create a custom query to select the data you want to export into the CSV. For help with your query, see query operators.|
|Destination table||Select the destination table where you want to import the records.|
|Merge field||Enter the field you want to use to update existing records or add them if they don't exist.|
|Terminate on error||Select whether or not you want to terminate execution on user error. No means the Pipeline will ignore user errors for this step and continue the execution and you will have control over the error handling.|
|Field to map to column||Select the fields you want to map to each column.|