Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
One visual in the PowerBI service does not render correctly and the following error is displayed:
Couldn't retrieve the data for this visual. Please try again later.
Please try again later or contact support. If you contact support, please provide these details.
This only occurs in the PowerBI Service; the visuals are correctly displayed in the desktop version.
The data is from a measure calculated from a direct query to an Azure for PostgreSQL database. There are other visuals in the report, reading from not only the same database, but from the same table which do render correctly. There is also another visual with essentially the same measure calculated from a different table which does render correctly. The measure which seems to cause the issue is as follows:
AllPlayers =
CALCULATE(
COUNTROWS ('public dim_players'),
FILTER (
ALLEXCEPT('public dim_players', 'public dim_date'[date]),
'public dim_players'[creation_date] <= MAX('public dim_date'[id]) &&
(
ISBLANK ( 'public dim_players'[deletion_date] ) ||
'public dim_players'[deletion_date] > MAX('public dim_date'[id])
)
),
USERELATIONSHIP('public dim_players'[creation_date], 'public dim_date'[id]),
USERELATIONSHIP('public dim_players'[deletion_date], 'public dim_date'[id]),
USERELATIONSHIP('public dim_players'[game_id], 'public dim_games'[game_id]),
USERELATIONSHIP('public dim_players'[group_id], 'public dim_groups'[group_id])
) + 0
A visual based on the same measure run on a 'public dim_moderators' instead of 'public dim_players' table however displays just fine. Visuals based on other measures involving the public dim_players table also work just fine within the report.
Any ideas what could cause this issue?
If it is the measure itself, could this measure be created in a simpler, more efficient manner?
Hi @Anonymous ,
This is a very common error faced in Services when DirectQuery is used. This mainly occurs because Services takes time to get data and if the time exceeds a particular threshold, it throws the error. This threshold erstriction is not present in Desktop and hence you won't see the error there.
What you can do is use Performance analyzer in Power BI Desktop and try to optimize your DAX as much as possible. DAX+DirectQuery takes a lot of time to render the visual.
If nothing works from your end, you can raise a ticket with MS Support.
Give a thumbs up if this post helped you in any way and mark this post as solution if it solved your query !!!
Thanks @Anand24
I thought it might to do with timeout thresholds, but I cannot figure out why this is happening.
Do you know of a way in which I can optimize the query in the original post? From what I can see is that ALLEXCEPT is taking a longtime to process.
Hi @Anonymous ,
You can refer to this blog to improve DAX performance.
https://maqsoftware.com/expertise/powerbi/dax-best-practices
Best Regards,
Liang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Bumping this as I haven't been able to figure it out yet and the issue is persisting. Will any additional information to mytop post be helpeful?
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the September 2025 Power BI update to learn about new features.