Top > Using import templates
A data map describes how the columns in your source data are mapped to the properties of the object. A data map can be saved as an XML template to facilitate repetitive import tasks, such as imports every month from a financial system. A template is created or modified during the process of importing data. A template created and saved during a csv import can be reused in a SQL Server import, and vice versa, as long as the headers match the data being imported. A template also includes details about the source, such as the SQL Server connection, the SQL query entered, the source CSV filename and LDAP parameters. Even if you modify a template for csv that was originally intended for a SQL Server import, the template will remember its last SQL Server connection and query details. Since a template contains all the information required to perform an import, you can run an import directly from any template (All Import Templates view).
Only individuals with Service Manager roles of Author and Administrator can save templates during the import process.
One use for templates is to create different objects from the same data. Even though your source data may contain columns that are applicable to multiple objects, such as a hardware asset, a cost center and a location, use a template to create one type of object from that data. For example, one template can create a cost center object from your data. Another template could create a hardware asset. Both templates would create their objects from the same source data.
The Last modified time in the All templates view is not the server time. It is the current GMT.
If you modify a csv after creating a template from it, such as changing a header or removing a column, an error is generated during the next import of the csv. You can correct the error by remapping the affected property of the object you are creating. In the case of a renamed header, you would simply remap the property to the new header name.