Who is this article for?

Administrators who want to import and export translation files.

Access to this screen requires the Area Admin role.

In many instances, a data conversion project includes attachments. A record may not be complete without the associated attachments. For example, importing Condition objects to a related Action requires a complete set of attachments (pictures, documents, etc.).

Warning: Attaching information to a saved record 
Attachments can only be added after the associated record has been created and assigned an object identifier through the data conversion process. Orphan attachments whose record didn't get created during the data conversion process increase the size of the attachments and will raise an error when processing.

The image below describes the attachment process at an elevated level (click on the image to enlarge it).

Per File Size Limits

By default, the platform has a 20 Megabyte restriction per attachment. When adding an attachment through the UI, any attachment above the 20 Mb limit will be rejected by the server. The REST server is bound to the same limitation. For further information on adjusting this limit please contact your Technical Account Manager (TAM).

Attachment size limitations
The record itself can have as many attachments as needed. The total size of the attachments assigned to an object is not limited to the 20 Megabytes limitation. The limitation is on a single attachment basis only.

For example:

• Attachment A represents 19 Megabytes --> Success
• Attachment C represent 20 Megabytes --> Success
• Attachment B represent 21 Megabytes --> Unable to attach the file
• Attachment A and C represent 39 Megabytes --> Success, the size of every single attachment is less or equal than the 20 Megabytes limitation.

Compressed Total Size 

Customers must collect all the necessary files (attachments and mapping documents) and combine them using compression (zip, tar, etc.) into manageable portions where the total size of the aggregate of all attachments compressed is preferably 1 GB or less.

The typical file transfer is done through SFTP. Sending a huge file could result in a time-out. When a time-out occurs, the process must be restarted, which results in a loss of time. Large files may take several hours to transfer.

The process is not considered complete until all portions are successfully transferred to the server.

Communicate project attachment size 
To prevent issues with the server receiving the file, please communicate the total size of all compressed portions to your project team as soon as possible in the project schedule.

Mapping Files

A mapping file is used to assign individual attachments to the correct record/object once imported. The mapping file is provided by the customer and must be included with each group of attachments provided.

Internal identifier vs. source identifier
When data is loaded onto the platform a unique internal identifier is assigned to each record/object. This internal identifier will not match the source identifier. The source identifier will be loaded into a field for search and reference purposes. The source identifier field will also be used to match attachments to the newly imported record.

The CSV formatted mapping file includes the following columns with a row for each attachment:

• Source Identifier (Required) - The unique identifier from the source where the attachments originated.
• Physical File Name (Required) - The name of the physical file.
• File Path (Required) - The path to the file if a folder structure exists.
• Display File Name (Optional) - The name the file will appear as in the system. If no display file name is provided the physical file name will be used.