Issue: Scheduled Reports Not Migrated Correctly During Migration to Platform Analytics

saichary · 3 hours ago

Background

We recently migrated all Core UI reports to Platform Analytics reports using the Migration Center . The bulk migration was mostly successful—Core UI reports were smoothly converted into visualizations without major issues.

However, we encountered a critical problem with Scheduled Reports.

In Platform Analytics, scheduled reports are now called Scheduled Exports.
After migration, while reports were converted correctly, the visualizations were not tagged to the scheduled exports.
As a result, scheduled exports did not perform as expected.
This issue first appeared in DEV and was reproducible in lower instances.

Investigation

Findings

Not all scheduled reports were migrated properly.
- Visualisations are not tagged at all.
- They were not present in sysauto_par (which stores scheduled export jobs).
Migration Property Setting
- At the time of migration, the property com.glide.par.unified_analytics.enabled was set to True.
- Because of this, some scheduled reports were not activated correctly.
Expected Behavior
- If migration is performed with the property set to false, this issue should not occur again.

Probable Cause

The issue was caused due to incorrect migration while the property was still active (com.glide.par.unified_analytics.enabled = true).

Some reports migrated but were not activated.
A few reports did not migrate at all.

Resolution

To resolve this issue and correctly activate scheduled exports:

1. Run Fix Script (Background Script)

Execute fix_bridge_records.txt as a background script.
This script ensures all bridge tables for migrated components are reset to the correct state before activation.

// This script reverts bridge tables to sync their state back to migrated, before activation,
// if the Next Experience component is not actually activated
function revertBridgeRecords(bridgeTable, referenceField, targetTable) {
    var bridgeGR = new GlideRecord(bridgeTable);
    bridgeGR.addQuery('active', 'next'); // Check all bridge records that have active experience Next Experience
    bridgeGR.query();

    while (bridgeGR.next()) {
        var refSysId = bridgeGR.getValue(referenceField); 
        if (refSysId) {
            var targetGR = new GlideRecord(targetTable);
            if (targetGR.get(refSysId)) {   
                if (!targetGR.active) {  
                    bridgeGR.active = ""; 
                    bridgeGR.update();
                }
            } else {
                gs.warn('Missing reference in ' + bridgeTable + ': ' + bridgeGR.getValue('sys_id'));
            }
        } else {
            gs.warn('Reference field ' + referenceField + ' is empty in ' + bridgeTable + ': ' + bridgeGR.getValue("sys_id"));
        }
    }
}

// Process component bridge table
revertBridgeRecords('par_coreui_migration_bridge_component', 'component', 'par_component');
gs.info("Finished updating component bridge table");

// Process dashboard bridge table
revertBridgeRecords('par_coreui_migration_bridge_dashboard', 'par_dashboard', 'par_dashboard');
gs.info("Finished updating dashboard table");

2. Update System Property

Set the property to false in sys_properties:

com.glide.par.unified_analytics.enabled = false

This reverts the migration state back to the correct pre-activation state.

3. Re-Activate via Migration Center

Navigate to Migration Center.
You should now see the Activate button.
Click Activate to complete the correct flow of activation.

Key Takeaways

Scheduled reports become Scheduled Exports in Platform Analytics.
If migration is done while com.glide.par.unified_analytics.enabled = true, some reports may not migrate or activate properly.
Always set the property to false before migration to avoid such issues.
If reports are missing or not linked to exports, run the fix script and re-activate via Migration Center.

Closing Note

This issue should not recur if migrations are performed with the property disabled. For any missing scheduled exports, you can manually recreate them in Next Experience if needed.

👉 If this article helped you resolve your problem, please mark it as helpful and share your feedback in the comments so others in the community can benefit.

Thanks & Regards,
Sai