Forum Discussion

sasdfasdfsad's avatar
sasdfasdfsad
Icon for Advocate IV rankAdvocate IV
3 months ago
Solved

How does PowerBI assign a ReportID when published and can the ID be changed?

I have a report "Quarterly Sales".  

I published it, it has an ID, the report is deployed and there are multiple places in our org that have links to the report.

 

I went to update the report with newly requested features and when I went to deploy, it was given a NEW ID.  Even though the name was the same.  Now there are two "Quarterly Sales" reports in the workspace.

 

Is there anyway to resolve this?  To re-deploy the updated report and ensure it overwrites the "original" report?


  • Hi sasdfasdfsad ,
    Thank you for the additional information.

    The key detail is that the report was repointed to a different semantic model before it was republished. Since there are now two reports with the same name in the workspace, Power BI appears to have created a new report artifact instead of updating the existing one, which would explain the different ReportIDs.

    To better understand why this occurred, could you confirm:

    • Was the report originally connected to one semantic model and then republished after being switched to a different semantic model?

    • Do both reports appear to be connected to different semantic models in the workspace?

    • During publishing, were you prompted to replace the existing report?

    These details will help determine whether the semantic model change influenced the publish behavior or whether Power BI treated the report as a new artifact for another reason.

    Best Regards,
    Abdul Rafi

9 Replies

  • The report ID is assigned by the service when a PBIX is first published, and Publish only overwrites an existing report when the PBIX filename matches the report name in the target workspace and you confirm the Replace prompt. A new report (and a new ID) is created when the filename differs from the existing report name, when the PBIX is uploaded via the web UI instead of Publish from Power BI Desktop, or when the Replace prompt is skipped.

    To recover, delete the new duplicate so the workspace only has the original. Rename your local PBIX so its filename matches the original report name exactly, open it in Power BI Desktop, and click Publish to that workspace. You should see the "A report named ... already exists. Do you want to replace it?" prompt, confirm yes, and the original report ID is preserved, so the links your org already shared keep working.

    If you no longer have the matching PBIX, download the original from the workspace via File then Download this report as .pbix, edit from that copy, and republish.

     

    If that was helpful, please give a thumbs up and mark it as resolved.

     

    Thank you,
    Shai Karmani

     

    Let's connect in LinkedIn

  • Hi sasdfasdfsad 

     

    I have seen this happen in the past sometimes where in an underlying data source has changed which then? Causes Power BI to think it is a completely new report with the semantic model and that is why the ID changes. If that is your case you would need to then go into the PBIP format and change it back. In your existing report.

    • sasdfasdfsad's avatar
      sasdfasdfsad
      Icon for Advocate IV rankAdvocate IV

      When you say change it back, do you mean the reportID for the datasource the report is referencing?

      • v-moharafi-msft's avatar
        v-moharafi-msft
        Icon for Community Support rankCommunity Support

        Hi sasdfasdfsad ,

        Thank you for reaching out to Microsoft Fabric Community and thanks to GilbertQ, Lodha_Jaydeep  and Shai_Karmani for sharing meaningful insights

        No, the ReportID cannot be manually changed. Report IDs are generated and managed by the Power BI Service when a report artifact is created.

        Based on the behavior you described, Power BI appears to have created a new report artifact during the publish operation, which resulted in a different ReportID being assigned. Existing links will continue to point to the original report because they reference the original ReportID.

        This can occur if the report was published as a new artifact rather than updating the existing one. Common causes include publishing to a different workspace, publishing a report that Power BI identifies as a new report, recreating the report after deletion, or other scenarios that result in a new report artifact being created.

        Could you confirm:

        • Whether the original report is still present in the workspace?
        • Whether the report was published to the same workspace as before?
        • Whether you now see two separate reports in the workspace or only the newly published one?

        This information will help determine why a new ReportID was generated and identify the best way to preserve existing report links.

        Best Regards,
        Abdul Rafi

         

  • Hi sasdfasdfsad,

     

    Normally, this is not possible that the new ReportID in the URL when publish the same report with the same name and in the same workspace. Unless you deployed it using (Publish without Replace, Save As + new publish, different workspace, or pipeline/deploy as new)

    Can you confrom in the 2nd deployment of the same report it asked you to replace and you have replace it on the power bi Desktop.

     

    As of now you can do,

    Delete the new version from the power bi service but make sure to have copy in your machine (Delete both model and report if both new created)

    Publish in a way PowerBI desktop => Home => Publish and hit replace when it asked. Chnage your Datasource settings if needed.

     

    I hope this will definetly help, please consider as an accepted solution or give some kudos.

    Thanks

  • Hi  sasdfasdfsad  ,


    Thank you for reaching out to Microsoft Fabric Community.


    Just wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. 

     

     Best Regards,

    Abdul Rafi.

  • Hi sasdfasdfsad ,

    Could you please confirm if the issue has been resolved? If not, feel free to reach out if you have any further questions.

    Your update would be helpful for other members who may face a similar issue.

    Best Regards,
    Abdul Rafi