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!The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!
Dear Power BI Team,
I have been encountering several issues with DirectQuery mode following the (Dec 2024) and (Jan 2025) updates. These problems occur randomly and often require a restart to resolve. Common errors include “Could not retrieve data” and “Couldn't connect to the server,” which significantly disrupt workflow.
Recently, I faced another issue. After adding two columns to a database view and refreshing the data in my report (running on DirectQuery), I later removed the columns from the database and attempted to refresh the data in Power BI. Although these columns were never used in the report, the report stopped functioning and displayed an error stating that the columns couldn't be retrieved.
Attempts to refresh the data resulted in a “Cannot connect to server” error. When I tried to manually remove the columns via the Data tab, Power BI froze after deleting just one column. I restarted the application and retried the process, but it continued to freeze after deleting a single column.
I reverted to an older version of Power BI, and it worked without issues. I was able to refresh the data and successfully remove the unnecessary columns. However, when I reopened the same report in the (Jan 2025) update, it failed again. It displayed an error related to a columns that no longer exists in the data or report. After multiple attempts—including clearing the cache and restarting the application—I was eventually able to resolve the issue, but the process was unnecessarily time-consuming.
I would greatly appreciate your support in improving the reliability of the newer Power BI versions, as the older versions seem to more reliable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.