Forum Discussion

JiriSM's avatar
JiriSM
Frequent Visitor
9 months ago
Solved

PBIR Format Issue – Old Report Version Persists After Publishing

Hello everyone, I’ve encountered a problem when switching a report definition from the legacy format to PBIR. After publishing the updated report to Power BI Service, the old version of the report r...
Need Help
  • Kedar_Pande's avatar
    Kedar_Pande
    9 months ago

    This is a known issue with PBIR migration:

    Old legacy report metadata can persist in Power BI Service after migrating from PBIR-Legacy to PBIR format.

    Reports converted from legacy to PBIR don’t fully replace the prior version on publish.

    Workaround: Save a new copy as PBIR, publish as a new report, then retire the old one.

    No rollback from PBIR to legacy; keep backups before migration.

    Microsoft plans improvements, but currently this behavior is expected for migrated reports.

     

    If this answer helped, please click Kudos or Accept as Solution.
    -Kedar
    LinkedIn: https://www.linkedin.com/in/kedar-pande

Kedar_Pande's avatar
Kedar_Pande
Icon for Super User rankSuper User
9 months ago

This is a known issue with PBIR migration:

Old legacy report metadata can persist in Power BI Service after migrating from PBIR-Legacy to PBIR format.

Reports converted from legacy to PBIR don’t fully replace the prior version on publish.

Workaround: Save a new copy as PBIR, publish as a new report, then retire the old one.

No rollback from PBIR to legacy; keep backups before migration.

Microsoft plans improvements, but currently this behavior is expected for migrated reports.

 

If this answer helped, please click Kudos or Accept as Solution.
-Kedar
LinkedIn: https://www.linkedin.com/in/kedar-pande

JiriSM's avatar
JiriSM
Frequent Visitor
9 months ago

Thank you very much for your response! This is new information for me. I haven’t found anything similar in the official documentation or in blog posts. I understand that migrating from PBIR back to the legacy format is not possible. However, to be honest, this is a significant issue with the PBIR format. The suggested workaround is not feasible in large environments because each report copy generates a new GUID in the service. 😟

  • v-achippa's avatar
    v-achippa
    Icon for Community Support rankCommunity Support
    8 months ago

    Hi JiriSM,

     

    Thank you for reaching out to Microsoft Fabric Community.

     

    Thank you Kedar_Pande for the prompt response. 

     

    Thank you for the response. Yes this behaviour after migrating from legacy format to PBIR is a known limitation on the service side.

    Since this impacts existing report GUIDs and you are working in a large environment where creating new report copies is not feasible, so I recommend you to please raise a support ticket.
    To raise a support ticket, kindly follow the steps outlined in the following guide:

    Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn

     

    Thanks and regards,

    Anjan Kumar Chippa

    • v-achippa's avatar
      v-achippa
      Icon for Community Support rankCommunity Support
      8 months ago

      Hi JiriSM,

       

      As we haven’t heard back from you, we wanted to kindly follow up to check that have you raised the support ticket? Is your issue resolved?

       

      Thanks and regards,

      Anjan Kumar Chippa