Skip to main content

Migrate Platform Reports to Angles Hub

Introduction

The Platform Report Migration feature in Angles Hub provides a streamlined interface for importing, monitoring, and managing the migration of reports from your legacy platform to the Angles Hub system.

Prerequisites

Before migrating Platform reports in the Angles Hub, ensure that the following prerequisites are met:

  • Administrator access to the Angles Hub

  • A proper .noetix or .json file extracted using the Report Migration Utility (RMU), containing complete and accurate report metadata.

  • An Oracle target connection in Angles Hub, which serves as the destination for importing the reports.

  • View metadata already extracted in the target connection, required to support the import and mapping of the extracted reports.

Migrate Platform Reports to Angles Hub

To migrate platform reports to Angles Hub, sign in to the Angles Hub and perform the following steps:

  1. Click Metadata > Platform Report Migration. The Noetix Platform Report Migration page is displayed.

  2. In Migration Process > Select Target Connection, select the required connection to which you want to import the migration file.

  3. To import the file, drag and drop, or click to upload the appropriate .noetix or .json file. In the Select Reports to Migrate section, select the reports you want to import into Angles Hub (one, multiple, or all), and click Import.

    It is recommended to use a smaller batch of reports so that errors can be easily tracked.

Monitor Migration Progress

During the migration process, you can monitor the real-time progress and access detailed information about the import operation.

Migration Logs

In the Migration Logs section, you can view real-time logs that display:

  • Individual report processing status

  • Timestamp for each migration event

  • Detailed error messages for failed imports

  • Warning notifications for potential issues

The logs update dynamically as the migration progresses, providing continuous visibility into the import operation.

While the migration is in progress, the Stop button (located beside the Import button) becomes enabled, and clicking it will immediately terminate the migration process.

Important: Terminating the migration will result in the loss of all processed report data up to that point, and the migration will stop completely.

Migration Results

The Migration Results section provides both a high-level overview and detailed status information for each report, enabling you to quickly assess the success of the migration and identify any issues that require attention

  • Migration Summary

    The Migration Summary provides an overview of the entire migration process, including:

    • Total Reports: The total number of reports included in the migration file

    • Migrated: The number of reports imported successfully into the Angles Hub

    • Failed: The number of reports that could not be imported

    • Warnings: Any non-critical issues or alerts generated during the migration process

  • Migration Results:

    The Migration Results section displays the report name, migration status (success, failed, or warnings), and error details for reports that encountered issues.

Download Migration Logs

To download the migration logs for offline review or record-keeping, select the Download Migration Logs button.

The logs download in a text format containing the complete migration history, including all events, errors, and warnings from the current import session.

View Migration History

The Migration History feature provides a comprehensive record of all past migration operations performed in the Angles Hub.

To access migration history, perform the following:

  1. Select the Migration History button located in the Platform Report Migration tab. The Migration History page is displayed.

  2. The Migration History table displays the following information for each migration operation:

    • Connection: The target connection used for the migration

    • Start Time: Timestamp indicating when the migration process began

    • End Time: Timestamp indicating when the migration process completed

    • Status Summary: Displays the following metrics:

      • Total: Total number of reports in the migration

      • Success: Number of reports migrated successfully

      • Failed: Number of reports that failed to migrate

  3. In the Actions column, you can access additional details and logs for each migration:

    • Details: Select this option to view the complete migration summary, including:

      • Breakdown of successful and failed reports

      • List of warnings and error messages

      • Individual report status information

    • Download Logs: Select this option to download the complete log file for the specific migration session

    • View Logs: Select this option to open and review the migration logs directly in the browser without downloading

The Migration History page allows you to track all migration activities over time, compare results across different import sessions, and access historical logs for troubleshooting or audit purposes.

Best Practices

  • Platform Report Migration accepts .noetix or .json files that are extracted exclusively using the Report Migration Utility (RMU). Metadata files generated from external or unsupported sources are not accepted, as report processing is performed only for reports constructed using the MxPlatReport object.

  • The Import button is enabled only after:

    1. A valid target connection is selected.

    2. A supported .noetix or .json file is successfully uploaded.

  • Once the migration process has started, do not refresh the page or navigate away from the Platform Report Migration screen. Refreshing or leaving the page during migration will result in session loss, causing the migration process to terminate immediately.

Migration Failure Scenarios and Resolutions

Scenario 1

Missing Columns in Views

Problem:

A report fails to migrate if one or more required columns are not available in the associated view.

Error Message:

Column 'COLUMN_NAME' not found in view 'VIEW_NAME'

Resolution:

  1. Identify the missing column(s) from the error log.

  2. Navigate to the view in Angles Hub.

  3. Manually add the missing column(s) to the view definition.

  4. Deploy the updated view to the target connection.

  5. Re-import the failed report.

Scenario 2

Missing Views in Target Connection

Problem:

A report fails if the required view does not exist in the selected target connection.

Error Message:

View 'VIEW_NAME' does not exist in target connection

Resolution:

  1. Identify the missing view from the error log.

  2. Create the required view in the target connection.

  3. Extract and deploy the view metadata.

  4. Re-import the failed report to complete the migration successfully.

Scenario 3

Unsupported Filter Operators

Problem:

Some filter operators used in Noetix Platform are not supported in Angles Hub.

Unsupported Operators:

  • exists

  • does not exist

  • yesterday

  • today

Behavior:

These unsupported filters are automatically skipped during migration, and a warning log is generated for each occurrence.

Warning Message:

Filter with operator 'OPERATOR_NAME' is not supported and has been skipped.

Resolution:

  1. Review the warning logs to identify skipped filters.

  2. After successful migration, open the imported report in Hub.

  3. Manually re-add the filters using supported operators available in Angles Hub:

    • Replace exists with IS NOT NULL

    • Replace does not exist with IS NULL

    • Replace yesterday with specific date range filters

    • Replace today with current date filters

  4. Save and test the report with updated filters.

Scenario 4

Duplicate Report Names

Problem: Angles Hub does not support multiple reports with the same name within a connection. If the extracted file contains duplicate report names, duplicate reports are skipped during migration.

Warning Message:

Report 'REPORT_NAME' already exists and has been skipped

Resolution:

  1. Identify duplicate report names from the warning logs.

  2. Choose one of the following options:

    1. Option A: Rename the duplicate reports at the Noetix Platform level and re-extract using RMU

    2. Option B: Edit the extracted .json file directly to rename duplicate reports

    3. Option C: Import reports in separate batches, renaming conflicts manually in Hub between batches

  3. Re-run the migration with uniquely named reports.

Filter Expressions

The following filter expression patterns are supported in Platform Report Migration:

  • Case-insensitive value comparison

    UPPER(Line_Status) <> 'ENTERED'

  • Compound conditional expressions using OR

    (UPPER(Account_Type) = 'LIABILITY' OR UPPER(Account_Type) = 'ASSET')

  • Null and Not-Null checks

    Line_Type_Code IS NOT NULL
    Line_Type_Code IS NULL

  • Flag-based exclusion conditions

    UPPER(POLIN_Cancel_Flag) <> 'Y'

  • Pattern matching using LIKE with multiple conditions

    (UPPER(TRANSACTION_TYPE) LIKE 'ADDITION%'
    OR UPPER(TRANSACTION_TYPE) LIKE '%RETIREMENT%')

Snapshot Reports

When you migrate or import reports from Noetix Platform to Angles Hub, the system detects which reports have subscriptions and automatically converts them to snapshot reports. Each individual subscription is transformed into a separate non-global personalization in Angles Hub. This ensures seamless transition while maintaining data security and user workflows.

After importing snapshot reports, users must manually trigger Refresh Snapshot in Angles Hub. This creates a snapshot table in the database and populates it with the latest data. The system then automatically creates database views for each personalization, applying the original subscription filters.

Users access their personalized reports through the Angles Hub Excel Add-in by selecting Report Personalization. The appropriate filters are applied automatically based on their assigned personalization. After initial setup, the process is fully automated with no further manual intervention required.

Reports without subscriptions migrate as regular reports and function automatically after import.

Was this article helpful?

We're sorry to hear that.