Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
Hello,
as a company we use power bi embedded for customers. (so those customers do not have a power bi license but we use a token)
in the report we use live connection to SSAS model.
frequently, working visuals suddenly break after a random time with the following error message.
Couldn't load the data for this visual
Couldn't retrieve the data for this visual. please try again later.
Http status code 403
when you hit F5 (refresh) the report works fine again.
anybody knows how we can fix this?
Solved! Go to Solution.
Hi @Karola
Here you are using app owns data to embed your report to your customer. You customers don't need to have access to Power BI. They will access your embedded report in portal by embedded token you assigned to them.
Each token has its lifetime, so I think your issue should be caused by embedded token expiration.
This is the workloads that how your customer gets embedded token.
For reference: Embed for your customers
Based on my research, we can try to use the token lifetime policy and Assign policy to a service principal to configure the expiretime up to 24 hours, please refer to this document and thread:
Configurable token lifetimes in the Microsoft identity platform (preview)
Access token setting expiration times
You can also keep the default expire time and generate a new token before expire to update. when generate an embedded token, it will return the expire time, then you can generate a new token before the expire time, please refer to the example code with javascript
https://github.com/microsoft/PowerBI-JavaScript/wiki/Update-Embed-Token
https://github.com/microsoft/PowerBI-JavaScript/wiki/Refresh-token-using-JavaScript-SDK-example
we did not find sample code by RESTful, but the logic should be similar.
Update:
following policy make the expire time up to 2 hours (token refreshed when 04:55 UTC+0)
$policy = New-AzureADPolicy -Definition @('{"TokenLifetimePolicy":{"Version":1,"AccessTokenLifetime":"02:00:00","MaxAgeSessionSingleFactor":"02:00:00"}}') -DisplayName "ApiDefaultPolicyScenario" -IsOrganizationDefault $false -Type "TokenLifetimePolicy"
Best Regards,
Rico Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @Karola
Here you are using app owns data to embed your report to your customer. You customers don't need to have access to Power BI. They will access your embedded report in portal by embedded token you assigned to them.
Each token has its lifetime, so I think your issue should be caused by embedded token expiration.
This is the workloads that how your customer gets embedded token.
For reference: Embed for your customers
Based on my research, we can try to use the token lifetime policy and Assign policy to a service principal to configure the expiretime up to 24 hours, please refer to this document and thread:
Configurable token lifetimes in the Microsoft identity platform (preview)
Access token setting expiration times
You can also keep the default expire time and generate a new token before expire to update. when generate an embedded token, it will return the expire time, then you can generate a new token before the expire time, please refer to the example code with javascript
https://github.com/microsoft/PowerBI-JavaScript/wiki/Update-Embed-Token
https://github.com/microsoft/PowerBI-JavaScript/wiki/Refresh-token-using-JavaScript-SDK-example
we did not find sample code by RESTful, but the logic should be similar.
Update:
following policy make the expire time up to 2 hours (token refreshed when 04:55 UTC+0)
$policy = New-AzureADPolicy -Definition @('{"TokenLifetimePolicy":{"Version":1,"AccessTokenLifetime":"02:00:00","MaxAgeSessionSingleFactor":"02:00:00"}}') -DisplayName "ApiDefaultPolicyScenario" -IsOrganizationDefault $false -Type "TokenLifetimePolicy"
Best Regards,
Rico Zhou
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
@v-rzhou-msft thank you, just figured out that the token expiration was causing the issue. it looked very random in the beginning but we can now reproduce it exactly. We are deciding if we want to expand expiration or renew.
thank you for your answer and the links.
how frequently do you refresh your cube?
User | Count |
---|---|
15 | |
5 | |
2 | |
1 | |
1 |
User | Count |
---|---|
16 | |
4 | |
3 | |
1 | |
1 |