Issues After Migrating Reports to DV– Flags, Missing Visualizations, Last Run Capture, and Domain Se

[SwapnasreeK]

Issues After Migrating Reports to Data Visualization – Flags, Missing Visualizations, Last Run Capture, and Domain Separation Concerns

Hi Community,

We recently migrated a large number of traditional reports to Data Visualization using the Migration Center, and I am noticing several issues that I need clarity on:

1. Migration Logs Showing Flags / Warnings:

After migration, several reports show flags in the Migration Logs.

Some of these reports display messages like:

Not fully migrated

Certain fields are not supported

Unsupported sort fields / dot-walk fields/reference fields

But in some cases, even though the log shows a warning, the visualization seems to render fine.

Is there any documentation or guidance on how to interpret these flags?

Do some warnings mean critical issues, while others are only informational?

2. Migrated Reports Not Appearing in Data Visualization:

Some reports that show “migrated successfully” in the logs are not visible under Data Visualization → Visualizations.

What are the typical reasons why a migrated report does not appear in DV?

Are there known limitations (sort fields, grouping, data source issues, unsupported types, etc.) that block the creation of the DV visualization?

3. Where Is “Last Run” Captured for Data Visualization?

In classic Reports, we could track the last execution using the report_stats table.

However, after migration:

When I opened several DV visualizations, the Updated field in par_visualization did not change

I cannot find any “Last Run” / “Last Viewed” equivalent field in DV.

Does Data Visualization track the last run / last viewed anywhere?

Or is it correct that DV does not store run statistics like the classic reporting engine?

4. Domain Separation Impact:

Our organization continuously undergoes a domain structure.

We have:

Legacy reports created under Domain A

After the upgrade, new reports fall under Domain B

Both domain reports need to exist and be visible in DV

How should Data Visualization be handled in domain-separated environments?

Is there a recommended approach to ensure migrated visualizations respect domain visibility and sharing?

5. Any Best Practices for Fixing Post-Migration Issues?

Before I log individual defects, I want to confirm:

Are there recommended remediation steps for DV migration issues?

Should incompatible reports be redesigned manually in DV Builder?

Is re-migration possible after fixing unsupported fields?

Any known limitations around domain separation + DV migration?

Any guidance, documentation links, or best practices from the community would be greatly appreciated. We want to ensure all legacy and new reports are fully available and functioning in Data Visualization.

I am attaching the screenshot of the logs and issues.

Looking forward to the Reply.

Thank you