DataLoader-FAQ

Encryption

1. Is there any encryption for DataLoader files? We don't want our data or upload files (e.g., CSV files) to be accessible by AutoRABIT or any other party.

Answer: AutoRABIT does not encrypt CSV files. However, the EBS volumes are encrypted using AWS KMS keys.

2. Can a customer's own key be used to encrypt their data? Is this possible?

Answer: Currently, AutoRABIT does not support customer encryption keys for data encryption. This feature is not supported at the moment.

Data Storage

1. Where is the result data (including exported data) physically stored, and can it be moved to a specific location (e.g., Another country)? Can we ensure this data is not stored in AutoRABIT?

Answer: AutoRABIT does not delete data in the DataLoader functionality until the customer deletes it. For example, the ap5.autorabit.com instance is hosted in an AWS Singapore data centre, and the data is stored in EBS volumes with AWS KMS keys in the same region.

Error Messages

Data Loader Pro job fails with "Invalid ID" error message when the parent object is not selected.

Invalid ID error occurs while running the DataLoader Pro job from release 23.1.26.

This is a known issue in the DataLoader Pro module. There is an invalid ID error while not selecting the parent object and keeping as null. A fix is available in the ARM 23.1.28 build version.

The customer has a DataLoader Pro job and has two queries:

1. They had to select the ancestor object whenever they ran the DataLoader Pro job.

2. They have tried a few records with null values, and it resulted in multiple object record failure with the error message Invalid ID.

Feature Overview

As per the customer scenario, they are trying to update with "null" values. For this to happen, you must choose "Insert/Update with null values" while running the pro job.

There are several different times you do not want to include ancestor records you haven't changed.

If there are no changes on ancestors, then it is not required to include that Parent object in the job unless it is a Master-Detail relation.

Feature Considerations

The current DataLoader setup in AutoRABIT requires parents' objects to be included without the Limit.

Resolution: The current DataLoader setup in AutoRABIT requires parents' objects to be included without the Limit 0 option for the records, causing some records to fail. A code fix has resolved this issue, available in the ARM 23.1.28 build version.