The Template Library in Datarails provides users with a curated collection of best-practice templates that accelerate reporting, planning, and analysis. You can access it by clicking the Template Library from the left-hand navigation panel.

What can you do with a template?

Each template listed in the library offers two main actions:

Download (Preview-only)

Download the template as an Excel file for review purposes.

• No Datarails connections
• No Data Mapper
• No live elements or dynamic links
• Intended for offline review to evaluate structure and design

This version does not contain live data or automation. It's static and is not linked to your workspace's data. 

Import Template (Recommended)

This option fully integrates the template into your Datarails workspace. 

When you import a template:

• The full Filebox is added to your workspace
• The Data Mapper, including field mappings and table logic, is automatically connected
• Version tags and metadata are included
• All Datarails functions (DR.GET, DR.YTD, etc.), Excel tables, and dynamic ranges are bound to your workspace's dataset

Highly recommended: This is the production-ready version that enables automation and reporting with your live data..

How template mapping works

During import, the system attempts to auto-map all tables and fields in the template to your workspace's existing datasets.

Table Mapping

If a table from the template (e.g., Headcount) cannot be found in your dataset:

1. You’ll be prompted to assign a system name to one of your available tables
2. A list of unmatched tables will appear
3. You can choose the appropriate match from your data.
4. Tables can only be mapped to one system name. Consequently, only tables lacking a designated "system name" will be accessible for mapping. 

Note: a single template may use multiple tables — each one must be mapped.

Field Mapping

Each table in the template contains multiple fields (columns). These must also be matched:

1. If a field (e.g., Department) cannot be found by system name in your data, you'll be asked to assign one
   • You can only assign system names to fields that don’t already have one.
   • The counter at the top left indicates the number of tables remaining to be mapped.
   • All fields used in the template are accessible at the top of the screen. Hover over the information icon to view the source field description.
2. You will need to map all template fields (e.g., ID, Region, Status) to your table's corresponding fields. Each row provides details about your table's fields, such as data type, five random values, and a description.
   • Fields with an existing system name will not be available for reassignment.
3. Once all fields for a given table are mapped, the "next" button will become available in the bottom right corner. The "Import" button will then appear when the mapping of the last table is complete.
   
4. Finally, assign the chosen version tag to the imported version. The newly imported version will be tagged according to your selection.
   
5. After clicking "Import," please wait for the green confirmation message to appear in the bottom right corner of your screen. This message will contain a link to the newly created Filebox. Alternatively, you can always locate the Filebox within your workspace. The file will automatically download to your computer. 
   
   

How DR.GET() and other functions behave

Once imported, any Datarails Excel function (like DR.GET, DR.QTD, DR.YTD, etc.) will reference system names, not original field labels.

System name reference

• Regular field name reference: DR.GET(value,"[Department]")
• System name reference: DR.GET(value"{department}")

The use of {} indicates that the field is being referenced via its system name, ensuring consistent mapping across organizations, regardless of naming conventions.

Updated September 03, 2025 11:43