Search the Omeda Knowledge Base

Data Loader – Using Templates (coming soon)

Overview

Templates are special Field Mappings that can be used to quickly map incoming files. They are tied to the Profile in which they created and cannot be used across Profiles. This article assumes the reader knows how to access various locations in Data Loader.

Make a Template from an existing Field Mapping

The Edit Mapping option of a file will bring up the Field Mapping dialog. This is how the User

 

Figure-1

To make a Field Mapping become identified as a Template, simply click the checkbox next to Use this as a Template for other Files? (Figure-1.A). This will do a quick save to make the Field Mapping available for other actions.

The name of a Field Mapping/Template is defaulted to the name of the file. This can be changed at any time by clicking the little edit icon next to the Template Name (Figure-1.B). Doing so will allow it to be edited.

 

Figure-2

When the name is satisfactory, the user can hit the checkbox button to the right of the input field. This will do a quick save. Hitting the cross button will cancel any changes and revert the area back to a read-only state.

Applying a Template to an existing Field Mapping

As long as the Field Mapping is editable, Templates can be applied to them. This is done by clicking the Apply a Template button in the top left. This will bring up a dialog (Figure-3, below) for the User to pick the Template and the pieces of it they want to apply.

 

Figure-3

Once the template is selected (Figure-3.A), the user can decide which aspects of the the template to use (Figure-4.A). The default is to apply everything about a template to the Field Mapping that is being accessed. If the User is unsure if the Template has the selected features, they can leave it checked and the program will account for the scenario. The main time a User would want to unselect a feature to be copied is when they know for sure they don’t want that feature to be applied; otherwise it is safe to leave it selected.

 

Figure-4

Each piece of the template is essentially an available step. For example, if the only piece selected is Field Mappings, then all of the fields will be mapped, which may create an additional step the user will need to finish after the template is finished being applied. The last step of applying the Template is to check to see if the file is now ready to process. If it isn’t, then that should become evident by the various warnings and errors displayed throughout the application. If it is, then the status will be changed to Ready to Process.

When the Template is applied, it’s doing some pretty strict comparison of field names. Fields that don’t a field in the Template won’t be modified; they will remain as they were prior to attempting to apply the Template. In this way, a User could apply multiple Templates to a Field Mapping, however they would want to be careful about any name overlaps.

Use a Template with a new File

 

Figure-5

When uploading a file, one of the options is to use a Template. The Template chosen can be viewed as a baseline. If the incoming file does not have fields that match the Template, a new Field Mapping is created instead. The Template will then be applied to the new Field Mapping to the extent that it can. This includes creating anything extra for all of the steps of a Template.

 

Last Updated On June 19, 2019
Knowledge Base Feedback