Templates
What Are Data Validation Templates?
Data Validation Templates let you define reusable validation scripts and file structures that are applied when running data checks on a Dimensions project. Instead of rebuilding your validation setup for every project, you create a template once — complete with file paths, script logic, and dynamic markers — and select it each time you start a data validation job.
Templates use two types of markers to stay dynamic across projects:
Runtime placeholders — replaced with actual file paths when a project runs data validation.
Script injection markers — define where Metaforms-generated scripts are injected into your template at runtime.
Getting Started
Navigate to the Templates section under the Build tab, then switch to the Data Validation tab to view and manage your data validation templates.
Creating a Template
Step 1: Click New Template and enter a descriptive name. As with survey programming templates, name it based on the team, client, or validation workflow it supports — for example, "Client B - Post-Field Validation" or "Standard DV Template."
Choose Dimensions as the tool.
Building the Template Content
After creation, you'll enter the template editor where you define your validation files and configure the markers.
Adding Validation Files
Step 2: On the left panel, import or create your validation files (e.g.,.dms files). You can also import files from an existing template to use as a starting point.
Runtime Placeholders (File Path Markers)
Step 3: Use the tools on the right to insert runtime placeholders into your scripts. These are {{…}} tokens that act as dynamic input paths — they get replaced with the actual file paths when a project runs data validation.
Click Insert next to the placeholder you need:
{{INPUT_DATA_FILE_PATH}}
Replaced with the path to the project's data file at runtime
{{INPUT_METADATA_FILE_PATH}}
Replaced with the path to the project's metadata file at runtime
Script Injection Markers (Metaforms Script Markers)
Step 5: Insert script injection markers to define where MetaForms-generated scripts should be injected into your template at runtime. Each marker has a Section ID — scripts whose section matches are injected into that specific marker. Use default for scripts that don't match any specific marker.
Available Section IDs include: default, property_check, screenout, and others depending on your setup.
The marker block looks like this in your script:
You'll need to mark where generated scripts are injected at runtime—validation logic will lie between these markers when the template is applied to a project.
Key distinction: Runtime placeholders (
{{…}}) are for file paths that change per project. Script injection markers (START/END: METAFORMS SCRIPT) are for code blocks where you'll need to insert the validation scripts. Both are necessary for a fully functional template.
Saving the Template
Step 6: Once you've configured your files, placeholders, and injection markers, click Save to finalize the template.
Using a Template in a New Project
Step 1: Create a new project, choose Data Validation, and select Dimensions as your validation type.
Step 2: Under Templates, select the template you want to use and click Next.
Step 3: Select your variable definition and data files, then enter the required file paths. The runtime placeholders in your template will be automatically populated with these paths, and the project will be ready for validation.
Last updated
Was this helpful?