Container export and import information related to FootPrints Service Core 12.1.01 and later

Manage Support IDs

Use checkboxes to 'Remove support IDs/Users' or 'Allow to create Cases'
Support IDs for BMC Customer Support Site Guest User
Profiles Which Include    Back to All Support IDs
 

Knowledge Article

Container export and import information related to FootPrints Service Core 12.1.01 and later
FootPrints
FootPrints Service Core 12.1.01 and later
FootPrints
FootPrints Service Core 12.1.01 and later
FootPrints
FootPrints Service Core 12.1.01 and later
The following information pertains to FootPrints Service Core versions 12.1.01 and later versions:

With the release of FootPrints 12.1.01, in order to create a better experience with exporting and importing Container templates, it will not be possible to create a container in version 12.1.01 or later by importing an xml template file that was created by exporting a Container which existed in FootPrints 12.1.00.006 or earlier version to a template file. The same is true for the reverse scenario, in that a version 12.1.01 or later template file cannot be imported into 12.1.00.006 or prior.

If such an attempt is made to do so, the following example error message will be displayed:

Message: Template has an unsupported version number: "1.0"

An image of the error details follows:

User-added image

The message is expected to appear in any scenario where the Template version number differs between the Application version of FootPrints where the template .xml file was exported from and the Application version where it was imported to.

Template Version Numbers

It should be noted, the version number in the message refers to the Template version number, not a FootPrints Application version number.


Template version number 1.0 indicates the template xml file was exported from FootPrints Service Core version 12.1.00.006 or prior.

Template version number 2.0 is associated with FootPrints Service Core version 12.1.01 or later version.

If a question arises as to which version of FootPrints Service Core a Container was exported from and which Template version number it contains, the following can be done:

Open the .xml file in a text editor such as notepad, Wordpad, Notepad++, etc.

The 2nd line of the file should look similar to the following:

User-added image

In this example, the Template version number is "2.0", indicating it was exported from a Container of Footprints Service Core 12.1.01 or later.​

Be advised, it is not recommended or supported to attempt to change the Template version number in the file to "workaround" the issue. Unforeseen results may occur.

 
If there is a desire to import Container template files into FootPrints 12.1.01 which were created by exporting from FootPrints 12.1.00.006 or prior and avoid the message seen above regarding the unsupported Template version, it is suggested to do the following:

If an existing Container, currently configured as desired on a 12.1.00.006 or prior version needs to be imported into a newer version (12.1.01 or later) of FootPrints, do the following:
  1. Upgrade the install of FootPrints where the Container was originally exported from to the same version of FootPrints where the Container template file will be imported into.
     
  2. Export the Container into a template file.
     
  3. Import the template file into the newer version install of FootPrints.

If you are in possession of a Container template file (which may have been saved as a backup) that is known to be properly configured as desired, BUT the Container where it was originally exported from either no longer exists or has significant changes to it (i.e. not needed for importing) and there is a need to import that Container file into a newer FootPrints system, do the following:
 
  1. Create a new Container in the original install of FootPrints using the Container template file.
     
  2. Upgrade the original install to a version of FootPrints that matches the version of where the Container will be imported into.
     
  3. Export that newly created Container to a template xml file (which means the Template version number should now match the Template version number of where it will be imported).
     
  4. Import the template file to create a Container in the newer version FootPrints install.
Attachment(s):