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

Import Customizations

The import feature of the NoetixViews Workbench can be used to import managed views, legacy scripts, and other configuration-specific customizations to an environment in the same or another NoetixViews Workbench installation. You can import the managed views of a custom package or all managed views of an environment. Typically, customizations pertaining to the original and latest revisions are imported. You can also import the customizations pertaining to all revisions.

For an environment to be used as a target, at least Stage 4 should have been completed till the Get Passwords wizard is displayed for the underlying NoetixViews schema.

IMPORTANT: The customizations exported from an environment cannot be imported to a target environment if the Noetix Views (NoetixViews) version of the view revisions in the source is higher than the NoetixViews version of the target environment. If you try to import customizations to an environment that is based on an earlier version of NoetixViews, an error message will be displayed.

To import customizations

  1. On the NoetixViews Workbench home page, click Export/Import. The Export-Import » Choose Options page appears.

  2. Click Import customizations, and click Next. The Export-Import » Welcome page appears.

  3. View the information displayed on the page, and click Next. The Export-Import » Package Import Options page appears.

  4. Click Browse to navigate to the location of the .nvwx file that you saved and select the file, and click Upload. A message stating that the package has been uploaded successfully appears. The package details are displayed on the page.

  5. In the New Package name box, type a name for the package that is being imported. If the package already exists in the target environment, select the Overwrite a package with the same name in the target environment, if it exists check box.

    NOTE: If the package already exists in the target environment, and if you do not overwrite the package, you will see a message stating that the package already exists, and you will be asked to provide another name or overwrite the package.

  6. Click Next. The Export-Import » Source & Target Compatibility page appears. If any compatibility-related issues are detected, make sure to select the check boxes corresponding to the settings before you proceed.

    IMPORTANT: Before you override the compatibility issues detected for the settings, make sure that the compatibility issue has no impact on the target environment.

  7. Click Next. The Export-Import » View Import Options page appears.

  8. Under From the source, click one of the following options:

    • Import everything (legacy scripts and managed views): Imports the legacy package along with the managed views. This option will replace the legacy package of the target environment. Also, the revision zero of a managed view will be based on the source package. You can use this option if the source package that is being imported includes customizations that are based on legacy scripts.

    • Import only managed views: Imports only the managed views from the source package. This option will not replace the legacy package. Revision zero of a view label is based on the template tables of the target environment.

      NOTE: Use this option if you have already imported the legacy package, if the target contains the same legacy package, or if the imported managed views are not based on customizations found in the legacy package.

  9. Under In the target '<target environment name>', click one of the following options:

    • Delete all target managed views and replace with imported views: Deletes all revisions of the managed views and packages in the target environment, and adds the revisions of the managed views in the source package to the target environment.

    • Keep all managed views and add imported views to them: Imports all the managed views in the source environment into the target environment. When a view is managed in the source environment but not in the target environment, the view will become managed in the target environment. When a view is managed in both the environments, the current revision of the managed view that has been imported is appended to the existing revisions of the managed view in the target environment. After the import is complete, for views managed in both environments, the target environment retains its previous revisions with the current revision being the imported one from the source environment. The remaining managed views in the target environment will not be affected. The packages in the target environment will not be deleted; however, the list of views may change if the views are managed in both the environments.

      NOTE: If you are importing all revisions of each managed view in your package or environment, this option will not be available for selection. Also, all revisions will be imported to the target environment, and the revision of the views that were added to the package will continue to be present in the package in the target environment.

    • Replace managed views with the imported views. Keep all the rest of the target views: Imports all the managed views in the source environment into the target environment. When views are managed in the source environment but not in the target environment, the views will become managed in the target environment. When views are managed in both environments, the managed views in the target environment will be overwritten by the managed views in the source environment. The remaining managed views in the target environment will not be affected. The imported views will be deleted from the packages in the target environment, and the remaining packages will not be affected.

  10. In the Imported views list, see the details of the views imported to the target environment. The list has the following columns:

    • View Label: Lists the names of the views that will be imported to the target environment. You can use the box available under the column label to filter the information based on the view label. If you want to sort the list on the basis of this column, click the column label.

    • Managed in target: Indicates if a view is managed in the target environment. If a view is managed in the target environment, the column will display the value "Yes"; otherwise, the column will display "No". You can use the box available under the column label to filter the information based on the value "Yes" or "No". If you want to sort the list on the basis of this column, click the column label.

    • Compare imported views to target: Enables you to compare the revisions of managed views that are being imported with the revisions of those that are available in the target environment. To compare the view revisions, follow these steps:

      1. In the Imported views list, identify the entry corresponding to the view for which you want to compare the revisions.

      2. In the Compare imported views to target column, click Show. The Compare Customizations dialog box appears.

      3. Compare the view revisions, and click Close.

  11. Click Next. The Import option selections dialog box appears. Verify the settings that you have selected, and click OK. The Export-Import » Finish page appears.

    IMPORTANT: If the NoetixViews Workbench could not generate the script corresponding to the view customizations for a view, an error message will be displayed along with the view name.

  12. Click Done or Home to go to the NoetixViews Workbench home page.

  13. Optionally, verify that the imported package is now available in the target environment through the Manage Packages option. For information, see View Package Information.

  14. IMPORTANT: To apply the customizations to the NoetixViews schema, you must stage the package to the NoetixViews schema installation folder of the target environment and then run Stage 4 or incremental regeneration  For information about staging packages, see Stage a Package in "Manage Packages", and for information about running the incremental regeneration process, see the Noetix Metabuilder Help.

Published:

Import Customizations

The import feature of the NoetixViews Workbench can be used to import managed views, legacy scripts, and other configuration-specific customizations to an environment in the same or another NoetixViews Workbench installation. You can import the managed views of a custom package or all managed views of an environment. Typically, customizations pertaining to the original and latest revisions are imported. You can also import the customizations pertaining to all revisions.

For an environment to be used as a target, at least Stage 4 should have been completed till the Get Passwords wizard is displayed for the underlying NoetixViews schema.

IMPORTANT: The customizations exported from an environment cannot be imported to a target environment if the Noetix Views (NoetixViews) version of the view revisions in the source is higher than the NoetixViews version of the target environment. If you try to import customizations to an environment that is based on an earlier version of NoetixViews, an error message will be displayed.

To import customizations

  1. On the NoetixViews Workbench home page, click Export/Import. The Export-Import » Choose Options page appears.

  2. Click Import customizations, and click Next. The Export-Import » Welcome page appears.

  3. View the information displayed on the page, and click Next. The Export-Import » Package Import Options page appears.

  4. Click Browse to navigate to the location of the .nvwx file that you saved and select the file, and click Upload. A message stating that the package has been uploaded successfully appears. The package details are displayed on the page.

  5. In the New Package name box, type a name for the package that is being imported. If the package already exists in the target environment, select the Overwrite a package with the same name in the target environment, if it exists check box.

    NOTE: If the package already exists in the target environment, and if you do not overwrite the package, you will see a message stating that the package already exists, and you will be asked to provide another name or overwrite the package.

  6. Click Next. The Export-Import » Source & Target Compatibility page appears. If any compatibility-related issues are detected, make sure to select the check boxes corresponding to the settings before you proceed.

    IMPORTANT: Before you override the compatibility issues detected for the settings, make sure that the compatibility issue has no impact on the target environment.

  7. Click Next. The Export-Import » View Import Options page appears.

  8. Under From the source, click one of the following options:

    • Import everything (legacy scripts and managed views): Imports the legacy package along with the managed views. This option will replace the legacy package of the target environment. Also, the revision zero of a managed view will be based on the source package. You can use this option if the source package that is being imported includes customizations that are based on legacy scripts.

    • Import only managed views: Imports only the managed views from the source package. This option will not replace the legacy package. Revision zero of a view label is based on the template tables of the target environment.

      NOTE: Use this option if you have already imported the legacy package, if the target contains the same legacy package, or if the imported managed views are not based on customizations found in the legacy package.

  9. Under In the target '<target environment name>', click one of the following options:

    • Delete all target managed views and replace with imported views: Deletes all revisions of the managed views and packages in the target environment, and adds the revisions of the managed views in the source package to the target environment.

    • Keep all managed views and add imported views to them: Imports all the managed views in the source environment into the target environment. When a view is managed in the source environment but not in the target environment, the view will become managed in the target environment. When a view is managed in both the environments, the current revision of the managed view that has been imported is appended to the existing revisions of the managed view in the target environment. After the import is complete, for views managed in both environments, the target environment retains its previous revisions with the current revision being the imported one from the source environment. The remaining managed views in the target environment will not be affected. The packages in the target environment will not be deleted; however, the list of views may change if the views are managed in both the environments.

      NOTE: If you are importing all revisions of each managed view in your package or environment, this option will not be available for selection. Also, all revisions will be imported to the target environment, and the revision of the views that were added to the package will continue to be present in the package in the target environment.

    • Replace managed views with the imported views. Keep all the rest of the target views: Imports all the managed views in the source environment into the target environment. When views are managed in the source environment but not in the target environment, the views will become managed in the target environment. When views are managed in both environments, the managed views in the target environment will be overwritten by the managed views in the source environment. The remaining managed views in the target environment will not be affected. The imported views will be deleted from the packages in the target environment, and the remaining packages will not be affected.

  10. In the Imported views list, see the details of the views imported to the target environment. The list has the following columns:

    • View Label: Lists the names of the views that will be imported to the target environment. You can use the box available under the column label to filter the information based on the view label. If you want to sort the list on the basis of this column, click the column label.

    • Managed in target: Indicates if a view is managed in the target environment. If a view is managed in the target environment, the column will display the value "Yes"; otherwise, the column will display "No". You can use the box available under the column label to filter the information based on the value "Yes" or "No". If you want to sort the list on the basis of this column, click the column label.

    • Compare imported views to target: Enables you to compare the revisions of managed views that are being imported with the revisions of those that are available in the target environment. To compare the view revisions, follow these steps:

      1. In the Imported views list, identify the entry corresponding to the view for which you want to compare the revisions.

      2. In the Compare imported views to target column, click Show. The Compare Customizations dialog box appears.

      3. Compare the view revisions, and click Close.

  11. Click Next. The Import option selections dialog box appears. Verify the settings that you have selected, and click OK. The Export-Import » Finish page appears.

    IMPORTANT: If the NoetixViews Workbench could not generate the script corresponding to the view customizations for a view, an error message will be displayed along with the view name.

  12. Click Done or Home to go to the NoetixViews Workbench home page.

  13. Optionally, verify that the imported package is now available in the target environment through the Manage Packages option. For information, see View Package Information.

  14. IMPORTANT: To apply the customizations to the NoetixViews schema, you must stage the package to the NoetixViews schema installation folder of the target environment and then run Stage 4 or incremental regeneration  For information about staging packages, see Stage a Package in "Manage Packages", and for information about running the incremental regeneration process, see the Noetix Metabuilder Help.

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