Yes, I'm using the latest version of Power BI. And in fact, this bug was introduced with the latest verison. Before that, I don't think I've had this problem. It happens in all reports, basically every time I use Power BI, and my colleagues experience the same issue.
Thanks for your reply. May I know what kind of connection mode are these reports created with? And please try the following workarounds to see whether they can solve your problem.
1 Quit other unncessary applications to make sure there are enough memory for Power BI Desktop
2 Clear Cache in Options(File>Options and Settings>Options)
3 Reinsatll Power BI Desktop
4 Downgrade to earlier version of Power BI Desktop as a workaround
The reports use different connections - as I said its not just me who experience this issue, it's all Power BI developers I recently spoke with (5 people so far). The report I'm currently working on uses an import connection.
Hi @Quiny_Harl
May I know whether this issue only happens in one report or all of your reports? Are you using the latest version of Power BI Desktop?
Best Regards,
Community Support Team _Caiyun