Platform Analytics - Migration Tool - Issues

[Pete35]

Is anyone else having issues using the Platform Analytics Migration tool after upgrading to Washington?

Some of the issue that I have found;

- Existing breakdown source field is not being followed. The way these breakdown sources are being migrated the new filters are not showing the same elements as the pre-migration breakdowns. Some of fields are no longer able to be chosen in the filter configuration so these breakdowns are being ignored all together. 

- Column visualisations that have been migrated from an existing PA Widget. The indicator list order is not being kept and the order needs to be reset. Straight migrations are not picking this up very well and all orders need to be adjusted after migration.

- Single score format values are not being migrating with the same specs as those that are contained within the indicator. These need adjustment.

Some other general issues that I have found and more a nuisance more than anything else;

- It seems you cannot migrate an existing report directly to the new Platform Analytics Data Visualisation list. These reports do not seem to be saved directly to the Data Visualisation list and need to be recreated to be consumed within Platform Analytics. This mainly affects reports not listed in a dashboard.

- In general, the change of names from 'Report' to 'Data Visualisation' is confusing for the users. It's long been called a 'Report'. To search for something else is confusing.

- Cascading Filters were previously neatly packaged and now these are separated. I know they can be linked however these were previously neatly packaged and easily consumed and navigated.

- Personally losing the Existing Breakdown source drop list from the top of a PA Dashboard is a backward step. Consumers of the dashboard lose the ability to select a Category (breakdown source) from a list and then select the element. Now all the categories are spread across the page separately and look overwhelming. 

I've attached a direct comparison of an existing PA Dashboard vs a Migrated Platform Analytics Dashboard

[martapenzo]

Hi @Pete35 ,
Please create a support case and we will look into this issue with our development team.
Thank you

[Pete35]

For anyone playing along at home.... 

- sys_ids appearing as a prefix for the migrated tabs. This has been identified as a bug and is being resolved under a Problem. PRB1824755. Apparently, this is resolved in the migration tool version 2.0.4. however, this is only compatible with Yokohama. I have not tested this as we are on Xanadu. Until Yokohama, ServiceNow support have suggested renaming these tabs individually and as required. 

- sys_ids appear in breakdown lists rather than display names. For this one it was found that 'if' the sys_id  is explicitly selected in the field value of the breakdown source then in fact the sys_id would be displayed in the breakdown. In this case changing the breakdown source field to just have field column has resolved the issue. I have tested changing the field value and it does resolve this issue. 

The following was provided to me by ServiceNow Support;

"The filter configurations, filter condition checks were different in Performance Analytics compared to current design of Platform Analytics related to breakdowns. In "Performance Analytics" configuration, there was no filter checks performed on "Field" column of the breakdown source. Instead the check was being performed on the display name of the Facts table selected on the breakdown source.
However, as per Platform Analytics system design, it checks on "field" column of the facts table in breakdown source and filters/displays data based on the same."

[Mark Manders]

I guess this was one of the many reasons that they have cancelled the mandatory migration. You can migrate on your own schedule now. Preferably when all these bugs are out of the migration center.