Export schemas
Use an export schema when a CSV needs a specific set of source fields, column headers, and column order.
A schema defines the layout, not the evidence itself. Naming a column does not add a missing value or establish that the exported data meets an audit requirement.
Built-in templates
Expand a built-in template to review its mappings. Built-in templates cannot be changed.
Create a custom schema
Name the schema
Select New Schema, enter a clear name, and add an optional description.
If no custom schemas exist yet, use Create schema. Name the destination or report, such as Monthly session review, so others can choose the right layout.
Map the columns
Add a row, choose a source field, and enter the CSV column header.
The source field selects the data. The header is the label readers will see in the CSV; changing it does not change the source value.
Each row needs both values, and a source field can appear only once. Remove fields the destination does not need, especially fields that may contain sensitive data.
Set the order
Move rows up or down until the columns match the required export order.
Expand the column preview and confirm the source field, CSV header, and order before saving.
The preview shows the mappings, not proof that every exported record has those values. Check a sample export against the report’s requirements before wider use.
Save
Create the schema. Administrators and Developers can reopen it to change mappings or delete it when it is no longer needed.
Change or delete a shared schema
Check with the report owner before renaming headers or changing their order. A spreadsheet or downstream import may depend on the existing layout.
Deleting a custom schema removes it from every user’s export menu and cannot be undone through the dialog. Confirm that it is no longer needed before deleting it. Built-in templates remain read-only.
Use a name that identifies the destination or report. Saved custom schemas appear in the schema chooser for CSV session exports.