Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. Register now.
Hello, is anyone else using Planview AgilePlace as a data source for their Power BI reporting? I am having ongoing refresh issues with their OData and API connections. I was wondering if anyone experiences similar issues. Thanks!
This is just an open discussion to understand if it's my organization or if it's a broader issue for the Planview user community.
Solved! Go to Solution.
Hey Justeen ! You're not alone, I saw a number of users have reported intermittent issues when connecting Power BI to Planview AgilePlace via OData and their REST API, especially when it comes to scheduled refreshes in the Power BI Service.
The OData endpoint can be quite slow, especially with larger boards or historical data. This often results in gateway timeouts.
If you're using basic auth or an API token, tokens sometimes expire or get revoked without notice. This results in silent failures.
the API returns partial or stale data depending on load or board structure.
Try to limit the data you pull by using filters ($filter, $top, $select) to reduce the dataset as much as possible during initial load.
Incremental refresh (if available in your Power BI tier) helps with large historical datasets.
Offload the heavy lifting to Power BI Dataflows and only connect the final data to your report.
Hey Justeen ! You're not alone, I saw a number of users have reported intermittent issues when connecting Power BI to Planview AgilePlace via OData and their REST API, especially when it comes to scheduled refreshes in the Power BI Service.
The OData endpoint can be quite slow, especially with larger boards or historical data. This often results in gateway timeouts.
If you're using basic auth or an API token, tokens sometimes expire or get revoked without notice. This results in silent failures.
the API returns partial or stale data depending on load or board structure.
Try to limit the data you pull by using filters ($filter, $top, $select) to reduce the dataset as much as possible during initial load.
Incremental refresh (if available in your Power BI tier) helps with large historical datasets.
Offload the heavy lifting to Power BI Dataflows and only connect the final data to your report.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
4 | |
4 | |
3 | |
3 | |
2 |