Step 5: Correcting Preview Import Warnings

Correcting Missing Group Warnings

For the application permission and viewpoint subscription warnings, the messages indicate that the permission and subscription aren't able to be imported because the Approvers - UK group does not exist in the target environment. This is because we created that group in the test environment only.

To correct this, use migration to export the groups from your test environment and import them into your production environment.

  1. In your TEST environment, click Tools, and then Migration.
    migration icon
  2. On the Categories tab, click Groups and Membership.
    groups and membership
  3. Expand Native Directory, select Groups, and then click Export.
    native directory groups
  4. Enter a file name, and click OK.
    groups file name
  5. When the export has completed, click Close.
    migration status report
  6. From Snapshots, locate the group export file, and then in the Actions column click actions and then click Download.
    template download

    The groups snapshot is downloaded to your local machine.

  7. In your PRODUCTION environment, click Tools, and then Migration.
    migration icon
  8. On the Snapshots tab, click Upload.
    upload button
  9. Click Choose File, select the file containing your groups, and then click Upload.
    upload groups file
  10. When the file has completed uploading, click OK.
    upload complete
  11. On the Snapshots tab, locate the file containing your groups and in the Actions column click actions, and then select Import.
    import groups
  12. Click OK on the dialog to confirm the import.
    import group confirmation
  13. When the import has completed, click Close.
    group import complete

Rerun the template preview and verify that the application permission and viewpoint subscription warnings are no longer displayed.

Application permission:


application permission warning cleared

Viewpoint subscription:


subscription warning cleared

Correcting Missing Node Type Warnings

For the warning about the node type, the message indicates that the Cost Center - UK Rollup node type converter isn't able to be imported because the source node type doesn't exist in the target environment. This is because we created the Cost Center Rollup node type in the Corporate Planning application in our test environment but not in our production environment.

To correct this, we need to bring the Corporate Planning application from the test environment (where we added the source node type) to the production environment. We can use templates in two different ways to accomplish this:

  • Export the Corporate Planning application to a separate template file in the test environment and import it first, then import the Corporate Planning - UK application.
  • Export both Corporate Planning and Corporate Planning - UK to the same template file so that both are brought over together. This is the approach that we will take for this scenario.
  1. In the TEST environment, click Tools, and then Templates.
    template icon
  2. On the Export tab:
    1. Expand Applications.
    2. Select the checkbox next to your both the Corporate Planning and Corporate Planning - UK applications.
    3. In Template File, enter a file name.
    4. Click Export.

    export template two applications

    The applications are exported to a .json file and downloaded to your local system.

  3. In the PRODUCTION environment, click Tools, and then Templates.
    template icon
  4. On the Import tab:
    1. Click Choose File.
    2. Navigate to the export file that was downloaded to your local system.
    3. Click Preview.

    template file import
  5. Verify that the node type converter warning is no longer displayed.
    node type warning not displayed