Feedback Type: Frown (Error) Timestamp: 2026-03-06T18:19:06.7423766Z Local Time: 2026-03-06T12:19:06.7423766-06:00 Session ID: d138d906-42e5-459d-9e66-75bfdd06282a 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 = 533325] Peak Virtual Memory: 87.7 GB Private Memory: 1.12 GB Peak Working Set: 1.2 GB IE Version: 11.3636.19041.0 User ID: ee65ea6f-6dfa-4919-aa17-f724be5fcc43 Workbook Package Info: 1* - en-US, Query Groups: 0, 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 Recent Actions: VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties, VisualContainerPersistProperties DPI Scale: 100% Supported Services: Power BI WebView2 Runtime Version: 145.0.3800.82 WebView2 SDK Version: 1.0.2365.46 ... 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

Hi,    When refreshing the schema and data in a PowerBI dashboard, i received an "Object reference not set to an instance of an object" error for all tables. This error does not occue if only the data is updated, so it seems to be an issue with updating the schema.    I experience this error with the February 2026 version of the PowerBI desktop app, however when reverting to the November 2026 version of PowerBI, this error does not occur.    Thanks! ... View more

Following the post: https://community.fabric.microsoft.com/t5/Desktop/ALT-letter/m-p/5108912 The Alt + [letter] shortcuts are not working. I also tested this on version 2.150.2455.0 64-bit (January 2026). ... View more

I will try to describe my issue in a structured manner:   sub-issue I am working with version control (DevOps). When I rename a notebook in Fabric, the underlying file structure in DevOps is not renamed. This is very annoying.    My workaround to the sub-issue  I download the notebook to my local computer, rename it and import it in Fabric via the web UI.  Main issue: When I call the notebook as a child notebook in a python runtime notebook. The following error appears:   Workaround to main issue Open the imported notebook. Select the runtime again and the runtime version. Start the session. Run a cell. Stop the session. Save notebook and close. This used to work but now it doesn't.   Steps to reproduce Create notebook Download notebook to local device Rename notebook Upload the renamed notebook Create a DAG with the imported notebook Run `notebookutils.notebook.validateDAG(dag)` <-- this is when the error should appear. ... 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

Previously I was able to search for a specific number in integer columns in the table view, but that option seems to be gone in the latest version of Power BI Desktop. I do have the option to make a number filter, but my problem is, that I am working with hash keys, which are (very) long strings of numbers.   When applying a number filter, the last two digits of the hash key get 'cut off' and replaced by '00' instead, making the search almost impossible. Why was the seacrh option removed, and is there some way to get it back? ... View more

To connect to our IBM DB2 database, we need to set a custom "packageCollection" value as an additional connection property in a copy activity.   However, when inspecting the pipeline's JSON, we noticed that "packageCollection" is added with a trailing space ("packageCollection "). This causes issues, as the DB2 database doesn’t recognize the property correctly.   Manually removing the space in the JSON makes the pipeline work again, so for anyone facing the same issue, that’s a temporary fix. But ideally, this bug should be resolved at the source.   As it stands, fixing it manually means the property can’t be configured through the UI anymore.   ... View more

After the latest updates released with the November Update, all our reports that use the New Card Visual have a serious problem with the management of images inserted in the Card. For example. I have this card with three blocks in which I have inserted a small icon (see image). In PowerBI desktop, the rendering is correct and consistent with the values entered in the configuration. However, when I publish the report on PowerBI Service, the card rendering is completely incorrect: (note how the image in the card is significantly larger, as if the “size” 50px parameter were not being taken into account) Could you kindly intervene as soon as possible, as all our reports using the new cards are currently illegible and, in some cases, do not contain any information? Regards -- Gianluca Pinelli ... View more

I have a report with a matrix visual, which is powered by a DirectQuery source that gets updates every minute. The report refreshes automatically with a change detection on the column with last updated timestamp. The problem is that the matrix visual scrolls up to the 101st position after each visual refresh. Users have to scroll back down to the position they were looking at before, and after a minute it jumps back up again. The faster I wish to refresh this report, the more prominent this issue becomes. The position of the scroll bar does not reset when the visual displays records in range 1-101 prior to refresh. The root cause seems to be present in the DAX query generated on the matrix refresh event - it contains "TOPN(101)" filter. Each scroll event past that number of rows generates a subsequent query that fetches next 101 records. This degrades the user experience massively, and puts unnecessary strain on my source by sending lots of small queries. In this case, I'm working with around 3000 raw records, which aggregate to 350 rows in the matrix. This could be easily fetched with a single query, which should keep the position of the scroll bar in place between refreshes. I would like to be able to specify the number of records fetched in a single query to my source; 101 is a very conservative number. ... 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

Hi, Since the update July 2025, Matrix visuals with fields parameter hierarchies show a confusing behavior when one field is on different hierarchy levels. To illustrate the issue I created a test report with the following field parameter:   FP_Test = { // Group1 ("Category", NAMEOF('Product'[Category]), 0, "Group1"), ("Business Type", NAMEOF('Reseller'[Business Type]), 1, "Group1"), // Group2 ("Country", NAMEOF('Sales Territory'[Country]), 10, "Group2"), ("Category", NAMEOF('Product'[Category]), 11, "Group2"), // Group3 ("Business Type", NAMEOF('Reseller'[Business Type]), 20, "Group3"), ("Color", NAMEOF('Product'[Color]), 21, "Group3") }   The fields "Category" and "Business Type" are part of 2 hierarchies but on different levels. The visual looks like this:   If I now switch to Group2, I get the following display:   For the users, it looks as if the button did not work, as the category is still displayed. They can't even recognize that they are at a drilled down level because no +/- signs and no elements of the next higher hierarchy are displayed.  Switching now to Group3 it gets completely weired because only the lowes level ("Color") is visible whereas the user would expect to start with "Business Type". The users have to be very experienced to notice that they are looking at a drilled down level and need to drill up  to see the full hierarchy for this group:   Starting with an expanded hierarchy in Group1, it is not apparent in which case the hierarchy remains expanded, when it is collapsed and when a drill down takes place without a top level hierarchy. Anyway, a hierarchy that is expanded by default is not recommended or possible for a large number of hierarchy elements.   The same behavior applies to bar charts and column charts, where it is even more difficult to recognize that it is a next lower level and you have to drill up.   Please add a formatting option to all visuals that works with the drill-up/drill-down functionality, where the developer can choose whether the matrix/chart should collapse when switching the dimensions or retains its expanded state.   And if a matrix/chart retain the expanded state, please add the upper levels as well! I'm working as BI Consultant for customers and they complain about this new behavoir, because it appears as if the dynamic doesn't work anymore. I don't want to go back to bookmarks switching between various matrix visuals.   Thanks and best regards! ... View more

Hi, Note: Issue noticed in unreleased July 2025 edition of PBI Desktop.   I m using Field Parameters on Rows of the Matrix and trying to provide dynamic selection for the users. However, the functionality stops after making slicer selection a couple of times and expand/ drill down buttons no longer works.   For the selection as shown in snapshot below, I would expect the user to expand and see Col2 and Col3 in the matrix visual. However.  no matter how many times you click, its not possible to expand. It is not dependent on the order of selection of columns or layout configuration in use. Request you to address the issue ASAP.     Sample PBIX is available at the below link: Test/Test Matrix.pbix at main · modi123p/Test   Thanks & Regards, Madan Prabhakara ... View more

Since the August 2025 update it appears Direct Query connections cannot be selected when connecting to Dataflow Gen 1 sources. Any reports that were previously setup using Direct Query return the following error: "This query contains transformations that can't be used for DirectQuery." ... View more

Hi,   After the March update (Version: 2.141.1253.0 64-bit (March 2025)), almost all of the visuals are showing errors. Here is the prompt when clicking "See details":   Error fetching date for this visual An expected error occured (file " , line , function ").   Hope this issue be reverted soon. Regards, ... View more

I'm encountering the following error when trying to connect to a Dataflow using the Dataflow connector in Power BI: The name 'Lakehouse.Contents' does not exist in the current context. This happens when attempting to access a Dataflow that is stored in a Microsoft Fabric environment, specifically within a Fabric workspace. Context: I'm using the Dataflow connector in Power BI Desktop. The Dataflow is created and stored in a Fabric workspace (not a legacy workspace or classic Power BI workspace). The error appears immediately after selecting the Dataflow and trying to load or transform the data. Troubleshooting so far: Verified permissions to the workspace and the Dataflow. Confirmed that the Dataflow is published and accessible via the Fabric UI. Tried using both organizational and personal accounts for authentication. Question: Has anyone else experienced this issue when working with Dataflows in Fabric environments? Is there a known workaround or update needed to support this connector in Fabric? Any insights or suggestions would be greatly appreciated!   Thanks in advance, David ... View more

For Gen1 Dataflows, my team and I cannot see any option to send refresh failure notifications to anyone but the Dataflow owner. This is when we configure refresh failure notifications via the Power BI Service. See the image below. We used to be able to do this without issues previously.   We have checked on multiple devices, with different users logged in, on different browsers, cleared cache and cookies, and done so in incognito mode to no success. ... View more

A huge range of app use cases don’t involve the Power BI homepage at all, so why do we need a button that takes you “back” there? In my own tenant, only a small percent of users ever discover the button — and when they do, it usually causes confusion. Most of our audience comes in through our company intranet or a saved bookmark directly to the app. Hitting “Go back” takes them somewhere unfamiliar (Power BI home) and disrupts their workflow. This could be fixed with one of two approaches: Let admins remove or hide the button entirely Or at least rename it to something clearer like “Power BI Home” so expectations match what it does Either way, making this change would help avoid confusion and keep users focused on the content that matters most: the app itself. ... View more