Export Template Data

Rebekah Garner
Rebekah Garner
  • Updated

The Export Template Metadata button lets Administrators to download a complete, structured record of a template's configuration as a CSV file. This includes every field, its type, validation rules, transformations, and any associated lists.

Instead of manually documenting how a template is built, admins can generate an accurate, up-to-date export directly from the platform in a few clicks.

 

Why This Feature Is Important

Templates often contain layered configuration: required fields, naming conventions, autonumbering rules, date formats, and concatenation logic. That configuration lives inside the platform, which makes it hard to document, audit, or share outside the tool.

This feature solves that by giving admins a portable, readable snapshot of the template. Common use cases include:

  • Keeping a data dictionary current. Instead of manually tracking field names, types, and rules in a separate document, admins can export the source of truth directly and update their data dictionary with accurate, current values.
  • Sharing configuration with teams. Marketing, analytics, or operations teams who need to understand naming conventions or field logic can receive the export without needing platform access.
  • Feeding analytics and BI tools. The exported CSV can be ingested into BI platforms or data governance tools to validate that campaign data matches the rules defined in the template.
  • Supporting audits and reviews. Compliance or QA teams can review field-level rules (validation, transformation, uniqueness) without needing a walkthrough of the template itself.

How to Export Template Metadata

There are two ways to export template metadata, depending on where you're working.

From the Templates page:

  1. Go to the Templates page.
  2. Select a single template using the checkbox. 
  3. Click the Actions button to access the menu and select Export Template Metadata.
  4. In the modal that appears, optionally enter a description for the export.
  5. Click Export. A CSV file will download automatically.

 

From within a template:

  1. Open the template you want to export.
  2. In the top right of the template view, click Export Template Metadata.
  3. In the modal that appears, optionally enter a description for the export.
  4. Click Export. A CSV file will download automatically.

 

When an admin exports a template, the platform generates a CSV containing:

  • Template details: name, version number, and export timestamp
  • The optional export description, entered at the time of export, useful for noting why the export was created or what changed
  • Field-level detail for every field in the template, including:
    • Field name and description
    • Field type (text, date, number, autonumber, concatenation, and others)
    • Whether the field is visible, required, or unique
    • Precedence (field order)
    • Any associated list or list column the field pulls from and it's UUID for API use
    • Governance rules applied to the field, such as validation patterns, text transformations, date formatting, autonumber settings, or concatenation logic
  • Template Lists used within the template

This gives a full picture of not just what fields exist, but how each one behaves and what rules govern it.


Tips and Best Practices

  • Use the description field to note the purpose of the export (for example, "Q3 audit" or "shared with BI team") so the context isn't lost once the file is downloaded.
  • Export metadata after any significant template change to keep your records aligned with the live configuration.
  • Share the exported CSV with teams who rely on naming conventions or field rules but don't need direct platform access.
  • Because the export reflects the template version at the time of export, re-export after updates rather than relying on an older file.

Comments

0 comments

Article is closed for comments.