Unmapped Columns
Allow users to submit columns not included in the sheet template.
There can be cases where each of your users has unique columns in their sheets that they want to upload. These columns are not known to you beforehand and hence cannot be configured as part of the sheet template. These columns can be discovered only after the user uploads the file. Hence, they cannot be configured as dynamic columns either. We call these columns Unmapped Columns.
With CSVbox you now have the option to accept Unmapped Columns as well.
Enabling Unmapped Columns
You can start accepting data from the Unmapped Columns by simply activating the option via your CSVbox dashboard.
Login to your account.
Edit the sheet of your choice.
Go to the 'Options' Tab.
Select 'Yes' for the 'Accept Unmapped Columns?' field.
Click 'Save'.
The importer will then start accepting data from the Unmapped Columns submitted by the users.
Receiving Data from Unmapped Columns
The data from the Unmapped Columns is available in the data destinations along with the data from the regular columns. Currently, Unmapped Columns are supported by the following destinations only:
API/Webhook Data Destination
In the API response JSON object, the dynamic data will be displayed inside the _unmapped_data object as shown below. The _unmapped_data object will be visible only if the Unmapped Columns are activated. In the example below check lines 12 and 32.
If any of the Unmapped Columns do not have a header specified in the user uploaded file, then the app will auto-insert column names _empty_header_1, _empty_header_2, and so on.
S3 Data Destination
In the AWS S3 file store, the Unmapped Columns will be added as new columns in the uploaded file.
Last updated