Before you begin
Set up a connection to MySQL.
Use bulk insert SQL query
The bulk insert data option is ideal for large data volumes. integrator.io builds the insert query for you automatically for each batch of records. Each batch's default number of records bound is 100, but you can use the Batch size field to tune your imports as needed.
By using metadata, you can now:
- Search for a specific database, dataset, table, or column to add to your query.
- Use lookups to find data.
- Refresh your data to get new updates automatically.
- Use Mapper 2.0 to map imported records.
- The metadata search will fail if you have a database or table that contains a period ( . ).
- You can use any schema and table name regardless of what you used in your connection with the following format in your import’s Destination table search: database.tableName.
Use SQL query once per record
Execute a SQL query once for each record.
You can write your SQL command in the SQL query text field. Click Edit () to the right of the text field to open the SQL Query builder AFE.
Use SQL query once per page of records
Execute a SQL query once per page of data. You can write your SQL command in the SQL query text field. Click Edit () to the right of the text field to open the SQL Query builder AFE.
Use SQL query on first page only
Use this option if you want to run a SQL command once per flow run. The SQL will execute as soon as the first page of data reaches the flow step. This option should be used carefully to avoid race conditions in your flows.
Question: I am getting an invalid_parameter error while exporting data from NetSuite to PostgreSQL.
Answer: When you are exporting data from NetSuite to a database, such as PostgreSQL, ensure that you enable Skip grouping in NetSuite export. By default, NetSuite results are returned as an array of arrays, whereas integrator.io expects a simple (not nested) array of results. When you enable Skip grouping, the results are received as a simple array.