Data Pane flickers/jitters uncontrollably during mouse scroll
Power BI Desktop (Oct 2026) - Data Pane flickers/jitters uncontrollably during mouse scroll. The latest version of Power BI Desktop causes a lot of problem. Please update it immediately.!!! Power BI desktop should not have auto update. YOur auto update sucks!!! I have over 100 dashboards using Power BI and your latest update has given me a lot of problems
Option to preserve original text casing for imported text values
Idea. Add a column or model level setting to keep the exact casing of each text value on load, for example a case sensitive option for text columns. Why. Power BI treats text values as case insensitive and shows the casing of the first value it encounters. In a reported example a City column with PunE, Pune, pune and PUNE loads as four rows that all show PunE. This is expected engine behavior, but it surprises people building connectors and models where the original casing matters, for example codes, identifiers or names. Suggested behavior. An opt in setting per column or per model that preserves the source casing and treats differently cased values as distinct, with clear documentation of the storage and performance impact. Benefit. Fewer workarounds such as adding a helper column with a hash or a prefix, and more predictable results when the source data is case sensitive. Source thread (raised by another community member) https://community.fabric.microsoft.com/discussions/power-bi-services/x/5368143[Fabric Copy Job] Unable to parameterize SQL Database name for Deployment Pipelines (CI/CD)
I spotted an issue with the Fabric Copy Job item regarding the parameterization of SQL Server sources within Deployment Pipelines. Scenario: I am using a Copy Job to ingest data from an on-premises SQL Server to a Fabric Lakehouse. My environment utilizes Deployment Pipelines to promote content from Dev to UAT/Prod. I am attempting to use Variable Libraries to handle connection differences across these environments. The Issue: While I can successfully bind the SQL Server Connection object to a Library Variable, the Database Name field in the source settings does not support parameterization or variable binding. It remains hardcoded. Consequently, when I deploy the Copy Job from the Development workspace to UAT/Prod, the job continues to target the hardcoded Development database name (e.g., fabnavtest1), which is incorrect for the target environment. Troubleshooting Steps Taken: Verified that the Connection ID is successfully parameterized using the Variable Library VL_FDL_Config. Attempted to locate the underlying JSON definition via OneLake Explorer (similar to the workaround available for Dataflow Gen 2 destination issues) to manually inject a parameter, but the Copy Job folder appears empty/inaccessible. Technical Evidence: Below is the JSON definition of the source. You can see that connectionVariableLibrary is set correctly, but the database property is a hardcoded string with no option to bind it to a variable. JSON { "properties": { "jobMode": "Batch", "source": { "type": "SqlServerTable", "connectionSettings": { "type": "SqlServer", "typeProperties": { "database": "fabnavtest1" }, "externalReferences": { "connectionVariableLibrary": { "variableName": "SQL_CONN_ID", "libraryName": "VL_FDL_Config" } } } } } } Impact: This prevents the successful use of Deployment Pipelines for Copy Jobs using SQL Server sources, as we cannot dynamically change the database target per environment. Thank you for your help
BUG: Fabric pipelines stored procedure activity does not update target correctly after deployment
I have a data pipeline that uses the stored procedure activity to call a sproc in a warehouse in the same workspace. This works fine in dev, but after using the deployment pipeline and running in the test workspace, I get the below error: The server address cited in the error message is indeed for the dev workspace, but when I look into the source code for the activity, I see that the connection details are correctly listed as the test workspace server address and workspace ID: I've also checked the JSON definition of the entire pipeline and can't find any reference to the dev workspace server name either, so I'm not sure why it's attempting to access the dev workspace. The only fix for this appears to delete and recreate the activity in the test environment, invalidating the pipeline. As such, I believe this is a bug in the pipeline activity feature and requires fixing. Procedure runs successfully when directly executed in SSMS
Power Query Editor window no longer states which file it relates to.
In previous versions, the Power Query Editor window would include the name of the file it relates to. Now, all Power Query Editor windows are all called "Power Query Editor". I often work with multiple reports at once, and have Power Query Editor open for multiple reports. If the files are different versions of the same report, it is virtually impossible to confirm with Power Query Editor window you are working in. Perhaps there is somewhere you can look to get this information, but in the name of the window itself was incredibly convenient and just made sense.Stop Auto update on Power BI Desktop
My team has been experiencing a lot of problems every time there is a Power BI Desktop updates. Our latest problems were - Data Pane flickers/jitters when using mouse scroll - Backend engine update isn't complete during the new update causes my previous version of Power BI not to work!!! This happened to me because I've over 70 tables and over 30 reports tabs. Even the basic command like calculate filter and count function doesn't work!!! This is horrible!!!! My question is how do I stop auto update on Power BI desktop!!!!! Your programmer team when update need to considered the fact that there are thousands of corporate users using your product and every time you update the product, it causes big problem!!! Our Power BI expert is very tired after every new update!!! what used to work in the past now doesn't!!!! You guys better test the program properly before update
Lakehouse shortcuts do not persist variables from Variable Library (Connection, Location, Subpath)
I am trying to use variables from a Variable Library when setting up an ADLS Gen2 shortcut in my Lakehouse. Specifically, I select variables for the Target Connection, Target Location, and Target Subpath. The UI lets me pick the variables without any problem, but once I click save, the changes are not saved at all. Expected result: The shortcut should keep the selected variables linked. Actual result: The variables did not appear, and the settings reset to previous values. What I already tried: Tested this across different Lakehouses. Tried both editing existing shortcuts and creating new ones from scratch. The issue happens every time. Is anyone else having this problem, or is this a known bug?Power Query Intellisense not working well
Having an 'auto complete' feature in a coding language is great. When it work right. Power Query auto complete does NOT. Try this: Open a query and click the Custom Column on the Add Column menu. The dialog box opens where you input your M language statement. Now type into the formula box "Text.Combine" and see the suggestions it brings up and more importantly WHERE IN THE LIST it places the highlight. If you're fast on the keyboard and hit the TAB key without looking at the suggestion it gives, you will get "TextTable.Combine". What is TextTable.Combine? That's not even a Power Query Function. It an erroneous amalgamation of the FISRT word I typed plus the full command that it chose. Look at the screen shot below and note the SUGGESTED row it highlights (the one it will take if you simply hit <Tab>) as opposed to the one three rows below it THAT IS AN EXACT MATCH OF WHAT YOU ARE TYPING Seems Intellisense cannot match on the entire phrase, but only looks at the last word after the period? After typing "Text." I shouild see a list of all the functions that start with "Text." not ones that start with other words. I see this as a bug
Power query steps can't be edited since Sept 26 update
The overhauled power query editor in power bi is not allowing edits on steps created via the UI. It's bad enough that adding Missing.Ignore disables the edit, but now I can't even reopen a Choose Columns step and change my mind. Same issue on Expand Fields after a merge, and Added Items on a SAP view.
Regression: Google BigQuery connector loses Native SQL Query UI on gear icon click
Hello Power BI Team, Following the recent updates and the rollout of the new BigQuery connector implementation (ADBC), the Power Query UI is experiencing a significant regression regarding the Value.NativeQuery step. Previously, clicking the gear icon on the "Source" step of a BigQuery connection opened a dialog box clearly displaying the Native SQL Statement, allowing for easy copying, pasting, and formatting. Now, this UI is completely missing or fails to map for BigQuery connections. As a BI Architect, this severely disrupts the workflow. Instead of a clean SQL text box (which is still perfectly functional and stable in the SQL Server connector), we are forced to use the Advanced Editor. This exposes the raw M code, wrapping the SQL in double quotes and converting all line breaks to #(lf), making it extremely tedious to copy/paste the query directly to BigQuery Studio for testing without manual text parsing. The SQL Server connector handles NativeQuery UI mapping flawlessly. The BigQuery connector needs to maintain this same parity and stability. Steps to Reproduce: Step 1: Connect to Google BigQuery and input a Native SQL query via Advanced Options. Step 2: Apply the step, then click the gear icon on the "Source" step to edit the SQL. Step 3: Notice the UI no longer provides the clean SQL input box. Please investigate and restore the Native Query UI parsing for BigQuery connections.
