An integrator.io export queries or copies data from an application or system. You also have options for mapping and transforming the data as it is extracted from the source application.
Create an export
To export data from NetSuite, click Create → Flow from the home page. Add NetSuite as your Source → click Transfer files out of source application → create a NetSuite connection or choose an existing NetSuite connection.
Edit NetSuite file cabinet export details
How would you like to parse files?
File type (required): Choose the type of file to be exported from the file cabinet. For example, choose CSV if you are exporting a flat, delimited text file, or XLSX for a binary Microsoft Excel file. The file type you select changes the fields available on the Create export panel. Acceptable file types include:
CSV (or any delimited text file)
Sample file (that would be parsed) (required): This field only displays if you choose CSV, JSON, XLSX, or XML as a file type. Choose a sample file to define the record structure. Click Choose file and navigate to a sample version of the files you will be exporting.
CSV parser helper: The CSV parser helper can be used to visualize and experiment with how integrator.io parses CSV files (or any other delimited text files) into the JSON records/rows that then get processed by your flow. See CSV parser helper.
EDI X12
EDI x12 format (required): Select the EDI X12 file format that matches the files you are exporting from the file cabinet.
EDIFACT
EDIFACT format (required): Select the EDIFACT file format that matches the files you are exporting from the file cabinet.
Fixed Width
Format (required): Select the Fixed width file format that matches the files you are exporting from the file cabinet.
JSON
Sample file (that would be parsed) (required): This field only displays if you choose CSV, JSON, XLSX, or XML as a file type. Choose a sample file to define the record structure. Click Choose file and navigate to a sample version of the files you will be exporting.
Resource path: You can use this field optionally to define the JSON path to the resources you are exporting from the JSON file with handlebars syntax.
XLSX
Sample file (that would be parsed) (required): This field only displays if you choose CSV, JSON, XLSX, or XML as a file type. Choose a sample file to define the record structure. Click Choose file and navigate to a sample version of the files you will be exporting.
File has header: Check this box if the files you are exporting contain a top level header row. If the first row of your XLSX file is reserved for column names (and not actual data), then check this box.
XML
Sample file (that would be parsed) (required): This field only displays if you choose CSV, JSON, XLSX, or XML as a file type. Choose a sample file to define the record structure. Click Choose file and navigate to a sample version of the files you will be exporting.
Resource path: Optionally, you can use this field to define the JSON path to the resources you are exporting from the JSON file with handlebars syntax.
XML parser helper: The XML parser will give you immediate feedback on how your parse options are applied against raw XML data. See XML parser helper.
Where would you like to transfer from?
Folder internal ID (required): Specify the internal ID for the Netsuite File Cabinet folder from which you want to export your files.
File name starts with (optional): Use this field to specify a file name prefix to filter which files in the FTP server Directory path will be transferred. For example, if you set this value to test then only files where the name starts with test will be transferred (like test-myFile.csv).
File name ends with (optional): Use this field to specify a file name postfix to filter which files in the FTP server Directory path will be transferred. For example, if you set this value to test.csv then only files where the name ends with test.csv will be transferred (like myFile-test.csv). You must specify the file extension for this filter to work correctly.
How would you like to group and sort records?
The Sorting and Grouping options allow you to manage your flow’s files by sorting and grouping records by field. This feature allows you to aggregate your data based on your chosen field(s), and sort the records in ascending or descending order (ASC or DESC).
Mock Output
You can now add mock output data to exports and lookups in the Mock output section of the Edit export panel as simulated output data when configuring a flow.
Advanced
Decompress files (optional): Set this field to True if you're exporting compressed files.
Leave file on server (optional): If you set this field to True integrator.io will NOT delete files from your FTP server after your export completes. The files will stay on the FTP server, and if the export process runs again, the same files will be exported again.
Backup folder internal ID (optional): Enter the internal ID. If you want to archive a copy of the exported files. For example, to have integrator.io store a copy of the exported file at ftps://ftp.my-site.com/integrations/backup, enter /integrations/backup. This path must already exist on the server.
Page size: Specify how many records you want in each page of data. The default Page size value (when you leave this field blank) is 20.
Data URI template (optional): This field ensures that all the errors in your job dashboard have a link to the original data in your FTP server. This field uses handlebars templates to generate dynamic links based on the exported data. For example, if you are exporting a CSV file, this field could include one or more columns from the file, such as {{{internal_id}} or {{{email}}}.
Do not store retry data (optional): Check this box if you do NOT want integrator.io to store retry data for records that fail in your flow. Storing retry data can slow down your flow's overall performance if you are processing very large numbers of records that are failing. Storing retry data also means that anyone with access to your flow's dashboard can see the retry data in plain text.
Override trace key template: (optional): Define a trace key that integrator.io will use to identify a unique record. You can use a single field such as {{{field1}}} or use a handlebar expression. For example, this syntax {{join “_” field1 field2}} will generate a trace key template field1_field2. When this field is set, you will override the platform default trace key field.
Batch size: (optional): Enter the maximum number of concurrent files (from 1 to 1000) that can be processed in a single batch request. This setting doesn’t limit the total number of files that you can process in a flow; instead, it allows you to optimize for really big files where bigger batches might cause network timeout errors. If you are importing very small files, increasing the batch size to include several files at a time will improve flow performance.
File encoding (optional): The file encoding indicates how the individual characters in your data are represented on the file system. The default encoding is utf-8. Depending on the source system of the data, the encoding can take on different formats. Current supported formats are: utf-8, GB 18030, ISO-8859-1, MAC OS Roman, Shift JIS, Windows-1252. If you don't know what encoding your data is, in most cases it will be utf-8.
Limitations
- For XLSX file type, we only support UTF-8 encoding mechanism.
- We only support file sizes of 10 MB or less.
- The Netsuite endpoint does not support UTF-16LE encoding, unlike other adaptors.
- This feature doesn’t support encryption or decryption.
- Special case: For files with leading spaces, NetSuite’s metadata trims leading spaces. Any subsequent files (import or backup) will trim leading spaces in names as well. If the file name has trailing spaces,you should specify the filter without the trailing spaces to include the file.
Comments
Please sign in to leave a comment.