Custom data maps offer greater flexibility and control when defining the structure and order of survey fields in exported reports. Rather than relying solely on field selections made in the Fields selector, a custom data map specifies exactly which fields and options appear, in what order, and how they are represented in the export file.
Why use a custom data map
Custom data maps are ideal when data analysis requires a specific report structure or when consistent reporting structure must be maintained across versions of a study. They can provide more granular customization than the standard field organizer.
Key benefits include:
- Precise field ordering: Define the exact order of questions, variables, and options in your export.
- Reordering checkbox options: Adjust the order of checkbox options, which cannot be rearranged in the standard field sorter.
- Tracker study alignment: Maintain consistent reporting structures across multiple survey waves, even when questions are added or removed.
- Custom variables: Add variables that don't exist in the survey programming but are needed for analysis or reporting.
How it works
Each time an export is created, a data map is automatically generated based on the selected and ordered survey fields. In some export formats—such as ASCII—a separate data map file is downloaded alongside the data, defining the structure of the export. In other formats, like Excel, a standalone data map isn't downloaded, but the export itself displays what each column of data represents.
When a custom data map is used, it overrides the field selection in the export setup. If questions are later added or removed from the survey source, those fields will not be represented in an exported file if (if the data map used is not updated).
Creating a custom data map
1. In Deliverables, create a New Export.
2. Select an export type that supports custom data maps (ASCII, Excel, SPSS, or Triple-S).
3. Arrange your fields in the desired order.
4. Under Advanced Export Options, locate Use custom data map.
5. Click the gear icon, then choose Save current fields as data map.
6. Name the file and click Save.
The data map will automatically download to your device.
Modifying and uploading a custom data map
1. Open the downloaded data map file.
2. Edit as needed:
- Reorder rows to change the field order.
- Add new fields or variables as needed.
- Keep key identifiers (like trans_id) near the top for easy data management.
3. Adjust the "Start Column" and "End Column" values. If this is not done correctly, data can be affected and/or the file may not upload. Read the next section for more details.
4. Save the updated file.
5. When creating a new report, go to Advanced Export Options again.
6. Click the gear icon next to Use custom data map and select Upload xlsx data map.
7. Follow the prompts to select and upload the file.
8. The uploaded data map is now available for any future exports that support custom data maps.
Adjusting the Start Column and End Column values
The number of columns required for a survey field depends on the question type (radio, checkbox, or numeric) and the length of its option IDs.
Helpful information:
- A radio question needs one row since only one value is stored.
- A checkbox question needs a row for each answer option, as multiple values may be stored.
- Each row should have enough columns to hold the full answer option ID. For example, an ID of '1' needs one column, while '999' needs three.
- Numeric questions are given 16 columns by default.
- Tables follow the same logic as their radio, checkbox, or numeric counterparts, with one row per table row—repeated if it's a checkbox table.
- Columns cannot overlap or decrease in value.
For ASCII exports:
- Truncating end columns may cause export issues.
- Extending end columns is safe; extra space just adds white space.
- Start/end columns don't affect non–fixed-field exports.
Tip! Exporting a set of selected questions/variables as a data map shows the exact start and end columns required for each field.
Comments
0 comments
Please sign in to leave a comment.