Top > Using import templates > Loading import templates

Loading import templates

An import template, from version 1.2 or later, that is saved as XML can be loaded into another Service Manager console and used to import data. You can import a single template or multiple templates either through the task or the PowerShell cmdlet (Import-ProvanceDMPTemplate). Although the cmdlet is designed to import a single template, you can import a directory of files using the native piping ability of PowerShell (see PowerShell sample calls).

When they have identical names, an import template replaces an existing template.

To load import templates using the task:

  1. Go to the Data Management workspace > Import view.

  2. In the Tasks pane, click Load Import Template. The Load Import Tem­plate form opens.

  3. Click the Add Files button to find and add one or more XMLs file to the list. When you load a template file that has the same name as an existing file a warning is given. You can choose to continue with the import or remove the duplicate file from the list.

  4. Enter a Display Name and a Description. The name and description should provide enough information about the template so you can choose it easily in a list.

  5. Click OK to load the template file or files into the console. Loaded tem­plates are found in the View All Templates view.

To load an import template using a PowerShell script:

  1. On the Service Manager management server where you installed the Data Management pack, click the Start menu and search for the Provance folder.

  2. Open the Provance folder and click Provance Data Management Shell. A command prompt opens with the cmdlet loaded.

  3. Enter the import command and its parameters to run the cmdlet, such as Import-ProvanceDMPTemplate -LiteralPath "c:\mypath\myfolder\MyTemplateDefini­tion.xml" -Name MyImportedTemplate -OnErrorAction skip. For more details, see PowerShell sample calls and  PowerShell import template parameters.


If you wish to run the cmdlet from a command prompt without directly access­ing the management server, it needs to be loaded first, see To load the PowerShell cmdlet:.