Hi all, I’m seeing a sudden Power BI Desktop refresh failure with Snowflake-backed Power Query tables. Has anyone else seen this with recent Power BI Desktop / Snowflake connector builds? Is there a known regression or recommended workaround? Power BI Desktop version: 2.155.756.0 Install type: Microsoft Store app Connector: native Snowflake connector Pattern: Snowflake queries fail in Desktop, but the same SQL runs successfully in Snowflake and the dataset/report still refreshes in Power BI Service. Representative M pattern: let Source = Value.NativeQuery( Snowflake.Databases( "<snowflake_account>", "<warehouse>", [Implementation="2.0"] ){[Name="<database>"]}[Data], "<native SQL query against a Snowflake view>", null, [EnableFolding=true] ) in Source Desktop refresh error: cannot convert the value null to type Text.   Things already tried: Restarted machine Uninstalled/reinstalled Power BI Desktop Cleared/re-authenticated data source credentials Removed [Implementation="2.0"] Removed [EnableFolding=true] Replaced select * with explicit column casts Tested multiple Snowflake queries/tables ... View more

Hi we are currently experiencing this issue on June update of Pbi - error message: Sequence contains more than one element. Data source SAP business app server, direct query. All reports are not working. Also unable to create new ones. Any idea what went wrong? On SAP side there were no changes.   Feedback Type: Frown (Error) Timestamp: 2026-06-15T13:34:11.4197245Z Local Time: 2026-06-15T15:34:11.4197245+02:00 Session ID: 02a75b59-23ab-4021-b050-d811b24249da Release: June 2026 Product Version: 2.155.756.0 (26.06)+7f1da5803bfe48beff98093405280405ddb467dd (x64) Stack Trace: System.InvalidOperationException at System.Linq.Enumerable.SingleOrDefault[TSource](IEnumerable`1 source) at Microsoft.PowerBI.Modeling.Engine.DataModel.Utilities.DataModelExtensions.GetCubeDataSourceType(INamedExpression namedExpression) at Microsoft.PowerBI.Modeling.Engine.Query.ModelingMashupDocumentGenerator.BuildQuery(IQueryableObject obj, IModelingQueryBuilder queryBuilder, IEnumerable`1 queryGroups, TwoWayDictionary`2 modelObjectNameToRuntimeIdMap) at Microsoft.PowerBI.Modeling.Engine.Query.ModelingMashupDocumentGenerator.BuildQueries(IDataModel dataModel, IModelingMashupDocumentBuilder mDocumentBuilder, TwoWayDictionary`2 modelObjectNameToRuntimeIdMap) at Microsoft.PowerBI.Modeling.Engine.Query.ModelingMashupDocumentGenerator.GenerateQueriesFromModel(IDataModel dataModel, IModelingMashupDocumentBuilder mDocumentBuilder, TwoWayDictionary`2 modelObjectNameToRuntimeIdMap) at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingQueriesGenerator.GenerateRestorationInputFromModel(IDataModel dataModel, IMashupDiscoveryService mashupDiscoveryService) at Microsoft.PowerBI.Client.Windows.Modeling.Hosting.ModelingQueriesGenerator.GenerateAndRestoreQueriesFromModel(Report report, IDataModel dataModel, Boolean restoreQueriesToReport) at Microsoft.PowerBI.Client.Windows.Services.ReportFactory.<SetAnalysisServicesDatabaseToReport>d__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.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.CommandLineFileService.TryOpenOrCreateReport(IPowerBIWindowService windowService, IExceptionHandler exceptionHandler, Boolean forceCreate) at Microsoft.PowerBI.Client.AppReportFlow.<OpenExistingReport>d__50.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at Microsoft.PowerBI.Client.AppReportFlow.<OpenExistingReport>d__50.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.AppReportFlow.<ContinueLoadWithMainWindow>d__43.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.AppModule.<>c__DisplayClass4_2.<<Run>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.MainWindow.<<ActivateMainWindow>b__41_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.IExceptionHandlerExtensions.<HandleAwaitableAsyncExceptions>d__1.MoveNext() PowerBINonFatalError: {"AppName":"PBIDesktop","AppVersion":"2.155.756.0","ModuleName":"Microsoft.PowerBI.Modeling.Engine.dll","Component":"Microsoft.PowerBI.Modeling.Engine.DataModel.Utilities.DataModelExtensions","Error":"System.InvalidOperationException","MethodDef":"GetCubeDataSourceType","ErrorOffset":"32","ErrorCode":""} OS Version: Microsoft Windows NT 10.0.26200.0 (x64 cs-CZ) CLR Version: 4.8 or later [Release Number = 533509] Peak Virtual Memory: 85.8 GB Private Memory: 296 MB Peak Working Set: 425 MB IE Version: 11.1882.26100.0 User ID: 8076080c-4640-48db-9342-e6360ebde53c Workbook Package Info: 1* - cs-CZ, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: False. Telemetry Enabled: True Model Default Mode: Empty Model Version: PowerBI_V3 Disabled Preview Features: PBI_DatabricksAdbcVersionEnabled PBI_googleBigQueryAdbcVersionEnabled PBI_UseRedshiftODBCV2 PQ_UseBaseViewXmlForSharePoint PBI_snowflakeLegacyOdbcVersionEnabled PBI_SpanishLinguisticsEnabled PBI_qnaLiveConnect PBI_b2bExternalDatasetSharing PBI_scorecardVisual PBI_onObject PBI_setLabelOnExportPdf PBI_oneDriveSave PBI_oneDriveShare PBI_useModernPublishDialogs PBI_publishDialogsSupportSubfolders PBI_gitIntegration PBI_tmdlInDataset PBI_enhancedReportFormat PBI_enhancedReportFormatPBIX PBI_advancedSlicerTypeList PBI_useModernMashupEditor PBI_aiNarrativesVisual PBI_customCalendars PBI_copilotUnifiedTooling MashupFlight_EnableOracleBundledOdacProviderV2 PBI_enableOracleBundledOdacProviderForDQ PBI_sqlDbNativeArtifactsOnDesktop PBI_warehouseSnapshotArtifactsOnDesktop PBI_dynamicCalcColumn PBI_newVisualDefaults2026 PBI_enableExportQueries PBI_DesktopNamedPipeBridge PBI_dateSlicerPreselectionAuthoring Disabled DirectQuery Options: TreatHanaAsRelationalSource Cloud: GlobalCloud DPI Scale: 150% Supported Services: Power BI WebView2 Runtime Version: 149.0.4022.69 WebView2 SDK Version: 1.0.2365.46 ... View more

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 ... View more

Microsoft Fabric down?   Localization: Europe   Can anyone confirm ? ... View more

Dear MS Power BI Team,   Since ± the beginning of October 2025, I have noticed an issue that the "Grid" type of Arrangement is broken on the service side:   Expected: in case of having 4 columns out of 6, an extra space on the right side left for 2 empty columns     Once published to the service side, the buttons stretch across the entire width, same way as behave "Horizontal" type of arrangement:     Can you please pay attention to this service side issue and fix?   regards, Alena ... View more

I am reporting a issue in the Input Slicer visual performance specifically within the Power BI Service (Web). This issue does not occur in Power BI Desktop.  Cursor Jump: When typing a value into the input box, the cursor automatically jumps to position 0 (the front of the text) after a single character is entered. This prevents me from entering multiple value (FYI: accept multiple value is toggled on). Unable to Delete: Values entered into the slicer cannot be cleared or deleted using the "X" keys. Kindly advise.    ... View more

I have an issue where the “new card” visual layout becomes misaligned / messy after publishing to Power BI Service, even though everything looks neat and properly aligned in my PBI local (desktop).     PBI Desktop         PBI Services   is there anyone have same issue guys? ... View more

I created  .pbip file, everything worked well; Suddenly yesterday something changed - it can be worked on and saved; however, the second I close file and try to reopen it. or try to publish the pbip, or sync workspace with git branch - it returns this error: 'pages/4dbd8244539262a7c568/visuals/e7c9a06c5e6a8566ddbe/visual.json': Property 'showActionsInTooltips' has not been defined and the schema does not allow additional properties. Path 'visual.visualContainerObjects.visualTooltip[0].properties.showActionsInTooltips' I tried to google this, but i think this Action in Tooltips feature is too new to be reported anywhere yet. I am wondering if it's only me experiencing this issue... or it's a common "bug"? ... View more

Issue Description We are experiencing an issue with Text Input Slicers in Power BI Service where the slicer value does not reset when using bookmarks or the Clear All Slicers option. Observed Behavior A user types a value into a Text Input Slicer (e.g., MRN). Clicking a Reset/Clear bookmark visually clears the slicer. When the user interacts with the slicer again, the previously typed value automatically reappears. This behavior occurs only in Power BI Service. The same report works correctly in Power BI Desktop. Expected Behavior Text Input Slicer values should fully reset when a reset bookmark or Clear All action is applied. After reset, the slicer should not retain or reapply previously typed values. Additional Notes This issue affects all reports using text-based slicers (e.g., MRN, Account Number). Dropdown slicers work as expected and reset correctly. This behavior appears to have started after a recent Microsoft Fabric / Power BI Service update. The issue is not related to report design, bookmark configuration, or persistent filter settings. Business Impact Prevents reliable Reset Filters functionality. Causes user confusion when old values reappear. Forces redesign of production reports to avoid text input slicers. Current Workaround Replace Text Input Slicers with Dropdown slicers, which reset correctly. Request for Clarification Could someone from the Power BI / Fabric product team please confirm whether this behavior is by design or a known issue planned to be addressed? This impacts multiple production reports and is forcing us to replace text input slicers with dropdowns. Understanding whether a fix or configuration option is planned would help us decide whether to wait for a resolution or permanently redesign our reports. ... View more

Hi everyone,   I noticed a possible issue in Power BI Desktop 2.150.1926.0 64-bit (January 2026), Report Server version.   In one of my PBIX files, I have a filter set under “Filters on all pages”. The filter is applied correctly at first and still affects the report. However, after hiding and showing the filter pane again, or collapsing and expanding it, the filter is no longer visible in the filter pane.   The filter still seems to be active, but I cannot see or change it anymore in the UI.   So far, I have only seen this behavior in this specific .pbix file/report and I have not been able to reproduce it in a new or different file. Filters on visuals and filters on this page are not affected.   I attached screenshots showing the filter before and after it disappears from the pane.   Has anyone experienced something similar, or is there a known issue or workaround for this? Set Filter:   Collapsing:   Expanding:   ... View more

Hi guys,   Our power bi semantic models are not refreshing when we use the on-demand option.   This night scheduled refreshes have been working properly.   Thanks a lot for your help. ... View more

Location: North Europe Publised Reports not loading at all - only blank pages.   Would be lovely if Microsoft would update the service status if this is a widespread issue. I am being run down by colleagues now.   Thanks ... View more

I could not import the data from Google Analytics due to this error:   The data still get updated in Edit query but I could not load it to my report. How can I fix this?   ... View more

Data source error: {"error":{"code":"Premium_ASWL_Error","pbi.error":{"code":"Premium_ASWL_Error","parameters":{},"details":[{"code":"Premium_ASWL_Error_Details_Label","detail":{"type":1,"value":"Refresh is not supported for datasets with a calculated table or calculated column that depends on a table which references Analysis Services using DirectQuery."}}],"exceptionCulprit":1}}} Cluster URI: WABI-SOUTH-CENTRAL-US-redirect.analysis.windows.net Activity ID: 954fd614-029c-451f-ab77-aac648a599e3 Request ID: 02fb20e5-43e4-376e-ccc8-b07440f335f0 Time: 2023-01-12 10:31:06Z ... View more

When exporting a report as an image to PPT (or to PDF), there is an option to export with default values or with the current selection. No matter what I try, the export is always with the default values. This is for all reports that we currently have online. This issue was previously raised  last year and a fix was issued, but it has recently stopped working again. Export to PDF or PPT always takes default values  Thanks ... View more

Hi all,   I exported report to PPT and there is now a page number in the report 21 of 25, etc. I don't want this in the PPT report and there is no way to remove it. Then i had to mannually remove the page number from all the page which is so annoying.    Please advise how to remove/turn off this unnecessary feature.     Thanks ... View more

Dear Colleagues,  I faced an issue that Bookmarks with new Button Slicer are broken after deploying through Power BI Deployment Pipeline. Steps:  1. A Bookmark is saved in Power BI Desktop and works as expected after publishing to Dev env: #1, #3 and #4 New Button Slicer visuals are selected (light blue color): 2. After deploying to Test env I can see that for the same bookmark, there are only #1 and #4 selected, #3 is not selected: 3. After deploying to Prod env I can see sometimes the expected behaviour: #1, #3 and #4 are selected, but sometimes it shows #1 and #3, but #4 is not selected.   It is really strange and unstable. As it didn't happen before with the old type of visuals, I can assume that this issue is related to the new Button slicer visual.  Please help ASAP as it affects production!  P.S. Please advise if there is any workaround to temporarily fix this issue until the permanent fix.  ... View more