Forum Discussion

amahmoud's avatar
amahmoud
New Member
6 months ago
Solved

Incremental refresh

Hi

I have created a new Power BI report based on an existing report; I have added a new tab and the new report has been configured to use incremental refresh.. Also both reports are currently published in our team workspace on PowerBI.com with different names to make sure it is working as expacted and tested. I am ready to replace the old report with the new one however I don't want any intruption to the link and users. 

I would like to remove the old report and replace it with the new version. At the moment, both reports exist in the same workspace. My intention is to replace the current production report, with the new incremental refresh version.

I have the updated report open in Power BI Desktop, saved and renamed as same name as old one, and attempted to publish it. However, instead of replacing the existing report, Power BI creates an additional copy of CEOOS rather than overwriting the current production report.

Please let me know the correct approach to replace the existing report, or if there are any additional steps or and i do have admin rights to workspace.
Need Help
  • cengizhanarslan's avatar
    cengizhanarslan
    6 months ago

    A report is replaced only when you publish over the same report object in the workspace. If you publish to the same workspace but Power BI can’t match it to an existing report, it will always create a new one. So instead of re-publishing your report try rebinding your report tho your new semantic model using the code below with NoteBook:

    %pip install semantic-link-labs
    import sempy_labs.report as rep

# List of reports to rebind
reports = [
    'ReportName'
]

# Rebind operation for each report
for report in reports:
    rep.report_rebind(
        report = report,
        dataset = 'NewSemanticModelName',
        report_workspace = 'WorkspaceName',
        dataset_workspace = 'WorkspaceName'
    )
    print(f"✓ {report} successfully rebound")

6 Replies

  • v-kpoloju-msft's avatar
    v-kpoloju-msft
    Community Support
    6 months ago

    Hi amahmoud, 

    Thank you for reaching out to the Microsoft Fabric Community Forum. Also, thanks to krishnakanth240, cengizhanarslan, Natarajan_M,  for those inputs on this thread.

    Has your issue been resolved? If the response provided by the community member krishnakanth240, cengizhanarslan, Natarajan_M, addressed your query, could you please confirm? It helps us ensure that the solutions provided are effective and beneficial for everyone.

    Hope this helps clarify things and let me know what you find after giving these steps a try happy to help you investigate this further.

    Thank you for using the Microsoft Community Forum.

    • v-kpoloju-msft's avatar
      v-kpoloju-msft
      Community Support
      6 months ago

      Hi amahmoud,

      Just wanted to follow up. If the shared guidance worked for you, that’s wonderful hopefully it also helps others looking for similar answers. If there’s anything else you'd like to explore or clarify, don’t hesitate to reach out.

      Thank you.

  • amahmoud's avatar
    amahmoud
    New Member
    6 months ago

    Sorry my report name is CEOOS just in case that word created some confusion

  • Natarajan_M's avatar
    Natarajan_M
    Super User
    6 months ago

    Hi amahmoud ,
    PBI at the backend will create GUID for each object that isgetting published so if a file is already published it will recognize that the file is already present so it gives us a promt whether it need to overwrite the existing file .
    I have few questions on the problem statement . 
    The new testing report you published to the workspace for validation purposes has been removed from the workspace ?

    any other change like space in the file name or 

    With the recent changes to the PBIX file, instead of publishing the file from the desktop app, try using the ALM Toolkit and try to migrate the changes from the desktop to the service.

    Thanks .

    If this response was helpful in any way, I’d gladly accept a kudo.
    Please mark it as the correct solution. It helps other community members find their way faster.


     

  • cengizhanarslan's avatar
    cengizhanarslan
    Super User
    6 months ago

    A report is replaced only when you publish over the same report object in the workspace. If you publish to the same workspace but Power BI can’t match it to an existing report, it will always create a new one. So instead of re-publishing your report try rebinding your report tho your new semantic model using the code below with NoteBook:

    %pip install semantic-link-labs
    import sempy_labs.report as rep

# List of reports to rebind
reports = [
    'ReportName'
]

# Rebind operation for each report
for report in reports:
    rep.report_rebind(
        report = report,
        dataset = 'NewSemanticModelName',
        report_workspace = 'WorkspaceName',
        dataset_workspace = 'WorkspaceName'
    )
    print(f"✓ {report} successfully rebound")
  • krishnakanth240's avatar
    krishnakanth240
    Super User
    6 months ago

    Hi amahmoud 

     

    From Power BI Service, can you try deleting the dataset only (not the report), and publish the PBIX file with same name. This might works if the report depends on the dataset and relationships remain compatible. If not getting possible, try using Deployment Pipelines from Dev to Test and Test to Production.