01-30-2019 05:10 PM
We utilised the API within a webpage to return PowerBI account Reports.
The authentication token is passed to the website and the content displayed perfectly inside a webbrowser window.
There is no problem with the report.
The API gives full operation and all visuals operate in the manner expected - including all drill downs and drill throughs etc.
The problem occurs when focus is moved from the webpage to another, and then you return to the report.
After some period of time - cannot say for sure - you can return to the report and the report appears to be working well and you can navigate the report ok - BUT - if you attempt a drill down or expand you get the X on the visuals and "This content isnt available. Learn more about PowerBI"
If I refresh the entire webpage - the content and all functiomality returns to normal.
Can someone explain why the API works well in the webpage, but after some period of inactivity, returns and errors on visuals.
Is there some kind of inactivity timeout to be considered when utilising the API ?
02-01-2019 12:34 AM
If you didn't make any change in the Azure, the token will expire in one hour. Please refer to active-directory-configurable-token-lifetimes.
This is the most possible cause. Please check your application to find out a way to extend the life of the token automatically.
Can you also share some snapshots, please?
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
02-05-2019 02:16 AM
Thanks for the response.
Yes I think you were correct in terms of the auth token.
If we work in the API for more than an hour the first drill down after the hour is up returns the issue where the visuals dont show data.
That points to the auth token being used - and as I understand it we should be getting a refresh token after the auth token as that has a longer expiry period. We used a powerbi API sample from web resource pages so clealry it was missing in there.
I wondered if you had any samples with the refresh token code in it we could work with ?
02-11-2019 01:14 AM
We are still having issues around the token (refresh and access token) timeouts.
I wonder what the best course of action was to get assistance offline by supplying code and a better example of whats trying to be achieved. Could someone perhaps provide some guidance on the next step in the support proces beyonfd the community.