Forum Discussion
WebApp Power BI Service API, get embedded report - how to trouble shoot
Dear community,
Trying to build a mock-up for a .NET webapp as a wrapper for reports running on Premium Embedded capacity.
I have followed Ted Pattisons "starter kit" guide at: https://github.com/PowerBiDevCamp/App-Owns-Data-Starter-Kit
The app "runs", authentication works, service principal user seems to do its job as well, I am able to add tenant manually in the admin SQL and view all members, datasets and reports via the REST API Groups, Members etc., i.e. authentication and rights seems to work well, and I can even "Delete" an entire workspace with a single click on a button 😉
However, for the embed / reporting features I am struggling, and too rookie to find a way of troubleshooting my way to a solution.
Appsettings and error-message shared below, any ideas on how to proceed and what might be causing all the troubles?
Best regards,
Lasse
PS: Running the following packages:
Hi Anonymous ,
Thanks, the link you shared is actually also originally from Ted Pattison's Dev Camp sessions, I have tried those steps as well.
Anyways, it turns out that there has been changes to the API version as well as the auth settings at Azure that were required to set appropriately, which was not covered in the guide, even though it was "only" 6 months old 🙂 Things change fast 😄 I finally managed to get both he API methods working and the Azure settings right, failed to document both so unfortunately I can't share it right now, will get back when I get to the final documentation.
Thanks again!
2 Replies
HI LasseMr,
Perhaps you can take a look at the following document about embedded content with power bi if helps: (it provides the sample application for use embedded, you can reference and copy corresponding steps to your applications)
Embed content in your Power BI embedded analytics application - Power BI | Microsoft Docs
Regards,
Xiaxoin Sheng
Hi Anonymous ,
Thanks, the link you shared is actually also originally from Ted Pattison's Dev Camp sessions, I have tried those steps as well.
Anyways, it turns out that there has been changes to the API version as well as the auth settings at Azure that were required to set appropriately, which was not covered in the guide, even though it was "only" 6 months old 🙂 Things change fast 😄 I finally managed to get both he API methods working and the Azure settings right, failed to document both so unfortunately I can't share it right now, will get back when I get to the final documentation.
Thanks again!
