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 problemsStop 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
Salesforce Reports Broken when Grouped
As far as I can tell there is no support in Service for grouping by date so as an attempted workaround I created a summary report in Salesforce (technically we use a force.com CRM) that had such grouping. I created a new dataset that imported the regular report and the grouped report and while all the fields are available on the regular report as expected, the only fields available on the grouped report are "Record Count" and "Sale: Net On" the latter of which is the date field used to create the groups in the Salesforce report. What additional information can I provide you to help troubleshoot this issue?
Dataflow Gen2 with SAP BW source cannot bind Lakehouse table
Issue Summary I found a reproducible issue in Microsoft Fabric Dataflow Gen2 when using SAP BW Application Server as the source and Lakehouse table as the destination. The Dataflow Gen2 can refresh successfully if the Lakehouse destination was already configured. However, when I try to open the destination settings and rebind the query to an existing Lakehouse table, the destination wizard fails with the error: Value should be defined This happens during the destination selection / binding step, not during data preview or refresh. Source Type SAP BW Application Server through Power Query / Dataflow Gen2. The query uses SAP BW cube functions such as: SapBusinessWarehouse.Cubes Cube.Transform Cube.ApplyParameter Cube.AddAndExpandDimensionColumn Cube.AttributeMemberProperty Cube.AddMeasureColumn Destination Microsoft Fabric Lakehouse table. The original load was created using the default Lakehouse destination and completed successfully. The Lakehouse table was created and refresh worked. Later, I tried to change/rebind the destination manually to the same existing Lakehouse table and change the loading method from Replace to Append. At that point, the destination wizard failed with: Value should be defined Important Finding I tested the same destination behavior with other sources: Source Rebind to existing Lakehouse table SharePoint Excel Works Table from another Dataflow Works SAP BW source Fails This suggests the problem is not caused by Lakehouse permission, workspace permission, table existence, or the destination wizard in general. The issue appears to be specific to SAP BW source metadata / Cube.Transform schema validation during Dataflow Gen2 destination binding. Reproduction Steps Create a Dataflow Gen2 in Microsoft Fabric. Use SAP BW Application Server as the source. Build a query using SAP BW cube functions such as SapBusinessWarehouse.Cubes and Cube.Transform. Configure a Lakehouse table as the destination. Run the dataflow. The first refresh completes successfully. Reopen the Dataflow Gen2. Open the Data destination settings. Select manual/custom destination. Choose an existing Lakehouse table. The wizard fails with: Value should be defined Expected Result The destination wizard should allow selecting an existing Lakehouse table and saving the destination mapping. It should support normal destination configuration such as Replace or Append, the same way it works for SharePoint Excel or another Dataflow table source. Actual Result The destination wizard fails before the mapping can be saved. The dataflow itself can still refresh if the previous destination configuration already exists, but I cannot safely rebind or modify the destination settings. Business Impact This blocks production setup for SAP BW ingestion into Fabric Lakehouse. We need to load SAP BW data incrementally into Lakehouse, but cannot reliably configure an existing Lakehouse table destination with Append mode using Dataflow Gen2 when the source is SAP BW. Current Workaround Use Dataflow Gen2 only to extract SAP BW data into a staging Lakehouse table with Replace mode. Then use a Fabric Notebook or SQL process to load data into the final table, for example: SAP BW ↓ Dataflow Gen2 ↓ Lakehouse staging table - Replace ↓ Notebook / SQL delete-insert or merge ↓ Final Lakehouse Delta table This avoids relying on Dataflow Gen2 existing-table destination rebinding for SAP BW queries. Request Please investigate whether this is a known Dataflow Gen2 issue with SAP BW source queries and Lakehouse destination binding. Specifically, please check whether Dataflow Gen2 has a bug or limitation when resolving schema metadata from SAP BW / Cube.Transform queries during existing Lakehouse table selection. Error Details Error message: Value should be defined Session ID from error dialog: ee47c976-888c-408f-ab30-60d3245b00f6 Environment Product: Microsoft Fabric Feature: Dataflow Gen2 Source: SAP BW Application Server Destination: Fabric Lakehouse table Issue area: Data destination / existing Lakehouse table binding
Template App "Microsoft 365 Usage Analytics" failing with 500 Internal Service Error and 404
The 'Microsoft 365 Usage Analytics' template app has been failing since the 8th of May giving "DataSource.Error: Microsoft.Mashup.Engine1.Library.Resources.HttpResource: Request failed: OData Version: 4, Error: The remote server returned an error: (500) Internal Server Error. OData Version: 3, Error: The remote server returned an error: (500) Internal Server Error.. Microsoft.Data.Mashup.ErrorCode = 10122. Microsoft.Data.Mashup.ValueError.DataSourceKind = OData. DataSourcePath = https://reports.office.com/pbi/v1.0/556f4662-c7de-4312-9a81-dd4e68521c32. . The exception was raised by the IDbCommand interface." When trying to authenticate I get: "Failed to update data source credentials: Microsoft.Mashup.Engine1.Library.Resources.HttpResource: Request failed: OData Version: 3 and 4, Error: The remote server returned an error: (500) Internal Server Error. OData Version: 4, Error: The remote server returned an error: (500) Internal Server Error. OData Version: 3, Error: The remote server returned an error: (404) Not Found. (Not Found)" This suggests to me that something has changed on the Microsoft side. The template app itself feels a little out of date already but our business does find some of its output very useful. The template app did receive some updates back in Feb, so not abandoned by Microsoft.
Issues with visual by MAQ
Feedback Type: Frown (Error) Timestamp: 2026-03-11T16:37:36.8361563Z Local Time: 2026-03-11T10:37:36.8361563-06:00 Session ID: 93e66753-b605-4be4-afa7-41028e7a76bc Release: February 2026 Product Version: 2.151.1182.0 (26.02)+b81be254f3450e536a43f73a9777be8307916ef0 (x64) Stack Trace: Javascript:TypeError at SandboxDelegate.persistProperties (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:3036206) at SandboxVisualProxy.onMessageReceived (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:12686173) at https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:12681723 at MessageChannelProxy.invokeHandler (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:2854412) at MessageChannelProxy.dispatchMessage (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:2854294) at MessageChannelProxy.onMessageReceived (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:2853959) at e.source._peerWindow._peerOrigin.e.origin._peerOrigin.e.data.type.e.data.nonce._handshakeNonce._peerPort.onmessage (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:2852283) PowerBINonFatalError: {"AppName":"PBIDesktop","AppVersion":"2.151.1182.0","ModuleName":"https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js","Component":"SandboxDelegate","Error":"TypeError","MethodDef":"persistProperties","ErrorOffset":"1:3036206","ErrorCode":""} OS Version: Microsoft Windows NT 10.0.19045.0 (x64 en-US) CLR Version: 4.8 or later [Release Number = 528372] Peak Virtual Memory: 88.4 GB Private Memory: 908 MB Peak Working Set: 1.21 GB IE Version: 11.3636.19041.0 User ID: 2a8c7e0f-5813-447c-b39f-ee48633227ba Workbook Package Info: 1* - es-MX, Query Groups: 23, 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_odspSaveBackgroundUpload PBI_modernOfficeFilePicker PBI_useModernPublishDialogs PBI_gitIntegration PBI_tmdlInDataset PBI_enhancedReportFormat PBI_directLakeOnOneLake PBI_advancedSlicerTypeList PBI_aiNarrativesVisual PBI_visualCalculationsAuthoring PBI_copilotUnifiedTooling PBI_sqlDbNativeArtifactsOnDesktop PBI_dataFunctionActions PBI_enableExportQueries Disabled Preview Features: PBI_snowflakeLegacyOdbcVersionEnabled PBI_shapeMapVisualEnabled PBI_SpanishLinguisticsEnabled PBI_qnaLiveConnect PBI_b2bExternalDatasetSharing PBI_onObject PBI_publishDialogsSupportSubfolders PBI_enhancedReportFormatPBIX PBI_qnaImproveLsdlCopilot PBI_customCalendars PBI_UserInstalledNetezzaODBCDriver MashupFlight_EnableOracleBundledOdacProviderV2 PBI_supportUDFs Disabled DirectQuery Options: TreatHanaAsRelationalSource Cloud: GlobalCloud Recent Actions: RenameNavigationTab, RenameNavigationTab, RenameNavigationTab, RenameNavigationTab, RenameNavigationTab, RenameNavigationTab, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties DPI Scale: 150% Supported Services: Power BI WebView2 Runtime Version: 145.0.3800.97 WebView2 SDK Version: 1.0.2365.46Visual gallery / build tab not showing visuals and mismatched names
Checked on PBI Desktop Version: 2.151.1182.0 64-bit (February 2026), but also appearing in previous January 2026 versions. When opening a new report or an existing report not all visuals are displaying in the Visual Gallery section in the Home page, but also not showing in the Data tab on right hand side. Some visuals do not display, such as the card visual, unless you click on the three dots and select "Restore default visuals". This must be done even on a fresh opened instance of PBI desktop with nothing else done other than open. Before Restore button click After Restore button click (clearly more visuals showing) Also since the new change to Text Visual, there appears to be a mismatch of Name values - in Build this is named "List Slicer (Preview)" and "Input Slicer" but in the Insert visual window on Home page this is displayed as "Text Slicer (Preview)", so mismatch of names to icon.Error graphic service
Feedback Type: Frown (Error) Timestamp: 2026-02-24T02:13:31.3476523Z Local Time: 2026-02-24T05:13:31.3476523+03:00 Session ID: 613a9f31-8f08-49aa-ae36-1979a8a5a293 Release: February 2026 Product Version: 2.151.1052.0 (26.02)+f24ef72a680490da641de392ea586cef1b10bfc8 (x64) Stack Trace: Microsoft.PowerBI.Common.DependencyInjection.DependencyInjectionResolutionFailedException at Microsoft.PowerBI.Common.DependencyInjection.ClassProvider.CreateInstance(Type type, ResolveContext context) at Microsoft.PowerBI.Common.DependencyInjection.ClassProvider.GetValue(ResolveContext context) at Microsoft.PowerBI.Common.DependencyInjection.Provider.Resolve(ResolveContext context) at Microsoft.PowerBI.Common.DependencyInjection.Provider.Resolve(ResolveContext context) at Microsoft.PowerBI.Common.DependencyInjection.ClassProvider.Construct(Type type, ConstructorInfo constructor, ResolveContext context) at Microsoft.PowerBI.Common.DependencyInjection.ClassProvider.CreateInstance(Type type, ResolveContext context) at Microsoft.PowerBI.Common.DependencyInjection.ClassProvider.GetValue(ResolveContext context) at Microsoft.PowerBI.Common.DependencyInjection.Provider.Resolve(ResolveContext context) at Microsoft.PowerBI.Common.DependencyInjection.DependencyInjectionContainer.Resolve[T](String name) at Microsoft.PowerBI.Client.Windows.ExploreHost.MinervaInteropHost.RegisterService[T](Func`1 factory) at Microsoft.PowerBI.Client.Windows.HtmlControls.ReportView.MinervaInterop.ReportViewInteropHost..ctor(IBrowserWrapper browserWrapper, IReportViewClientHost reportViewClientHost, IHostedScriptAsync hostedScript, IExceptionHandler exceptionHandler) at Microsoft.PowerBI.Client.Windows.ReportViewClientHost..ctor(IBrowserWrapper browserWrapper, IExceptionHandler exceptionHandler, IPowerBIWindowService windowService, IEventAggregationService eventAggregationService, SynchronizationContext synchronizationContext, IFeatureSwitchManager featureSwitchManager, IPowerBITelemetryService telemetryService, IPowerBISettings powerBISettings, IUIBlockingService uiBlockingService, IApplicationCommands applicationCommands, IWebView2VersionUtils webView2VersionUtils) at Microsoft.PowerBI.Client.Windows.Views.ReportView.get_ReportViewClientHost() at Microsoft.PowerBI.Client.Windows.Views.ReportView.Dispose() at Microsoft.PowerBI.Client.Windows.MainForm.Dispose(Boolean disposing) at System.ComponentModel.Component.Dispose() 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) PowerBINonFatalError: {"AppName":"PBIDesktop","AppVersion":"2.151.1052.0","ModuleName":"Microsoft.Graph.Core.dll","Component":"Microsoft.Graph.Serializer","Error":"System.IO.FileLoadException","MethodDef":".ctor","ErrorOffset":"-1","ErrorCode":""} InnerException0.Stack Trace: at Microsoft.Graph.Serializer..ctor() at Microsoft.PowerBI.Client.Windows.GraphService.GraphServiceClientFactory.CreateGraphServiceClient(String graphEndpoint, IAuthenticationProvider authenticationProvider) at Microsoft.PowerBI.Client.Windows.GraphService.GraphServiceClient..ctor(ICloudConfigurationManager cloudConfigurationManager, IAccessTokenProvider accessTokenProvider, IPowerBITelemetryService telemetryService, IEventAggregationService eventAggregationService, IAuthenticationManager authenticationManager, IGraphServiceClientFactory graphServiceClientFactory) 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 GB Private Memory: 186 MB Peak Working Set: 327 MB IE Version: 11.1882.26100.0 User ID: e588ec6a-4499-4ebd-bfd2-e4a9885d87a0 Telemetry Enabled: True DPI Scale: 125% Supported Services: Power BIRestore full control over number formatting in the new Card visual (disable automatic abbreviation)
The new Card visual in Power BI forces automatic number abbreviation (e.g., “2K”, “2 Mil”, “1.5M”), even when the measure has a custom format string applied (such as #,0, #.##0, or full currency formatting). There is currently no reliable way to disable this behavior, as the “Display Units = None” option is missing or inconsistent in the new Card visual. This creates several issues: • Reports cannot display full numeric values anymore (e.g., “1,783” or “2,149,125.00”). • The visual overrides the user’s chosen formatting, breaking existing reports. • Workarounds require converting numeric values to text using FORMAT(), which negatively impacts sorting, performance, and downstream calculations. • This is a regression compared to the old Card visual, which allowed full control over number format. Please restore the ability to disable automatic number abbreviation in the new Card visual, or ensure that the visual consistently respects the model’s numeric format string without forcing K/M/B scaling. Having full formatting control is essential for many business scenarios where exact numbers must be displayed without abbreviations. Thank you.
