This tutorial explains how mapping works within the application, focusing on auto detection, manual mapping, and behavior during template creation. It demonstrates how mappings are identified based on variable names and predefined matching rules, and how users can adjust mappings directly or during the Create TFL flow. The walkthrough highlights how only required variables appear for mapping and clarifies how mappings created during template generation are saved only when no prior mapping exists. Ultimately, the tutorial emphasizes that the dataset mapping tab serves as the authoritative “source of truth,” while still allowing temporary flexibility for one-off outputs.
Key Takeaways
Auto detection prioritizes variable names, then matching names (case-sensitive, then insensitive).
Manual mapping allows users to assign, modify, or delete variable mappings as needed.
The Create TFL flow only requires mapping for variables used in selected templates.
New mappings made during TFL creation are saved only if no prior mappings exist.
The dataset mapping tab is the “source of truth,” ensuring stability with optional temporary overrides.
Watch the Data Mapping Tutorial