Import Microsoft Azure Blob Storage files

Name your transfer

Name your resource so that you can easily reference it from other parts of the application.

Description

Describe your resource so that other users can quickly understand what it is doing without having to read through all the fields and settings. Be sure to highlight any nuances that a user should be aware of before using your resource in their flows. Also, keep this field up to date as you make changes to the resource.

Connection

Find an existing connection to apply to this export or lookup, or you can click Create connection to define a new resource that you can use here and in other flow steps. Each connection contains securely stored credentials and information needed to access this application. All connections displayed in this list are specific to this application and registered to you for this integration.

One to many

There are advanced use cases where a parent record is being passed around in a flow, but you actually need to process child records contained within the parent record context. For example, if you're exporting Sales Order records out of NetSuite and importing them into Salesforce as Opportunity and Opportunity Line Item records, then you will need to import the Opportunity Line Item records using this option. One to many is used in cases where you have a single record which internally needs to create multiple records. This field cannot be used when importing a CSV file.

Generate files from records

File type

Select the type of file that you want to generate. For example, select 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, although it does not affect this file type setting. You'll then be able to select a sample file to define the record structure. See Import files to an FTP server for more information.

How many files would you like to generate?

One file per flow run or one file per page of records.

Container name

Specify the Azure Blob Storage container and optional virtual path prefix to transfer files to. Click Browse to open a container and prefix picker and select a path — the selected value is written back to the field automatically. Note that Azure Blob Storage uses a flat storage model — folder-like paths are virtual prefixes formed by forward slashes in blob names, not real directories.

File name

Use this field to specify how the files being uploaded to the Azure Blob Storage container should be named. You can type '{{{' to include a predefined timestamp template in your file name. For example, 'FileXYZ-{{{timestamp "YY-MM-DD" "America/Los_Angeles"}}}.txt' will upload files with the following pattern: 'FileXYZ-16-06-30.txt' in America/Los_Angeles time. You can include any file extension — it does not affect the type of data generated.

Encrypt files

Use this cryptographic system to encrypt generated files. This option is enabled only when you have configured at least one cryptographic system in the connection. If it is unchecked, then encryption will not be performed on generated files.

File encoding

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. The default encoding is UTF-8. Other supported formats are Windows-1252 and UTF-16LE.

Compress files

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.

Backup container name

Where to store backup copies of processed files. Resolved at runtime via the provider's listing API. Leave empty to skip backups.