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

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

Hi Microsoft Fabric Community, Issue Summary Input slicers in public/Publish to Web links now freeze/block the browser tab when interacted with. This new problem began yesterday (April 24, 2026) after recent Service updates. Steps to Reproduce Create report with Input Slicer (Feb 2026 feature) on text/date field. Publish to web/public embed. Open link in Chrome/Edge new tab. Type/select in input slicer → tab freezes (unresponsive, high CPU). Environment Power BI Desktop: Works fine. Power BI Service/Public link: Fails (tab blocked). Browser: Chrome/Edge (latest), occurs consistently. No custom visuals; standard input slicer only. https://app.powerbi.com/view?r=eyJrIjoiNzM1MzRmODgtMjkwYi00MjRmLTljYWQtYThhZDcwMzdmMzZhIiwidCI6IjMxZjEzM2ZhLTRiODMtNDUwMi05NzNjLTcxMDdiZDY0ZTgwNyJ9  ... View more

Hi all, I’m seeing recently a recurring issue in Power BI Desktop where a brief CMD window appears during report load and sometimes during semantic model-related changes. After digging into it, I found that the CMD window is actually SQLDUMPER.EXE. From what I understand, SQLDUMPER.EXE is a Microsoft diagnostic utility that gets triggered when an internal Microsoft component crashes or throws an exception. In this case, the actions seem to be tied to msmdsrv.exe, which is the backend model/query engine used by Power BI Desktop. What the issue looks like The black CMD window appears briefly. It first happens while the report is opening, specifically during “Preparing report”. It can also happen later when making changes that affect the semantic model, for example renaming a field or making other model-related modifications. The issue does not seem to be a simple visual/UI problem. It looks more like the backend model engine is hitting an exception and SQLDUMPER is collecting a dump. My troubleshooting so far Confirmed the CMD window is SQLDUMPER.EXE Using process monitoring, I confirmed that the CMD window is SQLDUMPER.EXE. Looking deeper, the process triggering it appears to be msmdsrv.exe, which is the Analysis Services/model engine running behind Power BI Desktop. No issue with a PBIX that has no external file connection In my tests, the issue does not appear when the PBIX contains only embedded data and no external data source connection to a file. You can simulate it just entering a dummy data using "Enter Data" in power bi. Issue will not happen on those reports. Happens in both Store version and downloaded version I tested both: the Microsoft Store/App version the downloaded installer version The issue happens in both. Preview features do not seem to be the root cause Turning off some preview features, such as On-object interaction, seemed to reduce the frequency somewhat, possibly because they trigger semantic model changes more often. However, this did not solve the issue completely, so I do not think this is purely a preview feature problem. Cache clearing and fresh install did not fix it I tried: clearing cache fresh installation switching to the downloaded version None of these resolved the problem. Running Power BI as Administrator prevents the issue While investigating logs, I noticed some apparent file access-related problems involving msmdsrv.exe. That led me to try Run as administrator. When I ran Power BI Desktop as Administrator, the issue did not appear. I even turned all preview features back on and tested again as Administrator, and it still did not happen. Moving the PBIX to a simple local folder did not help I also moved the report to a simple folder path such as: C:\test. This did not solve the issue. Current conclusion So far, on my machine, the only thing that prevents the issue is running Power BI Desktop as Administrator, which is obviously not a real solution. At this point, I suspect this may be one of the following: a Power BI Desktop bug a permissions / file access / credential issue something related to external data source connections possibly some interaction between the local Analysis Services engine (msmdsrv.exe) and file-based external sources Main questions Is anyone else seeing SQLDUMPER.exe appear during “Preparing report” or during semantic model changes? Has anyone identified the exact trigger? Has Microsoft acknowledged this anywhere? Is there any proper fix besides running Power BI as Administrator? Thanks in advance. I’m sharing this in case it helps others narrow down the issue. ... View more

I am unable to find or access the new "Set as landing page" feature in Power BI, despite having the latest software version installed. The option does not appear anywhere in the UI (neither by right-clicking the page tabs nor under the "Page information" format pane).   ... View more

Since updating to the March 2026 version of Power BI Desktop, I am unable to connect to a specific Tabular model on Azure Analysis Services (AAS). Error Message: "The connection failed. An error occurred while trying to connect. Details: Could not connect to the Analysis Services server because the connection timed out or the server name is incorrect.". Key Findings: Regression: The connection works perfectly with the November 2025 version of Power BI Desktop on the same machine and with the same credentials/network. Specific Context: The issue occurs only with one specific Tabular model, while others remain accessible. Community Feedback: Other users and clients have reported similar connectivity issues specifically with the latest March 2026 update. Steps to Reproduce: Open Power BI Desktop (March 2026 version). Select "Get Data" > "Azure Analysis Services database". Enter Server and Database name (Connect Live). Error appears after a short attempt. Environment Details: Current PBI Desktop Version: 2.151.1182.0 Previous Working Version: November 2025 Data Source: Azure Analysis Services (Tabular) Authentication: Azure Active Directory - Universal with MFA ... View more

Regardless of desktop appearance selection (dark, legacy, light, system default) the top three icons on the left nav (Report view, Table view and model view) are now rendered solid black.  Has anyone seen this? The icons are functional, just solid black.  Pretty sure this showed up just today; repaired the install to no effect. - Using November 2025 Release.       ... View more

Issue Summary The On-premises Data Gateway version 3000.314.5 (released April 27, 2026) fails to install on Virtual Machines without GPU acceleration. The previous version 3000.310.1 installs correctly on the same environment with a workaround.   Environment OS: Windows Server 2019 Standard (Build 17763.8644) Machine type: Virtual Machine (no GPU acceleration) .NET Framework: 4.8 (Release 528049) WebView2 Runtime: 147.0.3912.86 Visual C++ Redistributable: 14.44.35211 Gateway version failing: 3000.314.5 Gateway version working: 3000.306   Steps to Reproduce Provision a Windows Server 2019 VM without GPU acceleration Download and run the Gateway installer version 3000.314.5 Observe the installation failing at the service start step   Error Details From Windows Event Log: Application: Microsoft.Mashup.Container.NetFX45.exe Framework Version: v4.0.30319 Description: The application requested process termination via System.Environment.FailFast Message: Unexpected exception in background thread of Mashup container (error code -2146233088) Exception: CLR20r3 — FatalError   From MSI log: Product: GatewayComponents -- Error 1920. Service 'On-premises data gateway service' (PBIEgwService) failed to start. Return value 3.   Additional log evidence: Even with all workarounds applied simultaneously (--disable-gpu, --no-sandbox, --use-gl=swiftshader, WEBVIEW2_USER_DATA_FOLDER), the MSI log confirms the installer returns 1603 with Return value 3 at the INSTALL action, consistent across all attempts on this environment.     Workarounds Attempted — None resolved on 3000.314.5 Workaround Result --disable-gpu --no-sandbox --disable-software-rasterizer ❌Crash persists --use-gl=swiftshader added ❌Crash persists WEBVIEW2_USER_DATA_FOLDER set with full permissions ❌Crash persists Visual C++ updated to 14.44.35211 ❌Crash persists Windows Defender exclusions added ❌Crash persists Performance counters rebuilt (lodctr /R) ❌Crash persists Service account changed to Local System ❌New error: "service is marked as interactive" Working Workaround Version 3000.306 installs successfully on the same VM with the following environment variables: WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS = --disable-gpu --no-sandbox --disable-software-rasterizer --use-gl=swiftshader WEBVIEW2_USER_DATA_FOLDER = C:\GatewayWebView2Data   Expected Behavior The Gateway should install successfully on Virtual Machines without GPU acceleration, as it did in version 3000.306. Actual Behavior Microsoft.Mashup.Container.NetFX45.exe crashes with a fatal error during service initialization, causing the installer to roll back. This appears to be a regression introduced in version 3000.314.5. Additional Context The crash occurs because Microsoft.Mashup.Container.NetFX45.exe requires an interactive desktop session that is not available in VM service context The --use-gl=swiftshader flag (SwiftShader CPU fallback) does not resolve the issue in this version Community thread with full investigation details: [Re: On-premises Data Gateway 3000.314.5 - Microsof... - Microsoft Fabric Community] ... View more

The copilot narrative is not able to produce a percentage with more than two decimals when connecting to a "composite model" data set measure.   For example, if the number format in the base (parent) semantic model is 36.53% then Copilot Narrative will ALWAYS produce .36 (without the proper percentage format) in a composite model vs 36.53% when connecting to the parent data set directly.    Similarly it will not pick up on currency formatting in a composite model.    Steps to reproduce: Build a power BI data set with a measure that produces 36.53% Publish and create a copilot narrative  Create a second PBIX with composite model based on the first semantic model Publish and create a copilot narrative  Compare the result The first narrative will show 36.53% and the second will show .36   This does not seem to be an LLM issue. The narrative output is consistently missing the decimals and percentage sign via a composite model.  ... View more

Hello, The November update of Power BI Desktop messed up the metrics and visuals in my new card visual. It happened with the image in the callout, and the reference labels had their layout changed, no longer keeping the spacing I wanted. This is really frustrating because the users who view the report daily (including the bosses) are not getting the metrics they need. Could you please provide a fix or workaround for this problem? Thank you for your support. Just a sample image for your reference.   ... 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 a data pipeline that uses the stored procedure activity to call a sproc in a warehouse in the same workspace. This works fine in dev, but after using the deployment pipeline and running in the test workspace, I get the below error: The server address cited in the error message is indeed for the dev workspace, but when I look into the source code for the activity, I see that the connection details are correctly listed as the test workspace server address and workspace ID: I've also checked the JSON definition of the entire pipeline and can't find any reference to the dev workspace server name either, so I'm not sure why it's attempting to access the dev workspace. The only fix for this appears to delete and recreate the activity in the test environment, invalidating the pipeline. As such, I believe this is a bug in the pipeline activity feature and requires fixing.   Procedure runs successfully when directly executed in SSMS ... View more

I've been trying all day to open both the Microsoft UI String Search and Microsoft Terminology Search pages. Just saw another person posting about it in another forum. I have tried different internet connections to rule out that it isn't my network with a problem. The pages didn't load no matter what.   Error details: Underlying Error: AdalUserAccountDisabledErrorCode Http Status Code: 400 Correlation ID: 108f08d4-b290-3c93-5030-9b4ed93bd126 Activity ID: 6a9b4095-fb15-4b0b-85f8-80b1e8dbc2d6 Request ID: aac0fe68-179b-883a-4bf4-1c7d8466a26d Time: Mon May 04 2026 18:29:32 GMT-0500 (Central Daylight Time) Service version: 13.0.28500.530 Client version: 2605.1.29125-train Cluster URI: https://df-msit-scus-api.analysis.windows.net/ Activity ID: 6a9b4095-fb15-4b0b-85f8-80b1e8dbc2d6 Request ID: aac0fe68-179b-883a-4bf4-1c7d8466a26d Time: Mon May 04 2026 18:29:32 GMT-0500 (Central Daylight Time) Service version: 13.0.28500.530 Client version: 2605.1.29125-train Cluster URI: https://df-msit-scus-api.analysis.windows.net/   Thanks in advance ... View more

Hello Team,   Could you please review and update on the below feature request. Background Customers have reported a regression in the Power BI Service where owners of on‑premises gateway connections unable to modify key connection properties—specifically: Connection type Server name Database name Business Impact Creating new gateway connections: Requires manual remapping of many datasets Increases risk of refresh failures Causes avoidable downtime and maintenance effort This limitation is especially impactful in environments with hundreds of reports and datasets tied to shared gateway connections. Feature Request We request that Power BI reintroduce support for editing existing gateway connection properties, specifically: Connection type Server name Database name At minimum, this capability should be available to: Gateway Admins / Owners. With appropriate validation and warning prompts to prevent accidental misconfiguration. Example below of a connection that the owner of connection and unable to change at this time.   ... View more

I created a semantic model using the 'Paste or manually enter data' option, and used this model to create a report. In my application, using the Microsoft.PowerBI.Api 5.1.0 Nuget package, calls to PowerBIClient..Admin.GetRefreshablesAsync(top: 1000, expand: "group") is throwing an exception, "Unknown RefreshType value. (Parameter 'value') Actual value was WebModeling.". Deleting that semantic model from my workspace resolved the issue, and other semantic models created from sources other than that 'Paste or manually enter data' option do not cause the issue.   The relevant object from the https://api.powerbi.com/v1.0/myorg/admin/capacities/refreshables?$expand=group&$top=1000 call response is  { "value": [ { "id": "...", "name": "Test", "kind": "Dataset", "startTime": "2026-05-11T23:30:24.777Z", "endTime": "2026-05-11T23:30:29.737Z", "refreshCount": 1, "refreshFailures": 0, "averageDuration": 4.96, "medianDuration": 4.96, "refreshesPerDay": 1, "lastRefresh": { "id": ..., "refreshType": "WebModeling", "startTime": "2026-05-11T23:30:24.777Z", "endTime": "2026-05-11T23:30:29.737Z", "serviceExceptionJson": null, "status": "Completed", "requestId": "...", "extendedStatus": null, "refreshAttempts": [] }, "refreshSchedule": { "days": [], "times": [], "enabled": false, "localTimeZoneId": "UTC", "notifyOption": "MailOnFailure" }, "configuredBy": [ "..." ], "group": { "id": "...", "name": "..." } } ] } The RefreshType enum, and the related RefreshTypeExtensions serializer, in the Nuget package need to be updated to handle the WebModeling refreshType.   ... View more

Hello, Starting today, Power BI Desktop freezes every time I try to save.  This happend to me and at least one other colleague. The freezing does not prevent the saving itself so far, but I need to restart Power BI Desktop after each time I save my Report.   Has anyone had a similar issue so far or any suggestion to resolve it? ... View more

Good Day,   Occassionally I filter tables using a Table View to copy filtered results to use outside of Power BI - I.E. in Excel.   As of today it appears that when copying the Table View that has been filtered, it ignores the filters and copies the whole table. This is an issue for me as when I have a table in excess of 700,000 rows it makes this process extremely slow to copy from Power BI, and near impossible to paste it into Excel.   I have already tried uninstalling and reinstalling the program.   Is anyone else experiencing this issue?   As an example, we are a service company and we have a geographic alignment for our field service team. Simply, filtering a table by the "East" Region and trying to copy the table when filtered to the East is not working. Instead, the entire table is copied.   ... View more