Forum Discussion

Simonawu's avatar
Simonawu
Frequent Visitor
1 month ago

Report Landing Page Setting Stops Working After Publishing to Report Server

Hi everyone,

I have a question about configuring a landing page for a report.

In Power BI Desktop, I set up a specific page as the landing page for my report by right-clicking on the page tab and selecting "Set as landing page". This worked as expected during local testing in Desktop. When I opened the report, it would always start on the page I designated.

However, after publishing this report to our on-premises Power BI Report Server, the landing page setting seems to be ignored:

When opening the report, it always displays the page that was active when the report was last saved, instead of the designated landing page.

When viewed through the web portal on the Report Server, the landing page property I configured in Desktop appears to be completely ignored.

Additional Context:

This issue started occurring after I recently upgraded our Report Server from the September 2025 version to the May 2026 version (version 15.0.1121.120) . The landing page functionality was working correctly on the previous version.

Questions for the community:

Is this a known issue (bug) with the May 2026 release?

Are there any special considerations or steps for configuring a landing page in a Report Server environment that differ from Desktop?

Are there any workarounds or temporary solutions available?

Thanks in advance for your help and suggestions!

Power BI Report Server

3 Replies

  • v-achippa's avatar
    v-achippa
    Icon for Community Support rankCommunity Support
    1 month ago

    Hi Simonawu,

     

    Thank you for reaching out to Microsoft Fabric Community.

     

    Since the landing page works correctly in the desktop and the issue started only after upgrading to the May 2026 report server version, this looks like a report server issue rather than a report configuration issue.

    • As a temporary workaround, the report opens on whatever page was active when it was last saved. Before saving and publishing, select your intended landing page so it is the active page, then save and republish the report.

    If the issue persists across multiple reports, I recommend opening a Microsoft Support ticket so the product team can investigate whether this is a known issue with the May 2026 report server release.

    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
    1 month ago

    Hi Simonawu​,

    As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked?  or have you raised a support ticket?

    Thanks and regards,
    Anjan Kumar Chippa

  • johncpratt's avatar
    johncpratt
    Icon for Advocate III rankAdvocate III
    14 days ago

    Simonawu​ I have been using PBIRS since 2017 and have always had to re-select the desired default/landing page in the report and reset all filters to the desired default before publishing.  This is an enormous headache, and I can't count the times I've worked on a very specific issue, fixed it, and then deployed the report with some slicer value selected and/or a different page than the desired default selected. 

    What v-achippa​ suggested is required, plus resetting filters.  It may just be a fluke of timing where the first time you encountered this issue was after the May 2026 update.

    There should be a PBIRS feature for developers to specify the default page and default filters for the report so that after every deployment those are automatically applied.  That would be a massive productivity boost and headache reliever.