Data Mapping Templates

Use Data Mapping Templates to map column headers in source files to the Yarken fields that receive the data. Reuse templates across manual and automated file uploads to keep field mapping consistent.

Go to Admin > Pipelines > Data Mapping Templates to create and manage templates.

A Data Mapping Template does not load data by itself. It defines how Yarken maps a source file when you upload the file manually or process it through a file-based pipeline.

What you can do

Use Data Mapping Templates to:

Map source file columns to Yarken destination fields.
Reuse the same mapping during future file uploads.
Standardize recurring data loads across teams and source systems.
Reduce repeated manual field mapping.
Prepare file-based data for Automate and cloud storage pipelines.
Create a template before an upload or save one during the upload workflow.
Preview, search, edit, and delete templates where supported.
Use the selected Destination Table to identify the Yarken data type that receives the mapped fields.

Before you begin

Confirm the type of data you want to load.
Prepare a sample file with the same column headers as your recurring source files.
Include all mandatory columns required for the selected destination.
Use consistent source column names across future files.
Confirm that you have access to manage Data Mapping Templates.

Choose the correct Destination Table. It controls which Yarken fields are available for mapping and determines the target data type for the upload.

How Data Mapping Templates work

Workflow	How the template is used
Manual file upload	Select a saved or predefined template to apply mappings without mapping every field again.
Automate	Use an existing template, replace one, or create one from a previously uploaded file.
BASIC cloud storage pipeline	Select a template when you configure the pipeline. Yarken applies it each time the pipeline processes a file.
BASIC API pipeline	Supported API pipelines use predefined mappings and do not require a custom Data Mapping Template.
ADVANCED file-based integration	Yarken automatically applies the required template when an Advanced file-based integration requires source-to-destination mapping. You do not configure or edit the template.

After you save a template, it becomes available for supported uploads that use the same destination data type.

Not every integration requires a Data Mapping Template. API and event-driven integrations may use predefined mappings or another integration-specific process.

Supported upload types

Data Mapping Templates support a range of file-based data types.

View supported upload categories

Master data — Accounts, Cost Centers, Employees, Vendors, and Products.
Assets and asset mappings
Allocation and rule files — Cost Pool Rules, Tower Rules, and Solution Rules.
Cloud consumption — Azure, AWS, and FOCUS files.
Financial data — Spend and budget data.
Companion Metrics
License or product usage

The upload types available to you depend on your Yarken environment and the selected Destination Table.

Create a Data Mapping Template

Create a template from the Data Mapping Templates page when you want to define the mapping before you upload or automate a file.

Step 1: Open Data Mapping Templates

Go to Admin > Pipelines > Data Mapping Templates.
Select + ADD NEW.

Step 2: Enter the template details

Field	Description
Name	Enter a clear name that identifies the data type, source, or file structure.
Destination Table	Select the Yarken data type that will receive the mapped fields.
File	Upload a sample file containing the source column headers. Include every mandatory column required by the destination.
Mapping Fields	Review the source fields and assign them to the appropriate destination fields.

*Define the template name and destination data type*

Step 3: Review the mapping

Confirm that the sample file contains the expected source fields.
Map each required source field to the correct Yarken destination field.
Review mandatory fields before you continue.

Do not save a template with missing or incorrect mandatory mappings. Future uploads may fail or load data into the wrong fields.

Step 4: Save the template

Select SAVE.
Confirm that the new template appears on the Data Mapping Templates page.

The template is now available for supported manual uploads, Automate workflows, and file-based pipelines.

Create a template during a manual upload

Save the mapping during a manual upload when you want Yarken to reuse the mapping for future files with the same structure.

Open the applicable data upload screen.
Upload the source file.
Map the required source fields to the destination fields.
Select Save field mapping for automation.
Select FINISH to complete the upload.

Yarken saves the mapping as a reusable template for that file type. You can select it during future manual or automated uploads.

Save field for automation-20251208-113012.png — *Save a manual mapping for future uploads*

Create or replace a template with Automate

You can start an automated file-ingestion setup from the UPLOADED FILES tab when a previously uploaded file contains the correct mapping structure.

Open the applicable UPLOADED FILES tab in Yarken Designer.
Find the uploaded file.
Select the Automate icon.
Choose whether to use the existing mapping, create a new template, or replace the current template where available.
Complete the remaining automation and pipeline setup.

Yarken uses the field mapping from the uploaded file as the mapping for future pipeline uploads of that file type.

Automate creates or uses a pipeline behind the scenes. Manage the generated pipeline from Admin > Pipelines > Pipelines.

For the complete workflow, see Automate.

Use a template with a pipeline

File-based cloud storage pipelines require a Data Mapping Template.

Create or identify the template for the destination data type.
Go to Admin > Pipelines > Pipelines.
Create or edit the applicable BASIC cloud storage pipeline.
Select the Data Mapping Template during pipeline setup.
Complete the schedule and pipeline details.
Save and activate the pipeline.

Yarken applies the selected mapping whenever the pipeline processes a source file.

If the source file structure changes, review the template before the next pipeline run. A mismatch between the source headers and saved mapping can cause missing or incorrect data.

For pipeline setup, see Create BASIC pipelines.

Manage Data Mapping Templates

From the Data Mapping Templates page, you can:

Search and filter templates.
Review the template name and destination data type.
Preview mapped fields.
Edit supported mappings.
Delete templates that are not referenced by a pipeline.

Edit a template

Edit a template when a supported source file structure changes.

Select the Edit icon next to the template.
Review the Name, Destination Table, sample file, and mapping fields.
Update the supported mapping fields.
Select SAVE.
Test the related upload or pipeline with a validated sample file.

Cloud Consumption restriction

You cannot manually add or modify mapping fields for system-defined Cloud Consumption templates, including Azure, AWS, and FOCUS file types.

Cloud Consumption templates

When you use a Cloud Consumption Data Mapping Template in a pipeline, Yarken displays an additional Date Format step during pipeline setup.
The selected format is saved with the template and used when Yarken processes Cloud Consumption files.
Yarken also displays a reminder to configure Upload Rules for Accounts, Cost Centers, and Vendors before you publish Cloud Consumption data to Spend.

You can edit supported non-cloud-consumption templates even when an active pipeline uses them. Review the next pipeline result after you change a mapping.

*Review editable and system-defined mapping behavior*

Delete a template

Delete a template only when it is no longer required.

You cannot delete a Data Mapping Template used by an active or inactive pipeline. Update or remove every pipeline that references the template before you delete it.

Identify the pipelines that use the template.
Update those pipelines to use another template, or delete the pipelines when they are no longer required.
Return to Data Mapping Templates.
Select the Delete icon.
Confirm the deletion.

After the template is used

After an upload or pipeline uses the template:

Confirm that the upload or pipeline completed successfully.
Review the processed file in the applicable UPLOADED FILES tab, where available.
Open the Yarken feature associated with the selected Destination Table.
Verify that the expected fields and records are available.
Refresh the affected cube if you need to review the data immediately in Reports or Analytics.

The Destination Table identifies the target data type. The upload or pipeline determines when the data is processed and made available in Yarken.

For refresh guidance, see Cube refresh and best practices for Pipelines.

Best practices

Use a clear naming convention that identifies the source and destination data type.
Use a sample file that matches the structure of future source files.
Include every mandatory field in the sample file.
Keep source headers consistent across recurring files.
Use separate templates when source systems use different column structures.
Review mappings after a source system changes its export format.
Test a new or updated template before relying on a scheduled pipeline.
Do not delete a template until you confirm that no pipeline references it.

Troubleshoot Data Mapping Templates

Issue	What to check
Required source fields are missing	Confirm that the sample file includes all mandatory column headers for the selected Destination Table.
Fields are mapped incorrectly after an upload	Compare the current source headers with the saved template. Update supported mappings and process a corrected file.
The source file structure changed	Review renamed, added, or removed columns. Update the template before the next manual or automated load.
You cannot edit Cloud Consumption mappings	Azure, AWS, and FOCUS Cloud Consumption mappings are system-defined and cannot be changed manually.
You cannot delete a template	Check for active or inactive pipelines that reference it. Update or remove those pipelines first.
A pipeline processed the file, but expected data is missing	Confirm the pipeline succeeded, verify the Destination Table and field mappings, then refresh the affected cube.
The wrong data appears after ingestion	Verify that the correct template and Destination Table were selected. Correct the mapping before you process the file again.

For additional help, see Troubleshoot Pipelines and integrations.

Related content