Import the exported file to Target Environment - EcoSys - Version - Administration & Configuration - Hexagon

EcoSys Configuration Migration

Search by Category
Administration & Configuration
EcoSys Version

After exporting the tagged objects from the source environment, you must import the file to the target environment:

  1. From the target environment, go to Configuration > Migration Management.

  2. Set the ‘Tag’ parameter to any value.

    The Tag created in the source environment does not need to be manually created in the target environment and will be created after a successful import.

  3. From the Import tab, click the Sheet icon and select Import or click the Import icon to import the .ecm file.

  4. Click Choose file and select the .ecm file previously downloaded.

  5. Select any of the following options and click OK:

    • Create New/Update Existing- Select this option to create new file or update the existing file.

    • Create New/Fail Existing - Select this option to create new file. If the file already exists, an error in displayed in the logs that the file already exists, so can't create a new file.

    • Create New/Ignore Existing - Select this option to create new file or ignore the existing file.

  6. Once the import completes, navigate to Admin > System Status & Logs > Batch Job Log and select the Batch Job that corresponds with the import.

  7. Review all messages within the log to ensure all failures and warnings are resolved.

    For example, migrating Custom Fields without first creating the Custom Field Type in the target environment will result in a failure.

  • Tag Names are not case sensitive and must begin with a non-numeric character

  • When migrating Custom Fields, if the Custom Field Group and subject area assignments exist, it will be merged with an attempt to maintain the sequence number during the import.

  • If the sequence number is already set for a different Custom Field in the target environment, the sequence of the new Custom Field will be incremented by 10.

  • Tagged Screen Layouts will not export dependent objects that are not also tagged. Instead, only references to the objects are exported. Those referenced objects must be tagged as well.

  • When importing .ecm file that contains multiple object types, imports are automatically processed in an intelligent sequence so that the most dependent objects are imported first.

  • When migrating a report that includes an Excel template, the Excel template will export/import along with the report. There is no need to manually migrate the Excel file.

For the migration of Versions:

  • If the Version pre-exists on the target system, the import will not update the Active Flag, Hide if not Aliased Flag, Major Period Start/End, Locked with Actuals Flag, Locked Periods or Exchange Rate Table settings.

  • If the Version Type does not exist, it will create the Version Type.

  • For the Applies To tab, the System Flag is never migrated. Migration will never remove an Applies To version setting in the target system.

  • When migrating a Version, if the target system does not have the Exchange rate table set on the Version, the Exchange Rate table will be created in the target system. Exchange rate table rates are not migrated as part of this process.