Structuring CSV Files
Below are the examples of how the structure for CSV file types must be set in order to merge appropriately.
CSV Data Structure
CSV documents are uploaded and converted into JSON so it can be read by the High Volume Document Generation mere engine. When converted to JSON, each row in the CSV file will translate to a single job as it would in a JSON file.
Required Elements:
Header Row
Unique ID value
A header row is required for the CSV to merge properly, and a unique ID is required per each row. Each row is equal to one job run by High Volume Document Generation.
Optional properties that can be specified to control delivery methods use specific column headings such as:
Note: Currently, only root level JSON properties are supported for CSV files.
CSV Example of five rows of data: | id | document.outputname | first_name | last_name | gender | ip_address | |
|---|---|---|---|---|---|---|
| 1 | 101.pdf | Muriel | Esmond | mesmond0@example.com | Female | 77.91.222.125 |
| 2 | 102.pdf | Millard | Chelsom | mchelsom1@example.com | Male | 6.37.110.221 |
| 3 | 103.pdf | Ricky | Dwelley | rdwelley2@example.com | Genderqueer | 131.13.242.161 |
| 4 | 104.pdf | Lucho | Nesfield | lnesfield3@example.com | Male | 125.107.63.103 |
| 5 | 105.pdf | Jamey | Bruckent | jbruckent4@example.com | Male | 185.113.28.119 |
document.outputname
email.to
email.from
email.cc
Converted CSV row to JSON example:{
"Id": "1",
"EmailOptions": null,
"DocumentOptions": {
"OutputName": "101.pdf"
}
"Data": {
"id": "1",
"first_name": "Muriel",
"last_name": "Esmond",
"email": "mesmond@example.com",
"gender": "Female",
"ip_address": "77.91.222.125"
}
}
