To import data from NetSuite, click Create → Flow from the home page. Add NetSuite as your Destination → click Transfer files into destination application or Lookup additional files (per record) → create a NetSuite connection or choose an existing NetSuite connection.
One to many (required): One to many is used when you have a single record that needs to create multiple records internally. You would use this setting if, for example, your parent record contains child records you need to process. This setting cannot be used when importing a CSV file.
Generate files from records (required): Choose Yes if you need to build a new CSV, XML, JSON or other file. Choose No if you are just transferring raw files as-is (such as PDFs, JPGs, etc).
File type (required): Select the type of file that you want to generate. For example, choose CSV if you are importing a flat, delimited text file, or XLSX for a binary Microsoft Excel file. The file name you specify can include a file extension, but it does not affect this setting. You can then choose a sample file to define the record structure. For example, if you are importing CSV files (i.e. files containing Comma Separated Value data), choose CSV. Each file type includes additional settings to customize your import. Acceptable file types include:
-
CSV (or any delimited text file): See File generation for structured data in CSV and XLSX.
Custom header rows (optional): In rare cases it is necessary to include one or more custom header rows before the CSV data. Add any such prefix rows in this setting.
-
EDIFACT
-
Fixed width
-
JSON
-
XLSX
-
XML
Sample file (that would be generated): If you have a sample file that represents the record structure of the files to transfer, you can upload the sample file here. We will use the sample file to auto-set various fields (where possible), and also help you map data in a subsequent step. The sample file that you provide does not need to be overly large (at max 5 records), but it should contain all the fields that you want to work with, and also be in the same format that the transfer will need to generate when running in a production capacity.
How many files would you like to generate?: Select how the flow should generate output files. Select One file per flow run to create a single file that contains all of the records processed during the flow run. If the flow includes more than one export, one file will be generated for each export. For real-time flows, a file is created using all of the records received in the current request. Select One file per page of records to generate a separate file for each page of records processed during the flow run. This setting appears only when you select CSV, XML, JSON, or XLSX file type.
Folder internal ID (required): Specify the internal ID for the NetSuite File Cabinet folder where you want to import your files.
File name (required): Specify the name (e.g. 'temp.txt') for the file that you want to import to the NetSuite File Cabinet. If the file name should be dynamic based on the data you are integrating, you can specify the JSON path to the field in your data containing the name values instead. For example, {{{myFileField.fileName}}}.
Backup folder internal ID (optional): Specify the internal ID for the NetSuite File Cabinet folder where files will be backed up after successful transfer.
Compress file (optional): If you would like to compress files before they are posted to the import application, set this field to True. Once you check this field, a dropdown field appears for you to choose the compression format.
File encoding (optional): The file encoding indicates how the individual characters in your data are represented on the file system. Leave this field blank if you do not know what the encoding format is. Currently supported formats are utf-8, GB 18030, ISO-8859-1, MAC OS Roman, Shift JIS, Windows-1252. If you do not know what encoding your data is, in most cases it will be utf-8.
-
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.
-
If you intend to use the File name starts with feature and your file name has leading spaces, you must include the correct number of leading spaces in the filter.