Compatibility Mode issues with Migration Tool
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2025 07:48 AM - edited 08-18-2025 07:53 AM
We're on Yokohama Patch 5, using version 2.0.7 of the PAR CoreUI Migration Scripts and version 2.0.6 of the sn-app-par-coreui-migration-center and sn-app-par-coreui-migration-legacy-widget plugins.
After running the migration tool on all of our dashboards and reports, we're seeing only {} on data visualizations that were migrated in compatibility mode. They are not presented in the iframe as described in the documentation.
Has anyone else experienced a similar issue and if yes, were you able to get around it?
Susan Williams, Lexmark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
For what it's worth, SN Support gave us this fix. We wrote a script to fix these in bulk.
"Following a thorough investigation, we have identified that the issue you're experiencing in some of the widgets that only show {} is related to PRB1901943. A workaround is available, and we would be happy to guide you through the steps:
1- Edit the dashboard.
2- Click on ""Open record"" in the widget context menu, located in the top right menu next to the edit button.
3 -Within the ""json"" field of the PAR Dashboard widget record, locate the ""headerTitle"" property and replace it with ""widgetTitle"".
4- Save the changes and then reload the Dashboard.
Susan Williams, Lexmark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago - last edited 2 weeks ago
Hi Susan,
Thank you for sharing this.
From what I understand, ServiceNow plans to deprecate compatibility mode in the Zurich/Australia release, which means all dashboards currently running in compatibility mode will become read-only at that point.
Are you planning to recreate these dashboards before the deprecation?
Also, have you received any guidance or recommendations from ServiceNow regarding this?