Issues Ideas

Input Slicer visual no longer correctly processes pasted multiline values

IoannisT — Fri, 14 Aug 2026 09:00:58 GMT

The Microsoft Input Slicer visual no longer correctly processes pasted multiline values.

Historically, users could copy a column of values from Excel and paste directly into the Input Slicer.

Each line would be interpreted as a separate value and applied as a multi-value filter.

The current behaviour converts line breaks into spaces, resulting in a single search string instead of multiple filter values.

Observations:

Issue reproduced using Notepad, therefore not related to Excel clipboard formatting.
The visual appears to replace carriage returns / line feeds with spaces before parsing the values.
Behaviour differs from previous functionality where bulk paste of multiple values was supported.

Environment:

Power BI Desktop: 2.156.951.0 (July 2026)
OS: Windows 11 (Build 26200)
Model Mode: DirectQuery
Input Slicer: Microsoft published visual

Impact:

Users can no longer efficiently paste lists of IDs, emails, personnel numbers, trade IDs, or other identifiers into the Input Slicer for ad-hoc analysis. Values must now be entered individually using Ctrl+Enter, which is impractical for larger lists.

FIX THE 'LINE GRAPH' VISUAL BUG IN LATEST VERSION OF POWER BI

markdean — Wed, 12 Aug 2026 06:48:18 GMT

Power BI Desktop 2.156.951.0 (July 2026) appears to have a bug in the standard built-in 'Line Chart' visual. Marker colour formatting is being ignored. Line colour updates correctly but markers continue to render using the default series colour. An example of the issue is highlighted below where we can see that the line graph markers should be displaying in matching pink, but the visual is failing to obey the instruction and is dispalying them in deafult blue instead.

Something went wrong

Aamir_Ali_SBP — Tue, 11 Aug 2026 10:35:49 GMT

I have exported my dashboard in PPT and the following error message appreas whenever try to open the file. Help me out to fix this.

Power BI Azure maps legend colours issue

H_TALIBART — Thu, 06 Aug 2026 10:26:26 GMT

Hello,

Azure Maps visual displays correct marker colours in Power BI Desktop (on the bottom). However, after publication, the legend colours shown in Power BI Service (on the top) do not match the manually configured data colours. The map rendering itself remains correct, but the generated legend uses a different colour palette and cannot be manually corrected within the Service.

It has been reported through several threads in the "Need Help" forum :

Power BI Azure map legend colour issues - Microsoft Fabric Community

Azure map legend colours incorrect in service - Microsoft Fabric Community

It has seriously impacted several of my dashboards, do we have any resolution timeline for this bug? thank you

Saul_Ring liz72

Unable to set default marker and line colours for line graphs

paulbodman — Mon, 03 Aug 2026 14:42:54 GMT

Both in desktop and service, even when creating new reports, setting a default 'all' category colour for markers and lines doesn't work. With markers, both in desktop and service, lines it works in desktop but defaults back to blue in service.

I don't want to have to set a colour for every month on my graph!

Make warnings more helpful

BryanD — Mon, 03 Aug 2026 12:56:24 GMT

"Object reference not set to an instance of an object" is a recurring issue in Power BI Desktop.
In other words: "There's a problem, but I'm not going to tell you where it is".
Rectifying the issue would be MUCH easier if Power BI would actually tell the user WHICH object refference is the problem!

Bookmark Bug after June Update?

AutoEder — Mon, 03 Aug 2026 09:58:46 GMT

Hey,

I noticed today that updating a bookmark seems to apply to all bookmarks, instead of just the one I selected. This started happening after I updated the client to the June version.

We have additional filters on our reports, that can be expanded with a button that triggers a bookmark. When I add an additional filter to the expansion, the filter shows up in every bookmark, including the one without the filter pane. We tried desktop and Power BI service with existing and brand new reports, none of it seems to work.

In this post the same bug is described after an update last year. The resolution was wating for the functionality to come back. Is anyone else having this issue?

Dynamic Subscription Sent Default Page instead of Report Page selected

weijingt — Mon, 03 Aug 2026 07:37:38 GMT

Hi,
My Power BI dashboard Dynamic Subscription is not working this month where it sent Default Page instead of Report Page selected. This is a monthly subscription and it is working fine last month. The subscription email received is with correct filter set but not the page selected, for example I set Page 2 but it give me Page 1 (the page I at when I saved and published).

I have "Set as landing page" unchecked.

Try recreate a new Dynamic subscription - not working.

Try recreate a new Standard subscription - working.

I google and cannot find a solution. Anyone with the same issue and found a solution?
By the way the "Include my changes" is missing for me, I not sure is my admin set that or PBI recent updates removed that.
Thanks in advance for any help~

Query changes won't apply to desktop

sclarkcfs — Fri, 31 Jul 2026 17:13:30 GMT

Feedback Type: Frown (Error) Timestamp: 2026-07-31T17:10:07.6000473Z Local Time: 2026-07-31T10:10:07.6000473-07:00 Session ID: b397d421-d902-480d-91b8-9fe88fd051e7 Release: July 2026 Product Version: 2.156.951.0 (26.07)+c9381f8e5efc99c8de04425f1572e841914690d8 (x64) Stack Trace: System.NullReferenceException at Microsoft.PowerBI.Modeling.Engine.DataModel.Utilities.DataModelAuthoringExtensions.GetCanRefreshData(ITable table) at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext() at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.RefreshData(IExtendedModelChangeScope modelChangeScope, IEnumerable`1 tablesToRefreshData) at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.<>c__DisplayClass28_0.b__0() at Microsoft.PowerBI.Modeling.Engine.Utilities.TransactionUtils.ExecuteInTransaction(IExtendedModelChangeScope modelChangeScope, Func`1 action, Boolean loadRequiresOutOfBandTransaction) at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.d__28.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.d__26.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.<>c__DisplayClass22_0.<b__4>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.<>c__DisplayClass22_0.<b__4>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<>c__DisplayClass12_0`1.<b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.d__11.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.d__12`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Modeling.Engine.Loader.LoadToReportFlow.d__15.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Modeling.Engine.Loader.LoadToReportFlow.d__10.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Modeling.Engine.Loader.LoadToReportFlow.d__9.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<>c__DisplayClass12_0`1.<b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.d__11.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.d__12`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.<>c__DisplayClass20_0`1.<b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBITelemetryServiceExtensions.<>c__DisplayClass6_0.<b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBITelemetryServiceExtensions.d__7`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBITelemetryServiceExtensions.d__6.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.d__21.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.d__19.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingTelemetryService.d__20`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.DesktopModelingHost.<>c__DisplayClass17_0.<b__3>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Modeling.Engine.Authoring.AsyncModelAuthoringService.<>c__DisplayClass10_0.<b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Modeling.Engine.Authoring.AsyncModelAuthoringService.d__13.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.DesktopModelingHost.d__17.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.PowerBI.Client.Windows.FloatingDialog.KoLoadToReportDialog.<>c__DisplayClass49_0.<b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.Mashup.Client.UI.Shared.IExceptionHandlerExtensions.d__1.MoveNext() PowerBINonFatalError: {"AppName":"PBIDesktop","AppVersion":"2.156.951.0","ModuleName":"Microsoft.PowerBI.Modeling.Engine.dll","Component":"Microsoft.PowerBI.Modeling.Engine.DataModel.Utilities.DataModelAuthoringExtensions","Error":"System.NullReferenceException","MethodDef":"GetCanRefreshData","ErrorOffset":"0","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: 88.7 GB Private Memory: 1.82 GB Peak Working Set: 1.85 GB IE Version: 11.1882.26100.0 User ID: 34492ac5-0b14-405d-b5f3-8943b02e1c0a Workbook Package Info: 1* - en-US, Query Groups: 10, fastCombine: Enabled, runBackgroundAnalysis: False. Telemetry Enabled: True Model Default Mode: Import Model Version: PowerBI_V3 Enabled Preview Features: PBI_DatabricksAdbcVersionEnabled PBI_scorecardVisual PBI_setLabelOnExportPdf PBI_oneDriveSave PBI_oneDriveShare PBI_useModernPublishDialogs PBI_gitIntegration PBI_tmdlInDataset PBI_enhancedReportFormat PBI_enhancedReportFormatPBIX PBI_advancedSlicerTypeList MashupFlight_EnableOracleBundledOdacProviderV2 PBI_sqlDbNativeArtifactsOnDesktop PBI_warehouseSnapshotArtifactsOnDesktop PBI_enableExportQueries PBI_DesktopNamedPipeBridge MashupFlight_EnableFirewallFlowsWithDataSources Disabled Preview Features: PBI_googleBigQueryAdbcVersionEnabled PBI_UseRedshiftODBCV2 PQ_UseBaseViewXmlForSharePoint PBI_snowflakeLegacyOdbcVersionEnabled PBI_SpanishLinguisticsEnabled PBI_qnaLiveConnect PBI_b2bExternalDatasetSharing PBI_onObject PBI_publishDialogsSupportSubfolders PBI_useModernMashupEditor PBI_aiNarrativesVisual PBI_customCalendars PBI_copilotUnifiedTooling PBI_enableOracleBundledOdacProviderForDQ PBI_dynamicCalcColumn PBI_newVisualDefaults2026 PBI_dateSlicerPreselectionAuthoring Disabled DirectQuery Options: TreatHanaAsRelationalSource Cloud: GlobalCloud DPI Scale: 125% Supported Services: Power BI WebView2 Runtime Version: 150.0.4078.105 WebView2 SDK Version: 1.0.2365.46

Allow report authors to disable or hide table right-click context menu options in Power BI Desktop

maruthisp — Fri, 31 Jul 2026 11:10:54 GMT

Hi Power BI Team,

I would like to request a new feature that allows report developers to disable or hide selected right-click context menu options on table and matrix visuals after publishing reports to Power BI Service.

Business reasons

This feature would help in reports where:

Users should only view the designed report experience
Include and Exclude create unexpected visual filters
Copy options are not appropriate for sensitive operational information
Show as a table exposes a different presentation from the approved report layout
Report owners need stricter control over user interaction
Reports are used in regulated, clinical, financial, or confidential environments
Administrators need a consistent interaction policy across reports

Important security note

This feature would not replace:
- Row-level security
- Object-level security
- Export restrictions
- Build-permission controls
- Tenant security settings
  It would provide better control over the report user experience and reduce unwanted or confusing interactions.
  
  Please consider adding this capability in a future Power BI Desktop and Power BI Service release.
  
  Thanks in advance.
  
  Best regards,
  Maruthi Siva Prasad
  http://www.linkedin.com/in/maruthi-siva-prasad/

Power BI Desktop (.pbip/TMDL) crashes on measure context menu — "Cannot read properties of undefined

GGCX — Thu, 30 Jul 2026 09:00:00 GMT

Hi,

When opening a Power BI report in .pbip format (Git-integrated project with TMDL), right-clicking on a measure in the field list causes an error: "An error occurred while rendering the report". The root cause is a JavaScript exception — Cannot read properties of undefined (reading 'capabilities') — thrown inside RenameDeleteMenuItemHandlers.capabilitiesCheck, which handles the rename/delete context menu logic. The same report works without issues when saved as .pbix. The problem appears to be specific to models using TMDL storage with the Enhanced Report Format preview features enabled (PBI_tmdlInDataset, PBI_enhancedReportFormat) in Power BI Desktop version 2.156.951.0 (July 2026).

Log trace below:

Feedback Type:
Frown (Error)

Timestamp:
2026-07-30T07:19:36.5501556Z

Local Time:
2026-07-30T09:19:36.5501556+02:00

Session ID:
6757d351-bc9a-440d-bbbb-b05fa3ba2fef

Release:
July 2026

Product Version:
2.156.951.0 (26.07)+c9381f8e5efc99c8de04425f1572e841914690d8 (x64)

PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.156.951.0","ModuleName":"https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js","Component":"","Error":"TypeError","MethodDef":"j","ErrorOffset":"1:11328572","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.8 GB

Private Memory:
676 MB

Peak Working Set:
869 MB

IE Version:
11.1882.26100.0

User ID:
773dc98c-b763-4862-b5e5-dc6b73c7793c

Workbook Package Info:
1* - da-DK, Query Groups: 4, fastCombine: Disabled, runBackgroundAnalysis: False.

Telemetry Enabled:
True

Model Default Mode:
Composite

Model Version:
PowerBI_V3

Enabled Preview Features:
PBI_DatabricksAdbcVersionEnabled
PBI_googleBigQueryAdbcVersionEnabled
PBI_scorecardVisual
PBI_setLabelOnExportPdf
PBI_oneDriveSave
PBI_oneDriveShare
PBI_useModernPublishDialogs
PBI_gitIntegration
PBI_tmdlInDataset
PBI_enhancedReportFormat
PBI_enhancedReportFormatPBIX
PBI_advancedSlicerTypeList
PBI_aiNarrativesVisual
PBI_copilotUnifiedTooling
MashupFlight_EnableOracleBundledOdacProviderV2
PBI_sqlDbNativeArtifactsOnDesktop
PBI_warehouseSnapshotArtifactsOnDesktop
PBI_enableExportQueries
PBI_DesktopNamedPipeBridge
MashupFlight_EnableFirewallFlowsWithDataSources

Disabled Preview Features:
PBI_UseRedshiftODBCV2
PQ_UseBaseViewXmlForSharePoint
PBI_snowflakeLegacyOdbcVersionEnabled
PBI_SpanishLinguisticsEnabled
PBI_qnaLiveConnect
PBI_b2bExternalDatasetSharing
PBI_onObject
PBI_publishDialogsSupportSubfolders
PBI_useModernMashupEditor
PBI_customCalendars
PBI_enableOracleBundledOdacProviderForDQ
PBI_dynamicCalcColumn
PBI_newVisualDefaults2026
PBI_dateSlicerPreselectionAuthoring

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

Recent Actions:
SetOutspacePaneContractWidth, SetOutspacePaneContractWidth, SetOutspacePaneContractWidth

DPI Scale:
100%

Supported Services:
Power BI

WebView2 Runtime Version:
150.0.4078.105

WebView2 SDK Version:
1.0.2365.46

PowerBI Online - Line/ Area Chart Issue after the July Update

theo_s — Wed, 29 Jul 2026 20:19:07 GMT

After the latest update I am having this this issue on the online version of PBI where if I have a single measure in the y axis and some category in x axis (for example months) I am not able to change the color of the line. The box is greyed out. I can do it month by month it doesnt allow me when "All" is selected.

When "All" is selected I get this message to select a series and color cannot be touched.

All this with a fresh new report, in a fresh workspace. If we go back to my actual report, I can work on it on the desktop version and change the colour normally but when I publish it defaults to blue. Older line charts remain with their colour before the update but on the online version they are locked"

Any help would be much appreciated.

Allow Table Visuals to Set or Preserve Column Header Height Across Horizontal Scrolling

yusukekamata — Wed, 29 Jul 2026 05:12:36 GMT

In Power BI table visuals, long column headers can be displayed in a vertical-like format by enabling text wrapping and setting narrow column widths.

However, when a table contains many columns and the long headers are outside the initially visible area, the column header height appears to be calculated only from the columns visible when the report is first rendered. After scrolling horizontally, the header height is not recalculated, causing long wrapped headers to be clipped.

Example scenario:

・Columns 1–20 use normal horizontal headers with custom widths.
・Columns 21 onward use narrow widths, such as 21–30 px, to display long Japanese headers vertically.
・Only columns 1–20 are visible when the report opens.
・After scrolling to columns 21 onward, the long headers are clipped because the header height remains unchanged.

Please add one or both of the following options:

・Allow users to set a fixed column header height.
・Calculate the column header height based on all columns, including columns outside the initially visible area.

This would improve usability for wide tables that contain a mix of normal and vertically wrapped column headers.

Unremovable Scroll Bars

AWE — Tue, 28 Jul 2026 16:07:38 GMT

Scroll bars that are impossible to remove seem to be appearing on page navigators, slicers, cards, etc. on Power BI Service.

This happened sometime July 24-26th.

Card Visual -> Reference ->Details -> Background - can't be set to "Blank" by "Reset to defaults"

_Airat_ — Sun, 26 Jul 2026 06:15:36 GMT

New Card Visual -> Reference label ->Details -> Background - can't be set to "Blank"
by clicking "Reset to defaults"

Slicer's drop-down list covers the Data pane

_Airat_ — Sun, 26 Jul 2026 06:09:12 GMT

Slicer's drop-down list covers the Data pane (relevant for June and July 2026)

Falha na atualização de dados

Isantiago59 — Fri, 24 Jul 2026 18:32:59 GMT

Feedback Type:
Frown (Error)

Timestamp:
2026-07-24T18:30:50.2843464Z

Local Time:
2026-07-24T15:30:50.2843464-03:00

Session ID:
73cda911-4678-4a85-9dd0-cc5ecb1ba040

Release:
July 2026

Product Version:
2.156.951.0 (26.07)+c9381f8e5efc99c8de04425f1572e841914690d8 (x64)

Stack Trace:
Microsoft.Mashup.Host.Document.SerializedException
em Microsoft.Mashup.Host.Document.Analysis.PackageDocumentAnalysisInfo.PackagePartitionAnalysisInfo.SetPreviewValue(EvaluationResult2`1 result, Func`1 getStaleSince, Func`1 getSampled)

PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.156.951.0","ModuleName":"","Component":"Microsoft.Mashup.Host.Document.Analysis.PackageDocumentAnalysisInfo.PackagePartitionAnalysisInfo","Error":"Microsoft.Mashup.Host.Document.SerializedException - Microsoft.Mashup.Host.Document.Evaluation.ErrorEvaluationResult","MethodDef":"SetPreviewValue","ErrorOffset":"","ErrorCode":""}

OS Version:
Microsoft Windows NT 10.0.26200.0 (x64 pt-BR)

CLR Version:
4.8 or later [Release Number = 533509]

Peak Virtual Memory:
88.4 GB

Private Memory:
1.44 GB

Peak Working Set:
1.2 GB

IE Version:
11.1882.26100.0

User ID:
4c23b2cc-dec1-4bc7-8965-d4ebf28d3307

Workbook Package Info:
1* - pt-BR, Query Groups: 2, fastCombine: Disabled, runBackgroundAnalysis: False.

Telemetry Enabled:
True

Model Default Mode:
Import

Model Version:
PowerBI_V3

Enabled Preview Features:
PBI_DatabricksAdbcVersionEnabled
PBI_googleBigQueryAdbcVersionEnabled
PBI_scorecardVisual
PBI_setLabelOnExportPdf
PBI_oneDriveSave
PBI_oneDriveShare
PBI_useModernPublishDialogs
PBI_gitIntegration
PBI_tmdlInDataset
PBI_enhancedReportFormat
PBI_enhancedReportFormatPBIX
PBI_advancedSlicerTypeList
PBI_useModernMashupEditor
PBI_aiNarrativesVisual
PBI_copilotUnifiedTooling
MashupFlight_EnableOracleBundledOdacProviderV2
PBI_sqlDbNativeArtifactsOnDesktop
PBI_warehouseSnapshotArtifactsOnDesktop
PBI_enableExportQueries
PBI_DesktopNamedPipeBridge
MashupFlight_EnableFirewallFlowsWithDataSources

Disabled Preview Features:
PBI_UseRedshiftODBCV2
PQ_UseBaseViewXmlForSharePoint
PBI_snowflakeLegacyOdbcVersionEnabled
PBI_SpanishLinguisticsEnabled
PBI_qnaLiveConnect
PBI_b2bExternalDatasetSharing
PBI_onObject
PBI_publishDialogsSupportSubfolders
PBI_customCalendars
PBI_enableOracleBundledOdacProviderForDQ
PBI_dynamicCalcColumn
PBI_newVisualDefaults2026
PBI_dateSlicerPreselectionAuthoring

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

DPI Scale:
125%

Supported Services:
Power BI

WebView2 Runtime Version:
150.0.4078.83

WebView2 SDK Version:
1.0.2365.46

Potential Microsoft Fabric Copy Job Issue – Incremental Column Detection with Snowflake

Chetanpanwar — Fri, 24 Jul 2026 18:03:33 GMT

While configuring an Incremental Column in a Microsoft Fabric Copy Job against a large Snowflake table/view, I noticed behavior that may be worth investigating by the Fabric engineering team.

Observation

Instead of appearing to retrieve the column metadata directly (similar to a SHOW COLUMNS or equivalent metadata query), the Copy Job seems to execute a query using something similar to:

SELECT ... LIMIT 10

On large or complex Snowflake views, this can take significantly longer than expected because the view may still need to be resolved before returning even a small number of rows.

Additionally, I observed that the request appears to hit a web request timeout of approximately 3.3 minutes while trying to detect the incremental column. As a result, the Incremental Column selector remains in a loading state and never completes.

Questions for the Microsoft Fabric Team

Is the Incremental Column detection intentionally based on sampling data (LIMIT 10) rather than retrieving metadata?
Would using Snowflake metadata APIs or SHOW COLUMNS provide a faster and more reliable experience?
Can the timeout for metadata discovery be increased or made configurable for large enterprise workloads?
Is this a known issue or something already planned for optimization?

If this behavior is expected, understanding the design would be very helpful. If not, it may be an opportunity to improve the user experience for customers working with large Snowflake datasets.

Has anyone else experienced similar behavior with Fabric Copy Jobs and Snowflake?

Database consistency checks (DBCC) failed while checking the string store. An error occurred while

AbrahamVR — Thu, 23 Jul 2026 21:00:14 GMT

Feedback Type:
Frown (Error)

Timestamp:
2026-07-23T20:49:22.7011654Z

Local Time:
2026-07-23T16:49:22.7011654-04:00

Session ID:
7986ca0c-2776-4cd0-bccf-766dc18a2943

Release:
June 2026

Product Version:
2.155.332.0 (26.06)+e0735f0c31a359322d616f9a18b1ce2cc5efa4e2 (x64)

Stack Trace:
Microsoft.PowerBI.Client.Windows.Storage.FileOpenException
at Microsoft.PowerBI.Client.Windows.Services.LocalAnalysisServicesDatabaseCreator.<CreateAnalysisServicesDatabaseAsyncImpl>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Services.AnalysisServicesDatabaseCreator.<CreateAnalysisServicesDatabaseAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Services.PowerBIPackagingService.<Open>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Services.BiPackageOperationHandler.<LoadArtifact>d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Services.CurrentArtifactManager.<>c__DisplayClass58_0.<<ExecuteAndHandleFileOpenErrors>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Telemetry.PowerBITelemetryServiceExtensions.<EmitStandardizedClientReportingEventWithDebugEvent>d__7`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Services.CurrentArtifactManager.<ExecuteAndHandleFileOpenErrors>d__58.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Services.CurrentArtifactManager.<>c__DisplayClass37_0.<<OpenArtifactAndSetAsCurrent>b__1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.<>c__DisplayClass19_0`1.<<BlockUIAndRun>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.WaitOnUIThreadForTaskCompletion[T](Task`1 task)
at Microsoft.PowerBI.Client.Windows.Services.UIBlockingService.BlockUIAndRun[T](Func`1 asyncMethod, PowerBIProgress progress, String activityId)
at Microsoft.PowerBI.Client.Windows.Services.CurrentArtifactManager.OpenArtifactAndSetAsCurrent(IPowerBIWindowService windowService, IPowerBIArtifact artifactToOpen, IExceptionHandler exceptionHandler, Nullable`1 entryPoint, ReloadFileOptions reloadFileOptions)
at Microsoft.PowerBI.Client.Windows.Services.FileOperationUIHandler.<ExecuteOpenAndApplyCore>d__54.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.Services.FileOperationUIHandler.<OpenFileInternal>d__52.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.PowerBI.Client.Windows.IExceptionHandlerExtensions.<HandleAwaitableAsyncExceptions>d__1.MoveNext()

PowerBINonFatalError:
{"AppName":"PBIDesktop","AppVersion":"2.155.332.0","ModuleName":"Microsoft.PowerBI.Client.Windows.dll","Component":"Microsoft.PowerBI.Client.Windows.Services.LocalAnalysisServicesDatabaseCreator+<CreateAnalysisServicesDatabaseAsyncImpl>d__9","Error":"Microsoft.PowerBI.Client.Windows.Storage.FileOpenException","MethodDef":"MoveNext - PFE_XM_DBCC_STRINGSTORE_CORRUPT,PFE_XM_ERROR_WHILE_PARALLEL_LOADING_IMBI_TABLE_DATA","ErrorOffset":"939","ErrorCode":"DataModelLoadFailed"}

InnerException0.Stack Trace:
at Microsoft.PowerBI.Modeler.TomExceptionExtensions.ThrowAsModelingASException(Exception ex)
at Microsoft.PowerBI.Modeling.Engine.TomServer.ExecuteAndWrapWithModelingException(Action action)
at Microsoft.PowerBI.Modeling.Engine.TomServer.EnsureConnectionAndExecuteAction(Action action, ITelemetryService telemetryService, String actionName)
at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesService.ImageLoadDatabaseFromStream(String databaseName, Stream abfStream, ITelemetryService telemetryService)
at Microsoft.PowerBI.Client.Windows.AnalysisServices.AnalysisServicesService.LoadDatabaseFromStream(Stream abfStream, DatabaseDocuments initialDocuments, Boolean connectImmediately)
at Microsoft.PowerBI.Client.Windows.Services.LocalAnalysisServicesDatabaseCreator.<CreateAnalysisServicesDatabaseAsyncImpl>d__9.MoveNext()

InnerException1.Stack Trace:
at Microsoft.AnalysisServices.XmlaClient.SendExecuteAndReadResponse(Boolean skipResults, Boolean throwIfError, Boolean useBinaryXml)
at Microsoft.AnalysisServices.XmlaClient.ImageLoad(String databaseName, String databaseId, Stream sourceDbStream, Boolean allowOverwrite, String readWriteMode)
at Microsoft.AnalysisServices.Core.Server.ImageLoad(ImageLoadInfo imageLoadInfo)
at Microsoft.PowerBI.Modeling.Engine.TomServer.<>c__DisplayClass37_0.<EnsureConnectionAndExecuteAction>b__0()
at Microsoft.PowerBI.Modeling.Engine.TomServer.ExecuteAndWrapWithModelingException(Action action)

OS Version:
Microsoft Windows NT 10.0.22631.0 (x64 en-US)

CLR Version:
4.8 or later [Release Number = 533320]

Peak Virtual Memory:
85.9 GB

Private Memory:
373 MB

Peak Working Set:
436 MB

IE Version:
11.1.22621.0

User ID:
6d98ce55-30f9-425b-92e7-0fbfd1bd96d1

Workbook Package Info:
1* - en-CA, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: False.

Telemetry Enabled:
True

Model Default Mode:
Empty

Model Version:
PowerBI_V3

Enabled Preview Features:
PBI_DatabricksAdbcVersionEnabled
PBI_googleBigQueryAdbcVersionEnabled
PBI_scorecardVisual
PBI_setLabelOnExportPdf
PBI_oneDriveSave
PBI_oneDriveShare
PBI_useModernPublishDialogs
PBI_gitIntegration
PBI_tmdlInDataset
PBI_enhancedReportFormat
PBI_advancedSlicerTypeList
PBI_aiNarrativesVisual
PBI_copilotUnifiedTooling
MashupFlight_EnableOracleBundledOdacProviderV2
PBI_sqlDbNativeArtifactsOnDesktop
PBI_warehouseSnapshotArtifactsOnDesktop
PBI_enableExportQueries

Disabled Preview Features:
PBI_UseRedshiftODBCV2
PQ_UseBaseViewXmlForSharePoint
PBI_snowflakeLegacyOdbcVersionEnabled
PBI_SpanishLinguisticsEnabled
PBI_qnaLiveConnect
PBI_b2bExternalDatasetSharing
PBI_onObject
PBI_publishDialogsSupportSubfolders
PBI_enhancedReportFormatPBIX
PBI_useModernMashupEditor
PBI_qnaImproveLsdlCopilot
PBI_customCalendars
PBI_enableOracleBundledOdacProviderForDQ
PBI_dynamicCalcColumn
PBI_newVisualDefaults2026
PBI_DesktopNamedPipeBridge
PBI_dateSlicerPreselectionAuthoring

Disabled DirectQuery Options:
TreatHanaAsRelationalSource

Cloud:
GlobalCloud

DPI Scale:
100%

Supported Services:
Power BI

WebView2 Runtime Version:
150.0.4078.83

WebView2 SDK Version:
1.0.2365.46

Add "One-Click Rollback" button after buggy updates for Gateway & Power BI Desktop

Gautam_Kumar01 — Thu, 23 Jul 2026 03:24:13 GMT

Problem:

Every 2-3 months Microsoft releases a new Gateway or Power BI Desktop update. But sometimes the update breaks critical things.
Example: Gateway version 3000.322.4 June 2026 update is causing intermittent refresh failures with DM_GWPipeline_Gateway_DataSourceAccessError for large datasets.
Right now if an update breaks production, we have to waste 4-5 hours finding the old installer, uninstalling, and reinstalling manually.

Impact:
1. Production reports go down
2. Business users can't get data
3. IT admins waste hours on rollback
4. No official way to go back to stable version

Suggested Solution:
Add a "Rollback to Previous Stable Version" button inside the Fabric Admin Portal and Power BI Desktop.
When a new update is installed, keep the last 2 versions saved. If something breaks, 1 click and it reverts back.
Just like Windows "Uninstall Updates" feature.

This will save hours for every company using Fabric and Gateway.

Issues Ideas

Input Slicer visual no longer correctly processes pasted multiline values

FIX THE 'LINE GRAPH' VISUAL BUG IN LATEST VERSION OF POWER BI

Something went wrong

Power BI Azure maps legend colours issue

Unable to set default marker and line colours for line graphs

Make warnings more helpful

Bookmark Bug after June Update?

Dynamic Subscription Sent Default Page instead of Report Page selected

Query changes won't apply to desktop

Allow report authors to disable or hide table right-click context menu options in Power BI Desktop

Business reasons

Important security note

Power BI Desktop (.pbip/TMDL) crashes on measure context menu — "Cannot read properties of undefined

PowerBI Online - Line/ Area Chart Issue after the July Update

Allow Table Visuals to Set or Preserve Column Header Height Across Horizontal Scrolling

Unremovable Scroll Bars

Card Visual -> Reference ->Details -> Background - can't be set to "Blank" by "Reset to defaults"

Slicer's drop-down list covers the Data pane

Falha na atualização de dados

Potential Microsoft Fabric Copy Job Issue – Incremental Column Detection with Snowflake

Database consistency checks (DBCC) failed while checking the string store. An error occurred while

Add "One-Click Rollback" button after buggy updates for Gateway & Power BI Desktop