Embedded Report Fails to Load (Works in Service); Token Generated via Script

[Nirvanjay26]

Hi Fabric Community,

​I'm facing a puzzling issue with an embedded report that I'm hoping for some guidance, as the report itself works perfectly when viewed directly in the service.

​The Working Scenario:

1. ​We have a central Warehouse in Microsoft Fabric.
2. ​Semantic Model A was created from this warehouse by another team member.
3. ​A report built from this model, Report A, is currently embedded on our website and works perfectly.

​The Failing Scenario:

1. ​From the exact same Warehouse, I created a new model, Semantic Model B.
2. ​I then built Report B using my new semantic model.
3. ​Crucially, Report B loads and functions perfectly when I view it directly in the Fabric/Power BI service.
4. ​However, after embedding Report B into our website, it fails to load.

​Technical Details & Troubleshooting:

• ​Our embedding links and tokens are generated using a custom TypeScript script.
• ​I have meticulously compared the settings for both Semantic Model A and my Semantic Model B. The settings, including RLS, relationships, and permissions that I can see, appear to be identical.
• ​Since Report B works correctly in the service, the issue seems to be specifically related to our embedding process or the token generation script.

​Error Message:

When the embedded report fails to load, this is the error I receive:

 My Question:

Why would a report work perfectly in the service but fail only when embedded? Since our embed configuration is generated via a TypeScript script, is it possible that a specific permission or dataset ID for my new Semantic Model B needs to be explicitly included or changed in the token generation payload?

Any guidance on what parameters are critical for embedding a report from a newly created semantic model would be a great help.

Thanks in advance!

[v-nmadadi-msft]

Hi @Nirvanjay26 ,

Could you please confirm if the issue has been resolved after raising a support case? If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.

Thank you for your understanding and assistance.

[Nirvanjay26 · Accepted solution]

Hello, @v-nmadadi-msft ,

Just wanted to close the loop on this.

The problem is solved! It was a simple fix in the end – there was an issue with the dataset ID we were using from the client.

Appreciate you checking in and reminding me to share. Hope this helps someone else out!

[v-nmadadi-msft]

Hi @Nirvanjay26 ,
Sorry to know it didn’t help. Please consider reaching out to Microsoft Support. You can provide them with all the troubleshooting steps you've already taken, which will help them understand the issue better and provide a resolution. They might be able to identify something specific about your admin account setup or provide a solution that isn't immediately obvious. 

Below is the link to create Microsoft Support ticket:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

Thank you

[v-nmadadi-msft]

Hi @Nirvanjay26 ,
Thanks for reaching out to the Microsoft fabric community forum.

As you have mentioned the Report is working without any issue in Service, to rule out issues with your application, verify that the Power BI item can be viewed in the Power BI embedded analytics playground

For security purposes, access tokens (a Microsoft Entra token or an embed token) have a limited lifetime. You should constantly monitor your access token and refresh it if needed. For more information, see Refresh the access token.


I hope this information helps. Please do let us know if you have any further queries.
Thank you

[Jessica_17]

Hello @v-nmadadi-msft ,

We have tried playground as well, and over there its working fine, we are facing issue in the website, where client has embedded it.

[suparnababu8]

Hello @Nirvanjay26 

I've few questions...

• You mentioned
  ""Semantic Model A was created from this warehouse by another team member.
  ​A report built from this model, Report A, is currently embedded on our website and works perfectly."" - Which mode here you used to build the report?
• Then you created ""Semantic Model B"" from same warehosue - Here Which mode here you used to build the report?

Please check it and let me know.

Thank you!!

Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

[Jessica_17]

Hi @suparnababu8 ,

I am also working on same project with Nirvanjay, direct query mode is used to build the semantic model on fabric workspace itself for both Model A and Model B and similarly we created report using create new report and also via desktop, but still faced issues after embedding reprots from our model.

[suparnababu8]

Hi @Jessica_17 

Thanks for response. If you are using direct query, It will fail to load the report as embedded report. I wonder how your report A is working on direct query as embedded report in your website. As per this thread Solved: Embedded Report Not Displaying Data (Using two sem... - Microsoft Fabric Community  direct query mode is not supported for embedded.

Can you please look into this.

Thank you once again!

Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

[Jessica_17]

HI @suparnababu8 ,

Then the other report should have also not worked, but its working fine, there seems to be something missing, which we are not able to find it out. And we are facing different issue than the one you sent on link