Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Introduction to Importing customizations

The import feature of the Noetix Views Workbench (NoetixViews Workbench) can be used to import a package that contains customizations exported from a NoetixViews Workbench installation to an environment in the same or another NoetixViews Workbench installation. However, you cannot import only a legacy package, a legacy package is always imported along with the managed views. For information about exporting and using customizations across environments within a NoetixViews Workbench installation, see Promote a Package in "Manage Packages".

Depending on your requirements, you can decide to import both the legacy scripts and managed views or only the managed views from the source package. The Import Customizations topic discusses the concept and procedure related to importing customizations.

IMPORTANT: The import process affects the views, packages, and scripts in the target environment. Therefore, if any object that is being imported to the target environment is currently being edited there by another user, the NoetixViews Workbench will display a message that it has been locked, and that you will have to wait for the other user to finish modifying it. If Stage 4 has failed for the underlying NoetixViews schema, you may still be able to access the environment to modify views and correct customizations. The environment can be accessed if the N APPLICATION OWNERS table has records, and the CURRENT CHECKPOINT LABEL column in the N VIEW PARAMETERS table returns the INSTALL COMPLETE, META DATA LOAD, or POST VIEW CREATE value. Alternatively, instead of performing these checks, contact insightsoftwareSupport.

For information about exporting customizations, see Introduction to Exporting Customizations.

Published:

Introduction to Importing customizations

The import feature of the Noetix Views Workbench (NoetixViews Workbench) can be used to import a package that contains customizations exported from a NoetixViews Workbench installation to an environment in the same or another NoetixViews Workbench installation. However, you cannot import only a legacy package, a legacy package is always imported along with the managed views. For information about exporting and using customizations across environments within a NoetixViews Workbench installation, see Promote a Package in "Manage Packages".

Depending on your requirements, you can decide to import both the legacy scripts and managed views or only the managed views from the source package. The Import Customizations topic discusses the concept and procedure related to importing customizations.

IMPORTANT: The import process affects the views, packages, and scripts in the target environment. Therefore, if any object that is being imported to the target environment is currently being edited there by another user, the NoetixViews Workbench will display a message that it has been locked, and that you will have to wait for the other user to finish modifying it. If Stage 4 has failed for the underlying NoetixViews schema, you may still be able to access the environment to modify views and correct customizations. The environment can be accessed if the N APPLICATION OWNERS table has records, and the CURRENT CHECKPOINT LABEL column in the N VIEW PARAMETERS table returns the INSTALL COMPLETE, META DATA LOAD, or POST VIEW CREATE value. Alternatively, instead of performing these checks, contact insightsoftwareSupport.

For information about exporting customizations, see Introduction to Exporting Customizations.

For an optimal Community experience, Please view on Desktop
Powered by Zendesk