Overview
Asset templates allow you to standardize asset information across all locations in your Limble account by using a pre-determined group of fields. This article will walk you through creating a template, configuring template settings, applying the template to assets, and deleting a template.
The asset template feature is currently in the "early access" phase. In the "early access" phase, Super Users can create one account-wide asset template which can be applied to new and existing assets at all locations.
Why Early Access Testing Matters
Early access testing allows us to refine and enhance asset templates before a full release. Your feedback helps us:
Identify usability improvements, which makes interactions smoother for all users.
Prioritize future enhancements, so we can focus development efforts on the most valuable updates.
We’d love to hear your feedback!
Use this Google feedback form anytime to log issues and share use cases.
Your input is invaluable in shaping the future of asset templates. Thank you for being part of this early access program!
Functionality will continue to expand in the coming months. This article and video walkthrough will be updated in real time to reflect those changes. If you experience any issues, reach out to our support team.
Table of Contents
Creating an Asset Template
Only Super Users can create and configure asset templates.
Navigate to the Asset Templates page by clicking on the template icon from the navigation menu.
Click "New Asset Template."
When you create a new template, it will show up in the Templates pane. In early access, this template will always be called "Master Template."
Until you publish the template, it will be considered a draft and not visible to users. This is indicated next to the template name.
From here, you'll take the following steps:
Add Templated Fields
Add Templated Fields
First, create your templated fields. The process is the same as creating a location-based field:
Click "Add & Edit Fields."
In the new window, click "Create New Field."
Name your field, select a field type, and click "Create."
Repeat this process until all desired fields are created.
(Note: while you do not have to use a field in a template, once it is created it cannot be deleted.)
Edit Field Settings and Configure the Order
Edit Field Settings and Configure the Order
After you've created a field, you can edit its settings, such as lock or show/hide settings, show on tasks, unique values, etc.
Click "Add & Edit Fields."
In the new window, click the pencil icon next to the desired field.
From here, you can configure field settings.
(Note: for date field reminders, you can only assign the “Send to” to a role, such as Manager, Technician, or a custom role.)
Use the four-way arrow icon to drag and drop fields in the desired order. This is the order they will appear in the asset card.
Publish the Template
Publish the Template
Once you have configured your fields and field settings, publish your template.
Make sure you are ready to publish your template. In early access, a published template, templated fields, and field settings will no longer be editable.
To make any changes after a draft is published, you will need to delete your template and start again.
When you're ready to publish the template, click “Publish Template.”
In the new window, confirm your choice by clicking “Publish.”
Once the template is published, you cannot make any changes. You can view field settings by clicking the pencil icon next to the field.
Configuring Template Settings
Once a template is published, make sure to enable templates in your account. By default, templates are disabled.
To enable templates, click the Settings button or the button in the templates pane.
In the new window, click on the dropdown to choose your templates setting:
“Required” will always require templates to be used when manually creating new assets at all locations on your account.
“Optional” will allow users to select a template when manually creating a new asset, but not require a template to be used.
“Disabled” will hide templates from users.
Choose your desired option and click "Confirm."
Once templates are enabled, whether required or optional, templates will be visible when a user is adding an asset.
If you disable templates, any assets you created using a template will still have those fields. Users can still update their values and include them in tasks. However, field settings will not be accessible or editable.
(Note: if you enable templates and use the bulk import or update systems with your assets, some exclusions apply. Please read about those processes carefully in the section below before performing an import or update.)
Applying a Template to Existing Assets
You can apply your template to existing assets and merge data from location-based fields with templated fields.
Applying a template to existing assets can only be done by a Super User from the Asset Templates page.
Apply Template Workflow
Apply Template Workflow
From the Asset Templates page, click the “Assets” tab. Then click “Link Assets.”
Applying templates to assets is done one location at a time. Select your desired location and click “Next: Select Assets.”
Select the assets you want to apply to the template and click "Next: Merge Asset Fields."
Next, you can merge location-based fields and values with templated fields. While merging fields is optional, it is highly recommended.
If you do not merge fields for the assets you selected in the previous step during the apply template process now, you cannot do it later -- so be sure to review your assets and fields carefully.
The right column shows fields in this template. These will be applied to the assets selected in step 3, even if you don't merge any fields.
In the left column, click to expand the dropdown to select the location-based fields to merge with each templated field.
You will only be able to choose from fields that meet the requirements.
Click the checkbox next to the fields you want to merge.
Once you have selected fields to merge, click "Next: Review + Confirm."
The final step is to review and confirm your changes. The summary of your choices will be listed here.
Click the checkbox next to each item to confirm your selections. Then, click "Apply Changes" to link assets to the template and merge fields.
Changes are applied in the background, so you may leave the Asset Templates page and return at any time to check the progress.
Field Merge Requirements
Field Merge Requirements
Fields can only be merged if:
They are the same field type. For example, a text field called "Mileage" cannot be merged with a number field called "Mileage."
They have not already been selected to merge with a different templated field. This 1:1 merge allows the system to maintain the field value and history from the location-based field.
What happens after a field is merged?
What happens after a field is merged?
Field merging only impacts the assets you selected in this workflow.
Here's what to expect:
Field values and history will move over to the new templated fields
The location-based field will be removed from applicable assets if it was merged
The location-based field can still be used at its location for other assets
Dropdown Fields
If you are merging a dropdown field, the current value and history will move over, but the dropdown options may differ.
If you configured different dropdown options for the templated field, consider performing a bulk update to update field values accordingly.
Reporting, Work Request Portal, & Workflow Automations
If you are merging fields used in custom dashboard widgets, filtering by asset field in the work request portal, or workflow automations, you may need to reconfigure them.
If the original location-based and new templated field do not share the exact same name, you will need to update reports, WRP asset filtering settings, and automations to use the new templated field.
Why can't I apply my template to some assets?
Why can't I apply my template to some assets?
The most common reason for not being able to apply your template is due to field merge conflicts.
This occurs when an asset has multiple fields that are being merged with a single templated field, preventing the system from determining which field data to retain.
If assets cannot be merged, you'll receive a warning message during the "Review + Confirm" step. To see which assets cannot be merged, click "View error details."
In the new window, you can click on each asset to remove the field(s) that you don't want to merge.
If you take no action, the template will be applied to all other assets that do not have merge conflicts.
Creating New Assets Using a Template
Once templates are enabled on your account, you can use your template when creating new assets.
Navigate to the Manage Assets page and click "Add an Asset."
(Note: Regardless of template settings, location-based field settings will still be honored. For example, if you’ve configured a location-based field to automatically be included with new assets, that field will still be added to all new assets.)
Creating Assets When Templates are "Required"
Creating Assets When Templates are "Required"
Name your asset.
Then, choose between “Use a Template” or “A Copy of an Existing Asset.”
If you select “Use a Template” your master template will appear. Then, click “Add.”
If you select “A Copy of an Existing Asset” you will only be able to select from assets that are linked to a template.
Click on the asset you’d like to copy, and click “Add.”
If the asset you selected has child assets, you’ll be taken to a new window.
If any of its children assets are not linked to a template, you will only be able to copy the top level asset. Do this by clicking “No, Copy only top level Asset.”
Limble will copy the templated fields and their field values (and location-based fields if the asset has any).
Creating Assets When Templates are "Optional"
Creating Assets When Templates are "Optional"
Name your asset.
Then, choose between "Blank Asset," “Use a Template,” or “A Copy of an Existing Asset.”
If you choose "Blank Asset" you will not use a template. Click “Add.” Once the asset generates, you will be able to choose from location-based fields.
If you select “Use a Template” your master template will appear. Then, click “Add."
If you select “A Copy of an Existing Asset” you will be able to choose from any asset at this location, even those not linked to a template. Limble will copy both the templated and location-based fields and their field values.
Click on the asset you’d like to copy, and click “Add.”
If the asset you selected has child assets, you’ll be taken to a new window.
You will have the option to copy the entire hierarchy, even if some children assets are not linked to a template. Make your desired selections to add your new asset(s).
Limble will copy both the templated and location-based fields and their field values.
If you duplicate an asset using the duplicate button, or add a child asset using the + button, template settings will still apply.
You will see the templated fields in the asset card. Templated fields are indicated with the template icon.
You can add and rearrange the order of location-based fields, but they will always appear after your templated fields.
Once a template is linked to at least one asset at a location, you will see templated fields in the edit visible columns tool.
You can include templated fields as part of your visible columns by checking the box next to the field name. Templated field settings will not be configurable from here.
When you create an asset using a template, it will be listed in the Assets tab on the Asset Templates page.
Bulk Importing and Updating Asset Fields
Templated fields can be used with Limble's bulk import and update systems.
Please read the following sections carefully before performing bulk imports and updates.
If you allow non-Super Users to perform bulk imports or updates, make sure to share this information with them.
Non-Super Users cannot access the Asset Templates page and would only be able to see templated fields if you've already created assets that use templates.
How to Perform a Bulk Import Using Templates
How to Perform a Bulk Import Using Templates
If you have enabled asset templates, please read this section in its entirety before performing a bulk import.
Performing a bulk import with templates is a similar to a typical bulk import. However, field names and import settings play a critical role in how your data is imported.
From the Manage Assets page, click "Import/Export." From the dropdown, select "Import Assets."
You will be taken to the import window. If asset templates are set to required or optional on your account, you will see a new option to "Prioritize Asset Template Fields."
If you use this setting, assets will be created using templated fields if they exist. Where templated fields don’t exist, the system will use fields at this location. To enable this, click the checkbox next to the setting name.
We recommend keeping windows open with your templated and location-based fields visible as you're building your import file to ensure the data imports as desired.
Expand the sections below to read more about how importing works with this setting.
Importing with "Prioritize Asset Template Fields" Enabled
Importing with "Prioritize Asset Template Fields" Enabled
This example walks through how importing could look with "Prioritize Asset Template Fields" enabled.
The following templated fields exist:
Mileage
VIN
Up/Down Status
And the following location-based fields exist:
Mileage
VIN
Model
Status
The user set up the sample import file to include the Mileage, VIN, Model and Status fields for their assets.
The user made sure to check the box next to "Prioritize Asset Template Fields" to enable the setting before importing their assets into Limble.
The newly imported assets include the following fields:
Mileage (templated field): This is a templated field because "Mileage" was the field name used in the import file, which matches a templated field.
VIN (templated field): This is a templated field because "VIN" was the field name used in the import file, which matches a templated field.
Model (location-based field): This is a location-based field because "Model" was the field name used in the import file, which matches a location-based field.
Status (location-based field): This is a location-based field because "Status" was the field name used in the import file, which matches a location-based field.
The system looks for exact name matches between column names in the import file and field names in the system. If the user wanted to use the templated field, they would have needed to name the column "Up/Down Status" to exactly match the templated field name.
If templated fields are prioritized, for dropdown fields, keep in mind that you can only use valid options for the templated field.
For instance, imagine you have both a templated and a location-based field named "Status." The options for the templated field are "Up" or "Down," while the options for the location-based field are "Up - Active" or "Down - Receiving Maintenance."
If templated fields are prioritized, you can only use "Up" or "Down" as dropdown options.
Importing with "Prioritize Asset Template Fields" Disabled
Importing with "Prioritize Asset Template Fields" Disabled
This example walks through how importing could look with "Prioritize Asset Template Fields" disabled.
The following templated fields exist:
Mileage
VIN
Up/Down Status
And the following location-based fields exist:
Mileage
VIN
Model
Status
The user set up the sample import file to include the Mileage, VIN, Model, and Up/Down Status fields for their assets.
The user made sure to uncheck the box next to "Prioritize Asset Template Fields" to disable the setting before importing their assets into Limble.
In the upload confirmation window, the user ignores the highlighted area and proceeds with their import.
The new assets include the following fields:
Mileage, VIN, and Model were all added using location-based fields.
Up/Down Status (new location-based text field): This is a new location-based text field because "Up/Down Status" was the field name used in the import file, which does not match an existing location-based field.
Even though a templated field with this name exists, the system did not map it because the setting to prioritize templated fields was disabled.
If a location-based field does not exist with the same field name, the system will follow typical behavior and create a new location-based text field.
You will be shown this in the import process before the upload is completed as the window appears above. If you do not want to create a new location-based field, edit your file and try your import again.
How to Perform a Bulk Update Using Templates
How to Perform a Bulk Update Using Templates
If you have enabled asset templates, please read this section in its entirety before performing a bulk update.
Bulk updates cannot be used to apply templates to assets. However, they can be used to update field values, regardless of whether or not the assets are using templates.
From the Manage Assets page, click "Bulk Actions." From the dropdown, select "Update Assets."
In the new window, download your asset list by clicking "List of Assets."
Before making changes, save a copy of your current list of assets. This ensures you have a backup to restore field data if needed.
Open your file. Templated fields and field data will be included in your export if they are linked to any asset at that location.
Performing a bulk update with templates is a similar to a typical bulk update, with two additional considerations:
You will see a new column named "Templated Fields - DO NOT EDIT OR REMOVE." If an asset was created using a template, the templated fields will be shown here.
Be sure to keep this column in your file. DO NOT edit, add, or remove field data. Doing so may result in loss of field data.
If both a templated field and location-based field exist with the same exact name, the data for both fields will export into one column.
In this example, the user has templated and location-based fields named "Mileage" and "VIN." The data has been consolidated into one "Mileage" and one "VIN" field respectively.
The new "Templated Fields..." column will tell the system which assets were created using a template, and where that field data needs to go.
In this example, the user is updating mileage for Vehicles 3 and 4 (location-based), and Vehicles 6 and 7 (created with a template). Their file looks like this before uploading:
In the update confirmation window, they can see assets that are being updated, and hover to see what info is changing.
When the updates are complete, the field data maps to the templated and location-based mileage fields for each asset respectively.
Deleting a Template
During the early access phase for this feature, in order to make any changes to your fields or their field settings, you must delete the existing master template and create a new one.
Navigate to the Asset Templates page. Click “Delete Template.”
A new window will appear to let you know the following actions will occur:
The template will be permanently unlinked from associated assets.
Fields and the data you’ve entered will not be deleted from associated assets.
Any assets you’ve created using this template will keep the fields from this template and the field values you’ve entered. You can continue to update the field value.
This does not mean the field will be treated as a location-based field. Even though the asset will no longer be linked to the template, the field itself is still a templated field. If the field settings are updated when configuring a new template, those will continue map to the field.
If you want to remove any of these fields from the asset, you will now have the ability to do so.If you copy an existing asset that was previously linked to this template, the templated fields will also be copied and the same logic will apply.
Fields in this template, including their settings, can be used again in a new template.
Confirm your choice by typing the number of linked assets in the provided field. Then click “Delete Template.”
Related Articles
Still don’t see what you’re looking for? Check out our YouTube channel for more tips and tricks! You can also reach out to us anytime at support@limblecmms.com.