Hi Microsoft Fabric Team, We are encountering a sign-in error when trying to use the Fabric MCP connector. The error is not on our tenant side — the app registration belongs to Microsoft. Error Code: AADSTS50011 Full Error Message: "The redirect URI 'https://global.consent.azure-apim.net/redirect/fabricmcp' specified in the request does not match the redirect URIs configured for the application '3f021233-1542-41f0-8faa-ca8aca37ace'." Details: - App ID: 3f021233-1542-41f0-8faa-ca8aca37ace - Missing Redirect URI: https://global.consent.azure-apim.net/redirect/fabricmcp - This application is NOT registered in our Entra tenant — it belongs to Microsoft This means the redirect URI needs to be added by Microsoft on their side in the app registration for the Fabric MCP application. Requested Action: Please add 'https://global.consent.azure-apim.net/redirect/fabricmcp' as an allowed redirect URI in the Microsoft-owned app registration (App ID: 3f021233-1542-41f0-8faa-ca8aca37ace). Thank you.       ... View more

We are observing Copilot in Power BI returning semantic‑model‑grounded responses (including DAX calculated results) for reports and models hosted entirely in shared capacity, even when the user has View‑only access. This appears to conflict with current Microsoft documentation around Copilot capacity and  behaviour. Environment / Setup Fabric F4 capacity enabled for a Copilot PoC (all existing reporting is on a shared capacity) Test report and semantic model: Both saved in a shared capacity workspace Workspace is not Fabric‑backed User permissions: Viewer access to the report No Build permissions on the semantic model Copilot accessed via: Copilot pane in the Power BI Service (within the report) We expected that copilot will only provide responses at the visual level for any artefacts in shared capacity workspaces and that model grounded responses would only be provided where the model is in the fabric workspace. Believe this is unexpected behaviour or a bug? If it is expected behaviour then the issue of preventing copilot accessing existing models is then our very big issue as there seems to be no way to control access to existing models that are published on the service is we enable copilot for our users.. ... View more

Hi we have a data portal on our wordpress site and out of nowhere are now getting an error message:    "This content isn't available. Learn more about Power BI."   any ideas on what we should do? Our webteam is saying it's a power BI issue but there doesn't seem to be any outages - we are in Australia.   thank you! ... View more

We are seeing an intermittent Power BI Embedded error when navigating to report pages that contain DirectQuery visuals (Snowflake). The report embeds successfully and authentication completes without issues, but on navigating to certain pages, Power BI throws a QueryUserError for one or more visuals. The issue is non‑deterministic and does not reproduce consistently, even after clearing browser cache. Retrying (re‑embedding the report) resolves the issue immediately. Environment Power BI: Embedded (JavaScript SDK) Data source: Snowflake (DirectQuery / Live connection) Authentication: Azure AD (MSAL, silent token acquisition) Client: Angular application Observed Behavior User loads the embedded Power BI report. Authentication completes successfully (silent token acquisition). Initial report page (navigation-only content) loads correctly. User navigates to another page containing DirectQuery visuals (tables from Snowflake). Power BI emits an error event: message: QueryUserError detailedMessage: Error fetching data for this visual. Could not render a report visual titled: undefined The same report works immediately after retry/re-embed, without any config or permission changes. Error Details Captured from Power BI error event: message: QueryUserError detailedMessage: Error fetching data for this visual. errorCode: (not present) technicalDetails: requestId: 69d24971-90f2-437b-ad53-f426b21c836e Note: Error occurs at the visual query execution stage, not during authentication or embed initialization. Key Observations This happens randomly, not on every load. Clearing browser cache does not prevent the issue. Silent token acquisition succeeds before and after the error. Re‑embedding the report (retry) resolves the issue consistently. The error occurs only on pages that trigger DirectQuery execution. The report works as expected in Power BI Service. Expected Behavior Once authentication and embedding succeed, navigating between report pages should consistently execute DirectQuery visuals without intermittent query failures. Why This Is Being Raised The issue appears to be a transient DirectQuery execution failure within the Power BI embedded session. Since retrying resolves the issue without any change, this suggests a runtime/session readiness or query execution instability rather than a configuration issue. We are providing the requestId for investigation into Power BI / Snowflake query execution at the time of failure. Impact Users intermittently see visuals fail to load when navigating report pages. Requires manual retry/reload, which impacts user experience. Hard to reproduce consistently, making it difficult to diagnose without backend correlation. Request Please investigate the above requestId to determine: Why the DirectQuery visual execution fails intermittently Whether this is related to session initialization, capacity load, or Snowflake connectivity Any recommended mitigation or best practice for embedded DirectQuery scenarios ... View more

Hi all,    I want to mirror a sharepoint list in Fabric (West Europe licence).   I saw online that you have to enable the Database mirroring option using the following steps:  Tenant settings -> Microsoft Fabric -> Mirrored Databases (Preview)  --> 'Enabled'.    But when I go to the tenant settings, I don't even see the Mirrored Databases (Preview) option. So I cannot enable it. Why is this the case? Is this nog available yet for me or did I overlook something else?    Thank you in advance for answering.    Kind regads, Redjien    ... View more

Description In the Korean localized version of Power BI Desktop, the Conditional Formatting Rules dialog has a translation error. The logical operator "AND" (which connects the minimum and maximum conditions) is mistranslated as "끝:" (meaning "End:"). What it looks like The rule row reads: If 값 >= 최소값   숫자   끝:   <   0   숫자   THEN   [color] Screenshot (red box highlights the mistranslated "끝:"): What it should be The correct Korean translation for "AND" in this context should be something like: "그리고" (and), or "AND" (keep the English term, as used in DAX/M), or "이고" (conjunction) "끝:" (End:) makes no sense in this context and confuses users. Location Feature: Conditional Formatting → Font Color / Background Color / Icons Dialog: Rules-based formatting Element: The connector between the "minimum" condition and the "maximum" condition in a rule row English UI: Shows "AND" Korean UI: Shows "끝:" (wrong) How to Reproduce Set Power BI Desktop language to Korean (한국어) Select any visual (e.g., Card, Table, Matrix) Go to Format → Conditional Formatting → Font Color (or Background Color) Set format style to "규칙" (Rules) Observe the rule row — the word between the min and max conditions shows "끝:" instead of "AND" Impact Confusing for all Korean-speaking Power BI users "끝:" (End) implies the rule is ending, which is the opposite of its actual meaning (a logical AND connecting two conditions) Simple localization fix — just correct the translation string This mistranslation has existed for nearly 10 years — since the early days of Power BI Desktop's Korean localization. It has never been corrected despite being immediately obvious to any Korean-speaking user who uses conditional formatting rules. A one-line string fix is all that's needed. Environment Power BI Desktop: March 2026 (latest), but this issue has been present since the feature was first localized to Korean OS: Windows 11 Language: Korean (한국어) ... View more

Description When typing Korean (Hangul) in the Power Query Editor — either in the Advanced Editor or the Formula Bar — characters overwrite each other instead of composing normally. Example Trying to type "고객주소" (4 Korean syllables, meaning "Customer Address"): Type "고" → appears correctly Type "객" → "고" disappears, replaced by "객" Type "주" → "객" disappears, replaced by "주" Type "소" → "주" disappears, replaced by "소" The result is only the last syllable instead of the full word. Each new syllable replaces the previous one instead of appending. Workarounds (not real solutions) Press Space after each syllable, then Backspace to remove the space — extremely tedious Type Korean text in Notepad first, then copy-paste into Power Query Disable M Intellisense in Power Query options — this fixes the issue, but losing Intellisense is not an acceptable workaround Root Cause The M Intellisense engine interferes with the Korean IME composition process. When M Intellisense is enabled, the editor intercepts the IME composition events, causing the overwrite behavior. Disabling M Intellisense confirms this is the root cause. How to Reproduce (Important for non-Korean testers) This bug only occurs with a Korean IME (Input Method Editor) active. To reproduce on a non-Korean system: Go to Windows Settings → Time & Language → Language & Region Add Korean (한국어) as an input language Add the Microsoft IME keyboard for Korean Switch to Korean input (Win+Space or language bar) Open Power BI Desktop → Power Query Editor Make sure M Intellisense is ON (default setting) Try typing any Korean text in the Formula Bar or Advanced Editor Observe: characters overwrite instead of composing Note: Simply installing the Korean language pack is not enough — you must actually switch the active input method to Korean IME and type in Korean. If you just test with English input, you will not see this bug. This is likely why previous reports were dismissed as "cannot reproduce." Impact Affects all Korean-speaking Power BI users who need to use Korean column names, comments, or string values in M queries Likely affects other CJK (Chinese, Japanese, Korean) IME users as well, since the underlying issue is IME composition event handling This has been ongoing for several months with no fix Environment Power BI Desktop: March 2026 (latest), but issue started several months ago OS: Windows 11 Input Method: Microsoft Korean IME M Intellisense: ON (default) → bug occurs / OFF → bug disappears Expected Behavior Korean text should compose normally in the Power Query Formula Bar and Advanced Editor, with M Intellisense enabled, just like it does in every other text input in Power BI Desktop (DAX editor, visual titles, etc.). ... View more

With Text Box visual when using Number or Bullet list items, if the first word is formatted then it affects the whole line item. This is only when it is published in Power BI Service, no issue in Power BI Desktop. Underline seems to be the only one not causing an issue, whereas Bold, Italic, Colour, and Font do. This issue seems to have only started in the last week or two (in Feb 2026). Image below to demonstrate.     ... View more

Hi,   this issue has me puzzled for some time now: I have a data set and a report published in the PowerBI service, which every few days shows incorrect data that does not match the imported data. The data is grouped by weeks. Every few days (but irregularly) the current week shows the exact same data as the previous week. Prior weeks are not affected. The underlying data is 100% correct (was checked multiple times by different people). If I export the summarized data it shows the same (false) values which the visual displays. If I export the underlying data it shows the correct data: Note how the visual shows a total cost of 8 for both weeks 12 and 13, while the underlying data shows a total cost of 5 for week 12 and 2 for week 13. This happens for all the visuals and KPIs in the entire report.   We import the data from csv files. We use full refreshes (no incremental refresh). I tried several things to fix this, but so far only found a temporary workaround. Refreshing did not fix it. Republishing the data set and report did not fix it. Only deleting the data set and report in Power BI service and then publishing it again (without any changes whatsoever, it's the same version that just was deleted) fixed it. At least for some days, when it occurs again.   Any help in finding the cause for this issue and a way to fix it (permanently) is greatly appreciated. ... View more

Hi,    I have this kind to architecture   Power BI report --> Publish to workspace --> Copy the link through report and share throughout our internal team (meaning the report is embedded report)    Then from this link, I actually use bat file to keep refreshing at one TV. (as Monitoring)   Questions, how for user to write comment on particular graph and once refresh it straight away appear at TV?    Anyone have idea?    ... View more

Description: Clicking any shape or image in a local .pbix file triggers a "Loading" spinner and an "Enter your email" prompt. The Failure: The sign-in dialog is non-functional. Entering an email address does not process; it either refreshes the prompt or remains frozen, preventing any return to the report canvas. Attempted Technical Bypasses: * Registry keys ShowLeadGenDialog and ShowOnObjectOnboarding set to 0 (Ignored by app). WebView2 cache cleared. "On-Object" formatting disabled in Global Options. "Action" and "Tooltips" toggled OFF for all objects. Business Impact: High. I cannot complete client deliverables or edit dashboard templates due to this soft-lock. Required Action: I am requesting a direct technical solution to completely suppress these onboarding/authentication prompts for local report development. Please provide a functional workaround or a fix that does not require cloud authentication to edit local shapes. ... View more

In Power BI Dataflow Gen1, there is a confusing discrepancy in the data preview experience that impacts usability and validation. When connecting to a data source containing approximately 10,000 rows, the Dataflow view displays only 10 rows, even though aggregation functions such as COUNT correctly return the full row count (10,000). Interestingly, when the same entity is linked or referenced, the entire dataset becomes visible. This inconsistent behavior creates uncertainty during data validation and transformation, especially for developers and administrators who rely on preview data to verify correctness. It would significantly improve the user experience if Dataflow Gen1 allowed configurable or full dataset previewing, or at least clearly indicated preview limitations. In addition, I would like to suggest introducing a “Clear Cache” option in the Power BI Service, controlled at workspace or artifact level, to help mitigate issues caused by stale metadata or cached results. A cache reset capability would improve troubleshooting, ensure more predictable job execution, and provide a smoother overall development and operational experience. ... View more

Feedback Type: Frown (Error) Timestamp: 2026-03-25T14:19:19.6099435Z Local Time: 2026-03-25T09:19:19.6099435-05:00 Session ID: 2624baec-d870-4a05-a0c2-b90000f02f9d Release: February 2026 Product Version: 2.151.1182.0 (26.02)+b81be254f3450e536a43f73a9777be8307916ef0 (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.<ApplyQueryChangesAndCreateRelationships>b__1() at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.ExecuteInTransaction(IExtendedModelChangeScope modelChangeScope, Func`1 action) at Microsoft.PowerBI.Modeling.Engine.Loader.PowerQueryToModelLoader.<ApplyQueryChangesAndCreateRelationships>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.<PerformLoadInternal>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.<<PerformLoadAsync>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.<<PerformLoadAsync>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.<<RunInAsyncActivity>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.<RunInAsyncActivity>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.<RunInAsyncActivity>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.<PerformLoadToAnalysisServices>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.<ExecuteInternal>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.<Execute>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.<<RunInAsyncActivity>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.<RunInAsyncActivity>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.<RunInAsyncActivity>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.DesktopModelingHost.<>c__DisplayClass17_0.<<LoadToModel>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.<<RunExtendedModelChangeAsync>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.<ContinueWithAsyncOperation>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.<LoadToModel>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__DisplayClass45_0.<<StartLoadToReportFlow>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.<HandleAwaitableAsyncExceptions>d__1.MoveNext() PowerBINonFatalError: {"AppName":"PBIDesktop","AppVersion":"2.151.1182.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.26100.0 (x64 en-US) CLR Version: 4.8 or later [Release Number = 533320] Peak Virtual Memory: 88.9 GB Private Memory: 1.32 GB Peak Working Set: 1.74 GB IE Version: 11.1882.26100.0 User ID: 969da791-4720-4053-ab65-3d17f7355c23 Workbook Package Info: 1* - en-US, Query Groups: 5, 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_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 DPI Scale: 100% Supported Services: Power BI WebView2 Runtime Version: 146.0.3856.72 WebView2 SDK Version: 1.0.2365.46 ... View more

Feedback Type: Frown (Error) Timestamp: 2026-03-24T13:32:12.3973224Z Local Time: 2026-03-24T10:32:12.3973224-03:00 Session ID: 2887ba44-635c-4d62-a53e-62a65876688d Release: March 2026 Product Version: 2.152.882.0 (26.03)+1a553843dbf742c4f296a385ff17812c9662bc4d (x64) Stack Trace: Javascript&colon;TypeError at SandboxDelegate.persistProperties (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:3052631) at SandboxVisualProxy.onMessageReceived (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:12717474) at https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:12712981 at MessageChannelProxy.invokeHandler (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:2870755) at MessageChannelProxy.dispatchMessage (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:2870637) at MessageChannelProxy.onMessageReceived (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:2870302) 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:2868626) PowerBINonFatalError: {"AppName":"PBIDesktop","AppVersion":"2.152.882.0","ModuleName":"https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js","Component":"SandboxDelegate","Error":"TypeError","MethodDef":"persistProperties","ErrorOffset":"1:3052631","ErrorCode":""} OS Version: Microsoft Windows NT 10.0.22631.0 (x64 pt-BR) CLR Version: 4.8 or later [Release Number = 533320] Peak Virtual Memory: 86.9 GB Private Memory: 756 MB Peak Working Set: 953 MB IE Version: 11.1.22621.0 User ID: 8246b434-78e2-4eba-9237-344adf91cb41 Workbook Package Info: 1* - en-IN, Query Groups: 0, 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_advancedSlicerTypeList PBI_aiNarrativesVisual PBI_visualCalculationsAuthoring PBI_copilotUnifiedTooling PBI_UserInstalledNetezzaODBCDriver PBI_sqlDbNativeArtifactsOnDesktop PBI_enableExportQueries Disabled Preview Features: PBI_UseRedshiftODBCV2 PBI_snowflakeLegacyOdbcVersionEnabled PBI_shapeMapVisualEnabled PBI_SpanishLinguisticsEnabled PBI_qnaLiveConnect PBI_b2bExternalDatasetSharing PBI_onObject PBI_publishDialogsSupportSubfolders PBI_enhancedReportFormatPBIX PBI_qnaImproveLsdlCopilot PBI_customCalendars MashupFlight_EnableOracleBundledOdacProviderV2 PBI_supportUDFs PBI_newVisualDefaults2026 Disabled DirectQuery Options: TreatHanaAsRelationalSource Cloud: GlobalCloud Recent Actions: VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties DPI Scale: 150% Supported Services: Power BI WebView2 Runtime Version: 146.0.3856.72 WebView2 SDK Version: 1.0.2365.46 ... View more

I’ve encountered what appears to be a significant issue in Power BI relating to how the Table visual handles rows when certain numeric fields are set to summarise (e.g., Sum).   If a table visual displays fields all coming from the same table, and one or more of those fields are summarised numeric columns—for example:   Cost (summarised as Sum) —then any row where these columns contain null/blank values is completely excluded from the table visual, even when: No filters are applied All filters are cleared/reset The record has valid values in all other displayed columns Power BI effectively omits these rows entirely, giving the impression that they do not exist in the data model.   I originally assumed this was a modelling or filtering issue, but it turned out to be caused solely by the column setting. Changing the fields from Summarize → Don’t Summarize causes the missing records to reappear.   Rows should appear regardless of whether a summarised numeric column has a value, especially since the visual is row-based and all columns originate from the same table. Or, at least have a toggle setting to manage this behaviour.   Could Microsoft please confirm whether this is expected behaviour, a modelling constraint, or a potential defect in the Table visual’s handling of summarised numeric fields? ... View more

While using WorkspaceInfoClient.GetScanResultAsync from the Microsoft Power BI .NET SDK v5.0 (https://github.com/microsoft/PowerBI-CSharp), an exception is thrown during execution and the scan result is not returned. The issue appears to be related to deserialization inside the SDK. Below are the error details and stack trace.   {"errors":[{"message":"Unable to synchronize testing. Unable to synchronize testing","details":null,"stackTrace":null},{"message":"Unable to synchronize objects.","details":"The requested operation requires an element of type 'Object', but the target element has type 'Array'.","stackTrace":" at System.Text.Json.ThrowHelper.ThrowJsonElementWrongTypeException(JsonTokenType expectedType, JsonTokenType actualType)\r\n at System.Text.Json.JsonElement.EnumerateObject()\r\n at Microsoft.PowerBI.Api.Models.RoleMember.DeserializeRoleMember(JsonElement element)\r\n at Microsoft.PowerBI.Api.Models.Role.DeserializeRole(JsonElement element)\r\n at Microsoft.PowerBI.Api.Models.WorkspaceInfoDataset.DeserializeWorkspaceInfoDataset(JsonElement element)\r\n at Microsoft.PowerBI.Api.Models.WorkspaceInfo.DeserializeWorkspaceInfo(JsonElement element)\r\n at Microsoft.PowerBI.Api.Models.WorkspaceInfoResponse.DeserializeWorkspaceInfoResponse(JsonElement element)\r\n at Microsoft.PowerBI.Api.WorkspaceInfoRestClient.GetScanResultAsync(Guid scanId, CancellationToken cancellationToken)\r\n at Microsoft.PowerBI.Api.WorkspaceInfoClient.GetScanResultAsync(Guid scanId, CancellationToken cancellationToken)\r\n ... View more

I am getting an error when trying to work open a dashboard. It said to copy the details to clipboard and paste them here for quicker help. Anyone have any idea how to fix the issue? Feedback Type: Frown (Error) Timestamp: 2026-03-23T21:23:05.8316437Z Local Time: 2026-03-23T16:23:05.8316437-05:00 Session ID: 1209e094-554b-4570-9745-44cd913eeb08 Release: November 2025 Product Version: 2.149.1429.0 (25.11)+bde538da1131949e2404b2eefbc12fe5cf1882b0 (x64) Stack Trace: Javascript&colon;TypeError: Cannot read properties of undefined (reading 'visual') at ThemeServiceBase.getInheritParentColors (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:9690325) at ThemeServiceBase.getVisualStyle (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:9690047) at ThemeService.getVisualStyle (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:12582602) at ExploreCanvasCore.updateDotGridLayout (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:5788206) at https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:5777748 at p (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:4862624) at ExploreCanvasCore.resetThemableProperties (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:5777597) at https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:5791149 at p (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:4862624) at ExploreCanvasCore.onExplorationLoaded (https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js:1:5791113) PowerBINonFatalError: {"AppName":"PBIDesktop","AppVersion":"2.149.1429.0","ModuleName":"https://ms-pbi.pbi.microsoft.com/minerva/scripts/desktop.min.js","Component":"ThemeServiceBase","Error":"TypeError: Cannot read properties of undefined (reading 'visual')","MethodDef":"getInheritParentColors","ErrorOffset":"1:9690325","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: 87.3 GB Private Memory: 634 MB Peak Working Set: 717 MB IE Version: 11.1882.26100.0 User ID: 2fb8a41b-8e8f-4b2e-b08a-eab1260b84a1 Workbook Package Info: 1* - en-US, Query Groups: 0, fastCombine: Disabled, runBackgroundAnalysis: False. Telemetry Enabled: True Model Default Mode: Import Model Version: PowerBI_V3 Enabled Preview Features: 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_textSlicer PBI_aiNarrativesVisual PBI_visualCalculationsAuthoring PBI_copilotUnifiedTooling PBI_UserInstalledVerticaODBCDriver PBI_sqlDbNativeArtifactsOnDesktop PBI_dataFunctionActions PBI_enableExportQueries Disabled Preview Features: PBI_DatabricksAdbcVersionEnabled PBI_snowflakeLegacyOdbcVersionEnabled PBI_shapeMapVisualEnabled PBI_SpanishLinguisticsEnabled PBI_qnaLiveConnect PBI_metricsArtifactsOnDesktop PBI_b2bExternalDatasetSharing PBI_enhancedTooltips PBI_onObject PBI_publishDialogsSupportSubfolders PBI_enhancedReportFormatPBIX PBI_qnaImproveLsdlCopilot PBI_customCalendars PBI_UserInstalledNetezzaODBCDriver MashupFlight_EnableOracleBundledOdacProvider PBI_supportUDFs Disabled DirectQuery Options: TreatHanaAsRelationalSource Cloud: GlobalCloud DPI Scale: 100% Supported Services: Power BI WebView2 Runtime Version: 146.0.3856.72 WebView2 SDK Version: 1.0.2365.46 ... 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

I am experiencing a visual regression where visual header containers (three white squares) appear when hovering over slicer visuals, even when all visual header options are disabled. This issue is not isolated to a single report and not caused by recent report edits: The behavior now appears in: Multiple PBIX files Including older backups stored on our network Including reports that have not been opened or modified recently This strongly suggests a Power BI Desktop / rendering regression, not report‑level configuration or authoring actions. They appear in the desktop version and the published report.      ... View more