Forum Discussion

kadirkkkk2's avatar
kadirkkkk2
Frequent Visitor
8 months ago
Solved

template app - unable to load report error

I use template apps to install my designs to my or other tenants.

In some of my reports although i get no error on my template app workspace installed app report gives error when i click on app or the report in workspace

 

Steps i follow;

- create a template app workspace (PRO)

- publish the report

- create app

- promote app

- get link

- paste link on browser and install app

- select app to open gives ERROR

- select report in workspace gives ERROR

 

This looks like a bug but i dont have support plan so i can not create a ticket. Can you please help me?

 

Unable to load report

Please try again later or contact support. If you contact support, please provide these details

Activity ID: 65ebdabf-471f-4edc-b5de-76536d3b3a55
Request ID: 2f566813-4089-a404-0f30-c995cbdd348b
Correlation ID: bab67ed6-e664-ea58-94ef-f2c809e2d7ee
Time: Tue Dec 16 2025 20:59:13 GMT+0300 (GMT+03:00)
Service version: 13.0.27228.39
Client version: 2512.1.27028-train
Cluster URI: https://wabi-west-europe-f-primary-redirect.analysis.windows.net/

  • Hi kadirkkkk2 ,

    Thanks for reaching out to the Microsoft fabric community forum.

    Thanks for sharing what you tried and the results you observed. Even though it’s frustrating, this kind of feedback is really valuable because it confirms that the issue isn’t caused by a specific visual or model object, but likely by hidden or corrupted metadata in the report.

    Your approach of creating a new blank report and copying the content over is a practical workaround and will definitely help others who run into the same “Unable to load report” issue with template apps. Hopefully this saves some time for anyone facing a similar situation.

    Best Regards, 
    Community Support Team 

5 Replies

  • kadirkkkk2 

    This is a known Power BI template app issue. Publish and promotion succeed, but the report fails to load after app installation due to unsupported or broken objects. This is not caused by your steps.

    Common causes:

    • Tenant-specific or unsupported data sources (DirectQuery, personal gateways)

    • Azure Maps or non-certified custom visuals

    • Hidden broken references (tooltips, hidden pages, deleted fields still used)

    • Field parameters or report-level measures with external models

    • RLS roles without default user mapping

    What to do:

    1. Test with a minimal report

    • Copy the report

    • Keep only one simple table visual

    • Publish and install the template app

    • Add visuals back one by one to find the failing object

    1. Remove Azure Maps and custom visuals

    • Replace with standard visuals and retest

    1. Re-publish clean

    • Delete the dataset from workspace

    • Re-publish the report

    • Recreate and promote the app again

    1. Test without RLS

    • Temporarily remove RLS

    • Install app and test

    • Re-add RLS later

    Important:

    • Activity ID confirms a service-side failure

    • Without Microsoft support, backend cleanup is not possible

    • Template apps are fragile for complex reports

    Workaround:

    • Keep template apps simple

    • Avoid Azure Maps and advanced features

    • Use normal apps for complex reports

    • kadirkkkk2's avatar
      kadirkkkk2
      Frequent Visitor

      It's so dramatic that,

      I deleted all the pages

      Deleted all the tables and all the measures

      Opened power query and deleted what i see

       

      But error still appears

       

      So now i'm going to create a blank report and copy all the contents from old to blank

      Thanks anyway

      • v-menakakota's avatar
        v-menakakota
        Community Support

        Hi kadirkkkk2 ,

        Thanks for reaching out to the Microsoft fabric community forum.

        Thanks for sharing what you tried and the results you observed. Even though it’s frustrating, this kind of feedback is really valuable because it confirms that the issue isn’t caused by a specific visual or model object, but likely by hidden or corrupted metadata in the report.

        Your approach of creating a new blank report and copying the content over is a practical workaround and will definitely help others who run into the same “Unable to load report” issue with template apps. Hopefully this saves some time for anyone facing a similar situation.

        Best Regards, 
        Community Support Team