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

Introduction to Exporting Customizations

The export feature of the Noetix Views Workbench (NoetixViews Workbench) can be used to export all the customizations or a package in an environment. This feature can be used for exporting customizations across NoetixViews Workbench installations. However, you cannot export only a legacy package, a legacy package is always exported 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".

When the export feature is used, the customizations are exported as a compressed file that you can save in your computer. The compressed file contains XML files corresponding to the customized objects, such as the original and latest versions of managed views and legacy package. The customizations can be exported by using the following two methods:

IMPORTANT: If the package, view, or script that you try to export is presently being edited 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 importing customizations, see Introduction to Importing Customizations.

 

Published:

Introduction to Exporting Customizations

The export feature of the Noetix Views Workbench (NoetixViews Workbench) can be used to export all the customizations or a package in an environment. This feature can be used for exporting customizations across NoetixViews Workbench installations. However, you cannot export only a legacy package, a legacy package is always exported 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".

When the export feature is used, the customizations are exported as a compressed file that you can save in your computer. The compressed file contains XML files corresponding to the customized objects, such as the original and latest versions of managed views and legacy package. The customizations can be exported by using the following two methods:

IMPORTANT: If the package, view, or script that you try to export is presently being edited 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 importing customizations, see Introduction to Importing Customizations.

 

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