Issues Ideas

AI instructions deployed via updateDefinition are ignored by Prep data for AI and MCP

ronnhoha — Fri, 13 Nov 2026 12:59:13 GMT

Setup: Direct Lake semantic models on Fabric capacity, Q&A enabled, AI instructions under 10,000 characters. Deployed with the Fabric REST API semanticModels/{id}/updateDefinition (TMDL). The instructions are in definition/cultures/en-US.tmdl, linguisticMetadata, "CustomInstructions", which is where a Prep data for AI save writes them (confirmed with getDefinition after a dialog save).

Expected: per "Prepare your data for AI", considerations and limitations, LSDL changes made through Git or deployment pipelines sync after a service refresh (once a day for Direct Lake). After that, the Prep data for AI dialog, Copilot and GetSemanticModelSchema on the Power BI and Fabric IQ MCP servers use the deployed instructions.

Actual:

getDefinition returns the deployed CustomInstructions unchanged, but GetSemanticModelSchema returns no custom instructions. On one model this held for more than two months of daily refreshes.
The Prep data for AI dialog shows the instructions box empty (0/10000).
Pasting the same text in the dialog and pressing Apply makes the service's Copilot settings carry it within about 5 minutes. Fabric IQ MCP then served it within 10 minutes; the Power BI remote MCP still served none 10 minutes later, and on an earlier test only the next morning.
After an Apply, the served text no longer follows the definition: later updateDefinition calls with different instruction text left the applied text in service.
The dialog reads /explore/nl/workspaces/{ws}/semanticModel/{id}/copilotTooling?lsdlFallback=false, which returns 204 on both models, including the one whose instructions are served. With lsdlFallback=true it returns persistedCopilotSettings with requiresMigration: true.

Impact: AI instructions cannot be managed from source control or CI/CD. Every change needs a manual paste in the service, and a deployment can leave the served instructions out of step with the model without any error.

Ask: a supported programmatic route for AI instructions (a definition part or a REST API), or a fix so the documented Git, deployment pipeline and refresh route works for Direct Lake models; and documentation of where the served instructions are stored and when a deployment updates or clears them.

Also reported on GitHub: https://github.com/microsoft/powerbi-modeling-mcp/issues/147 and https://github.com/microsoft/skills-for-fabric/issues/72. A support ticket is open with the model IDs.

Add Vertical Spacing Controls Between X-Axis Labels, Scrollbar, and Legend in Power BI Charts

Bharath_Kalagan — Wed, 11 Nov 2026 14:12:20 GMT

I am using a native Power BI column chart titled "Realized Incentives by Year", with year values on the X-axis, a horizontal scrollbar, and a legend positioned at the bottom.

Currently, the spacing between the X-axis year labels and the scrollbar, as well as between the scrollbar and the legend, appears to be automatically controlled by Power BI.

There does not appear to be a dedicated formatting option to adjust these vertical gaps independently.

Add a fixed / maximum bar width option for column and bar charts

Bharath_Kalagan — Wed, 11 Nov 2026 13:56:53 GMT

Problem:

In native column and bar charts, the bar width is calculated automatically from the number of categories on the axis. When slicers reduce the number of categories (for example, from 10 years to 3), the bars stretch to fill the visual and become very wide. This makes the same visual look inconsistent across filter states and against other charts on the page.

New Power Query Experience locale issues

milosi — Wed, 11 Nov 2026 10:09:05 GMT

Hi Team,

somehow the "New Power Query Experience" has broken the import locale in Power BI Desktop.
I have had the issue since the August Update of Power BI Desktop.

I'm a trainer giving Dashboard-in-a-day workshops in german for multiple Years now, so im working with the same exact official DIAD data, that has worked for many years. It is a csv. containing data in an US-format.

My windows language, and my Power BI Desktop GUI Language is set to german.

So the first step in a german training ist always to set the import locale:

Options and settings -> options -> current file -> regional setting -> import locale -> set to English (USA)

With the new Power Query Experience enabled, when i then import the csv. it will somehow read the decimal revenue as a whole number:

This is also independent of the encoding i define.

If i then deactivate the new Power Query Experience from options -> preview features without changing anything else, it will correctly read the data:

Is there any reason, explanaition or fix for this behavior? Could someone also working in non-US languages confirm this behavior?

Best regards.

----

Additional Info:

If i have set the import locale to English(USA), activate the preview feature (so my case 1 from above) and then switch my Power BI GUI language to english, it then works.... So in the new power query experience, the data-type of column seems to be dependent on my GUI language... which seems concerning

Incorrect storage values on Fabric Capacity Metrics Report

JoshT — Mon, 02 Nov 2026 11:25:50 GMT

I have been investigating how storage is reported and billed, and discovered that the Fabric Capacity Metrics report's 'Current Storage (GB)' figure is inconsistent with the same value reported elsewhere in the service. A week ago, I truncated all tables in warehouses in a given workspace. There are no other storage items in that workspace. A week later and after several refreshes, we are still getting a value of 38.72GB in current storage for that workspace:

Looking at that workspace's storage count, we see there's actually 0MB reported:

Using a notebook to retrieve warehouse file sizes reveals all warehouses in the workspace with a file size of 0:

So why is the metrics capacity app returning a value (which has slightly dropped since the truncation)? Can we trust onelake storage billing if this isn't accurate?

File not opening or refreshing consistently, unable to report issue

jmsny — Thu, 29 Oct 2026 16:48:34 GMT

I'm suddenly having trouble opening a PowerBI file and I'm at my wits end. I haven't made any changes since last time. I can't even report the issue because when I try to, I get "Something went wrong". This export just sits there for months until I have to make an update, and this is the first time I've been unable to do anything.

Most of the time I can't open the file, but on some occasions it will open and eventually start giving errors. On top of not being able to open, there is an issue when refreshing. On my backup, where an older version of the data is saved, I see this:

Attempt by method 'Microsoft.Mashup.SqlTranslator.SqlParser.Parse(System.String)' to access method 'Microsoft.Mashup.ScriptDom.TSql100Parser..ctor(Boolean)' failed.

On my current version, after refreshing, I see "Some of the tables have incomplete or no data."

This is what I get when I'm able to open it and refresh my data. Cannot include the error for when it opens due to the ridiculous 20,000 character limit on here. Pasting all the text here because otherwise I get an error that I have invalid HTML in my post.

Release:

October 2026

Product Version:

2.159.883.0 (26.10)+c91504a0c4eaaca794e7ad66f58963d139355c91 (x64)

Error Message:

We are encountering problems. Please close and restart Power BI Desktop.

Stack Trace:

Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesCrashedAfterSuccessfulConnectionException

at Microsoft.PowerBI.Client.Windows.MainForm.OnAnalysisServicesProcessExited(AnalysisServicesProcessExitedEventArgs e)

at Microsoft.Practices.Prism.PubSubEvents.EventSubscription`1.<>c__DisplayClass2.<GetExecutionStrategy>b__0(Object[] arguments)

at Microsoft.Practices.Prism.PubSubEvents.EventBase.InternalPublish(Object[] arguments)

at Microsoft.PowerBI.Client.Windows.Services.EventAggregationService.<>c__DisplayClass19_0`2.<PublishAndMarshalExceptions>b__0()

at Microsoft.Mashup.Host.Document.SynchronizationContextExtensions.<>c__DisplayClass2_0.<SendAndMarshalExceptions>b__0(Object null)

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

at Microsoft.Mashup.Host.Document.SynchronizationContextExtensions.SendAndMarshalExceptions(SynchronizationContext context, Action callback)

at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

Stack Trace Message:

We are encountering problems. Please close and restart Power BI Desktop.

Invocation Stack Trace:

at Microsoft.Mashup.Host.Document.ExceptionExtensions.GetCurrentInvocationStackTrace()

at Microsoft.Mashup.Client.UI.Shared.StackTraceInfo..ctor(String exceptionStackTrace, String invocationStackTrace, String exceptionMessage)

at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBIUserFeedbackServices.GetStackTraceInfo(Exception e)

at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBIUserFeedbackServices.ReportException(IWindowHandle activeWindow, IUIHost uiHost, FeedbackPackageInfo feedbackPackageInfo, Exception e, Boolean useGDICapture)

at Microsoft.Mashup.Client.UI.Shared.UnexpectedExceptionHandler.<>c__DisplayClass14_0.<HandleException>b__0()

at Microsoft.Mashup.Host.Document.SynchronizationContextExtensions.<>c__DisplayClass2_0.<SendAndMarshalExceptions>b__0(Object null)

at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)

at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)

at System.Delegate.DynamicInvokeImpl(Object[] args)

at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)

at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)

at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)

at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)

at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)

at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)

at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)

at Microsoft.Mashup.Client.UI.Windows.DialogWindowBase.ShowModal(IWindowHandle windowHandle)

at Microsoft.Mashup.Client.UI.Shared.WindowManager.ShowModal[T](T dialog, Func`1 showModalFunction)

at Microsoft.PowerBI.Client.Windows.Services.PowerBIWindowService.<>c__DisplayClass11_0.<Microsoft.Mashup.Client.UI.Shared.Ux.IWindowService.ShowDialog>b__0()

at Microsoft.PowerBI.Client.Windows.Services.PowerBIWindowService.Trace[T](String action, String title, String details, Func`1 showDialog, Func`2 getResult, T disposedResult)

at Microsoft.PowerBI.Client.Windows.Services.PowerBIWindowService.Trace(String action, String title, String details, Func`1 showDialog)

at Microsoft.PowerBI.Client.Windows.Services.PowerBIWindowService.Microsoft.Mashup.Client.UI.Shared.Ux.IWindowService.ShowDialog(IDialog dialog)

at Microsoft.PowerBI.Client.Windows.FloatingDialog.KoLoadToReportDialog.<>c__DisplayClass21_0.<ShowDialog>b__0()

at Microsoft.PowerBI.Client.Windows.Services.TelemetryHelper.RunInActivity[T](IPowerBITelemetryService telemetryService, ITelemetryEvent telemetryEvent, Func`1 action)

at Microsoft.PowerBI.Client.Windows.Services.LoadToReportDialogManager.Show(ILegacyUIHost uiHost, IExceptionHandler exceptionHandler, IPowerBIWindowService windowService, IPowerBIQueryErrorEditor queryErrorEditor, LoadToModelContext loadToModelContext, LocalizedString title)

at Microsoft.PowerBI.Client.Windows.FloatingDialog.KoLoadToReportDialog.<>c__DisplayClass20_0.<TryShowDialogForQueriesCore>b__0()

at Microsoft.PowerBI.Client.Windows.Report.SynchronizeLooselyWithQueries[T](Func`1 action)

at Microsoft.PowerBI.Client.Windows.FloatingDialog.KoLoadToReportDialog.TryShowDialogForQueriesCore(Report report, IExceptionHandler exceptionHandler, IPowerBIWindowService windowService, IPowerBIQueryErrorEditor queryErrorEditor, IEnumerable`1 queriesToApply, String loadReason, ITelemetryService modelingTelemetryService, QueryLoadStages queryLoadStages, LocalizedString title, Action`1 beforeSchemaSyncCallback, Action`1 afterSchemaSyncCallback, Boolean synchronizeLooselyWithQueries, IEnumerable`1 mashupIneligibleTablesToRefreshData, ModelSyncImpact minimumModelSyncImpact)

at Microsoft.PowerBI.Client.Windows.ModelAuthoringHostService.RefreshQueries(String refreshReason, QueryLoadStages queryLoadStages, IEnumerable`1 queriesToRefresh, ITelemetryService telemetryService, IEnumerable`1 additionalTablesToRefreshData)

at Microsoft.PowerBI.Client.Windows.ModelAuthoringHostService.<RefreshAllQueries_SchemaAndData>d__19.MoveNext()

at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)

at Microsoft.PowerBI.Client.Windows.ModelAuthoringHostService.RefreshAllQueries_SchemaAndData()

at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)

at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)

at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

at Microsoft.PowerBI.Client.Windows.WebView2.WebView2Interop.<>c__DisplayClass36_0.<InvokeCsMethod>b__0()

at Microsoft.PowerBI.Client.Windows.WebView2.WebView2Interop.<>c__DisplayClass39_0`1.<RunAsync>b__0(Object s)

at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)

at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)

at System.Delegate.DynamicInvokeImpl(Object[] args)

at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)

at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)

at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)

at System.Windows.Forms.Control.InvokeMarshaledCallbacks()

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)

at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)

at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)

at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)

at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)

at Microsoft.Mashup.Client.UI.Shared.WindowManager.ShowModal[T](T dialog, Func`1 showModalFunction)

at Microsoft.PowerBI.Client.AppModule.<>c__DisplayClass4_0.<Run>b__0()

at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<>c__DisplayClass3_0.<HandleExceptionsWithNestedTasks>b__0()

at Microsoft.Mashup.Host.Document.ExceptionHandlerExtensions.HandleExceptions(IExceptionHandler exceptionHandler, Action action)

at Microsoft.PowerBI.Client.AppModule.Run()

at Microsoft.PowerBI.Client.Program.RunApplicationFlow(String[] args, IPowerBIRootTrace trace)

at Microsoft.PowerBI.Client.Program.Main(String[] args)

PowerBINonFatalError:

{"AppName":"PBIDesktop","AppVersion":"2.159.883.0","ModuleName":"Microsoft.PowerBI.Client.Windows.dll","Component":"Microsoft.PowerBI.Client.Windows.MainForm","Error":"Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesCrashedAfterSuccessfulConnectionException","MethodDef":"OnAnalysisServicesProcessExited","ErrorOffset":"44","ErrorCode":""}

OS Version:

Microsoft Windows NT 10.0.26200.0 (x64 en-US)

CLR Version:

4.8 or later [Release Number = 533509]

Peak Virtual Memory:

86.5 GB

Private Memory:

865 MB

Peak Working Set:

1.01 GB

IE Version:

11.1882.26100.0

User ID:

d6f14ab9-ccbe-4f8e-9453-72376c917895

Workbook Package Info:

1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: False.

Telemetry Enabled:

True

Snapshot Trace Logs:

C:\...\FrownSnapShot59be0b6d-62d3-4efe-bbac-95d78139a051.zip

Model Default Mode:

Import

Model Version:

PowerBI_V3

Performance Trace Logs:

C:\...\PerformanceTraces.zip

Enabled Preview Features:

PBI_EnableResourceExpressionImpersonation

PBI_scorecardVisual

PBI_setLabelOnExportPdf

PBI_oneDriveSave

PBI_oneDriveShare

PBI_openInVsCode

PBI_useModernMashupEditor

PBI_aiNarrativesVisual

PBI_copilotUnifiedTooling

MashupFlight_EnableOracleBundledOdacProviderV2

PBI_sqlDbNativeArtifactsOnDesktop

PBI_warehouseSnapshotArtifactsOnDesktop

PBI_enableExportQueries

PBI_ganttChartPreview

MashupFlight_EnableFirewallFlowsWithDataSources

Disabled Preview Features:

PBI_UseRedshiftODBCV2

PQ_UseBaseViewXmlForSharePoint

PBI_databricksLegacyOdbcVersionEnabled

PBI_googleBigQueryLegacyOdbcVersionEnabled

PBI_snowflakeLegacyOdbcVersionEnabled

PBI_qnaLiveConnect

PBI_b2bExternalDatasetSharing

PBI_onObject

PBI_publishDialogsSupportSubfolders

PBI_customCalendars

PBI_enableOracleBundledOdacProviderForDQ

PBI_dynamicCalcColumn

PBI_MicrosoftGraphMailConnector

Disabled DirectQuery Options:

TreatHanaAsRelationalSource

Cloud:

GlobalCloud

PowerBIUserFeedbackServices_IsReported:

True

Formulas:

section Section1;

shared #"Dashboard" = let

Source = OData.Feed("{OData Link}", null, [Implementation="2.0"]),

#"Dashboard | 6e45ff22_table" = Source{[Name="Dashboard | 6e45ff22",Signature="table"]}[Data]

#"Dashboard | 6e45ff22_table";

shared Office = let

Source = Table.FromRows(Json.Document(Binary.Decompress(Binary.FromText("i45WcsksLkgsSc5ILVLSUTJUitWJVgpKLS5RyE9T8E9Ly0xOBQobgYVdMtPSUotS88BCxkqxsQA=", BinaryEncoding.Base64), Compression.Deflate)), let _t = ((type nullable text) meta [Serialized.Text = true]) in type table [Office = _t, Sort = _t]),

#"Changed Type" = Table.TransformColumnTypes(Source,{{"Office", type text}})

#"Changed Type";

WebView2 Runtime Version:

156.0.4314.50

WebView2 SDK Version:

1.0.2365.46

German localization errors in Power BI Service UI

ASchmieder — Wed, 28 Oct 2026 09:06:35 GMT

Hi Power BI team,

I came across two German localization issues in the Power BI Service (de-DE):

My workspace ("Mein Arbeitsbereich")
The description says "Arbeitsfüssen" instead of the correct "Arbeitsflüssen".

Workspaces / Task flows
An unnamed task flow is shown as "Unbenaufgehter Aufgabenfluss". "Unbenaufgehter" does not exist in German and seems to be a localization error.

Both texts are part of the standard Power BI Service interface.

I have attached screenshots showing both issues.

Thanks for taking a look!

Dark mode: visual "More options" menu text unreadable (white on white) in reports with light theme

provoj — Tue, 27 Oct 2026 22:56:11 GMT

With Power BI Desktop set to the dark app theme, the "More options" (...) menu on visuals renders its item labels in near-white text on a white menu background, making the options unreadable. The items still function when clicked; the problem is purely visual.

Details:

Occurs on every visual, on every page, in a report using a light custom theme (theme JSON: background #FFFFFF, foreground #231f20).
Switching Desktop to the light app theme makes the menu readable immediately. Switching back to dark reproduces it.
Changing the report theme's structural background / backgroundLight values has no effect on the menu, so the menu is not reading the report theme for its colors.
The hovered item renders correctly (dark text on gray highlight); only the non-hovered items are affected.
Reproduced consistently in the same file; other reports in the same install are not affected the same way.

Expected: menu text should use a dark-mode-appropriate color, or the menu background should follow the app theme.

Version: 2.158.1304.0 64-bit (September 2026)

OS: Windows 11

PBIR: Desktop writes preserveNewVisualVisibility in bookmarks but rejects it on reopen

mkonan_powerbi — Tue, 27 Oct 2026 19:25:51 GMT

Summary
In a PBIP project using the PBIR format, Power BI Desktop adds the property preserveNewVisualVisibility under options when creating a bookmark. The bookmark file still declares the bookmark/2.1.0 schema, which doesn’t define this property. When the project is reopened, Desktop validates the file against that schema and blocks opening the project with a validation error for every affected bookmark.

Environment

Power BI Desktop 2.159.883.0 (26.10) 64-bit, October 2026
Project format: PBIP with PBIR (definition/ folder)
Bookmark $schema: https://developer.microsoft.com/json-schemas/fabric/item/report/definition/bookmark/2.1.0/schema.json

Steps to reproduce

Open a PBIP project (PBIR format) in Power BI Desktop 2.159.883.0.
Create one or more bookmarks in the Bookmarks pane.
Save and close Desktop.
Reopen the .pbip file.

Expected result
The project opens normally with the new bookmarks.

Actual result
The project fails to open. One error is shown per new bookmark (displayed in French in my localized Desktop):

Une propriété supplémentaire « preserveNewVisualVisibility » a été incluse dans la propriété /options de 7ae761359fe775b3505c.bookmark.json.

(Approximate English: An additional property “preserveNewVisualVisibility” was included in the /options property of 7ae761359fe775b3505c.bookmark.json.)

The issue is reproducible: every bookmark created in this version triggers it at the next opening.

Workaround
Remove preserveNewVisualVisibility from options in each *.bookmark.json file before reopening the project. The project then opens normally, but the bookmark loses that setting.

Suggested fix
Either declare a bookmark schema version that includes preserveNewVisualVisibility when Desktop writes it, or have Desktop validate against the schema version that matches the properties it writes.

Unexpected Slicer Behavior with "Show Selected Text" Enabled

SantoshDhasmana — Tue, 27 Oct 2026 08:44:54 GMT

In the new slicer update, when I select a few values and enable the "Show Selected Text" option, the selected values are displayed correctly. However, when I subsequently unselect some of the values, those values are automatically selected again instead of remaining deselected.

Is this the expected behavior, or could this be an issue with the new slicer functionality?

Version: 2.159.883.0 64-bit (October 2026)

Thanks

Santosh Dhasmana

New list slicer: image not taken from column but from measure

GuyOutACube — Mon, 26 Oct 2026 13:35:46 GMT

Calculated columns typed/categorized as Image URL cannot be confirmed/selected in the flyout picker, whereas an identical DAX Measure categorized as Image URL is accepted immediately.

History Snapshot 'Edit Schedule' button is a 'submit' instead of a 'button'

beane031 — Mon, 26 Oct 2026 13:10:36 GMT

See original post here for moire details:

Issues setting snapshot schedule? | Microsoft Fabric Community

An issue arose from the septemeber 2026 update where the 'edit schedule' button for history snapshots was missing a 'type' making it default to submit which would open and immediately close the schedule editor page. Running the JavaScript below fixes the code to allow you to edit the schedule:

document.querySelector("button.btn-edit-schedule").type = "button"

Azure Maps missing from Desktop, and no longer visible online

liz72 — Mon, 26 Oct 2026 01:07:09 GMT

Is anyone else missing their Azure maps after these updates? I lost my desktop ones recently, though the online ones were still there. This morning, the online Azure maps are missing. The 'visual' is completely blank/transparent. I can select the visual but it shows the previously hidden visual underneath it.

If I open a new (blank) PBIX file and try to add a visual, the Azure Map visual doesn't even exist.

Scorecard Power BI Service Filter not function

SarahRahimah_04 — Fri, 23 Oct 2026 02:22:36 GMT

Hi,

My team and I tried to test scorecard with Power BI service report then, we connect several KPIs where we had filtered the same measure for different reporting units(the slicer). The slicer was based on the dropdown I have attached. Before this we can connect the metrics by choosing the filter first. Now, currently we cannot connect whenever we want to filter, the filter dropdown not showing any name/value.

Appreciate the helps since this is very urgent.

WebView2 Error in VM

RajeswariVegi — Thu, 22 Oct 2026 13:14:37 GMT

When I am working on powerbi desktop application in VM, it suddenly displays webview2 error and powerbi either goes to not responding state or crashes.

I have tried reinstalling the powerbi desktop

reinstalling it from microsoft store

clearing the cache

run as administrator

But nothing stated above are working.

Unnecessary Horizontal and Vertical Scrollbars in Power BI Reports When Viewed in Firefox

Amankumar0007 — Wed, 21 Oct 2026 14:41:42 GMT

I am experiencing an issue with Power BI reports when viewing them in the Firefox browser. Both horizontal and vertical scrollbars appear unnecessarily, even when the report content appears to fit within the available canvas.

Expected Behavior

The report should display without horizontal or vertical scrollbars when all visuals fit within the report canvas.

Actual Behavior

Unnecessary horizontal and vertical scrollbars appear in Firefox. Based on my testing, the issue appears to be limited to Card visuals and Button visuals, including buttons used for bookmark navigation. Other visuals do not appear to cause the same issue.

Troubleshooting Performed

Tried increasing and decreasing the Power BI report canvas size, but the issue persisted.
Investigated a possible browser-specific rendering issue.
Found a possible explanation in the Power BI Community suggesting that Firefox may handle sub-pixel overflow differently from Chrome and Edge. According to this explanation, visual boundaries extending slightly beyond the canvas (approximately 0.2–0.9 pixels) could trigger scrollbars.
However, I have not yet confirmed whether sub-pixel overflow is the root cause in this case.

Environment: Power BI report viewed in Mozilla Firefox. The issue has not yet been confirmed in other browsers.

Data pane: mouse wheel scrolling flickers/jumps when cursor is over field names

JorgeAFC — Tue, 20 Oct 2026 12:38:50 GMT

Description:

Version: Power BI Desktop 2.159.883.0 64-bit (October 2026)

Issue:
In the Data pane, when a table is expanded and its field list is taller than the pane (vertical scrollbar visible), scrolling with the mouse wheel does not work properly. The list flickers, jumps up and down, and does not move.

Steps to reproduce:

Open a report whose model has a table with many columns/measures (around 40 or more).
In the Data pane, expand that table so the field list is longer than the visible pane height.
Place the mouse cursor over the field names and scroll with the mouse wheel.

Actual behavior:

With the cursor over the field names, the pane flickers and jumps, and scrolling fails.
With the cursor on the right margin, next to the scrollbar (not over any field), wheel scrolling works correctly.
Dragging the scrollbar works correctly.
Tables whose field list fits in the pane are not affected.

It looks like the hover highlight (and the “…” button that appears on the hovered field) triggers a re-render that resets or interrupts the scroll position.

Expected behavior:
Smooth mouse-wheel scrolling regardless of where the cursor is inside the pane.

Already tried (no change):

Windows “Always show scrollbars” enabled, Power BI restarted
Changing report zoom and resizing the Data pane
Deselecting all visuals before scrolling

Workaround:
Scroll with the cursor on the right margin of the pane, or drag the scrollbar. I am attaching a screenshot for your review.

Thank you in advance

Power Query Editor window no longer states which file it relates to.

daniel96 — Mon, 19 Oct 2026 08:10:03 GMT

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

KongSutee — Sun, 18 Oct 2026 12:30:31 GMT

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

Data Pane flickers/jitters uncontrollably during mouse scroll

KongSutee — Sun, 18 Oct 2026 12:24:07 GMT

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