Import Organization | Vantage CX - Importing an Organization - Vantage Customer Experience

Vantage Customer Experience User Guide

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Vantage Customer Experience
Release Number
1.6
Published
October 2023
Language
English (United States)
Last Update
2023-10-26
dita:mapPath
hbt1563223944614.ditamap
dita:ditavalPath
oyf1565965838286.ditaval
dita:id
tmo1562969305444
Product Category
Teradata Applications

Any environments contained in the import file overwrite the corresponding environments in the organization that you selected.

The import process overwrites all objects such as attributes, which affects all environments in the organization. This can cause objects in environments that are not overwritten to break if those environments refer to global attributes that no longer exist.

Importing an organization will overwrite the contents, if any, of each environment in the target Organization, including Third Party Profile passwords and API Connections. You should also be aware of the following:
  • If a Connection with the same name exists in the target organization, the import will not overwrite the existing configuration data.
  • After importing an Organization, Third Party Profile passwords as well as API Connection usernames and passwords must be re-entered, if applicable. See Third-Party Profiles and API Connections.
  • Importing the Organization data from a specific environment (Dev, QA or Production) will not be successful if any of the expected global objects (such as attributes, objectives etc.) are not present in the import data source.
  1. Log in to the organization you want to import.
  2. Select "" > Status > Current organization.
    This page shows organization information.
  3. Select Import/Export, and select Import Org Data To File.
  4. Select Choose File and select the import file on your local machine.
  5. Select if you want to import any messages contained in the import file.
  6. Select if you want to import simulation environments.
  7. Select if you want to keep a copy of existing simulation environments. Note that the reports and contact history for the environment will remain in the database but won't be accessible by the application.
    If not selected, the existing simulation environment will be deleted even if you don't import any simulation environments.
    If you select both Import Simulation Environments and Keep Copies of Existing Simulation Environments, you must rename the existing environment if the imported environment has the same name.
  8. Select Import.
  9. Select Confirm. A success or failure message is displayed.
    Any environments contained in the import file overwrite the corresponding environments in the organization that you selected. You must also re-enter any Third Party Profile passwords and connection details, if applicable.