When multiple slicers are based on the same date dimension (e.g., a Month slicer and a Date slicer in “Between” mode), the Date slicer does not visually update when filtered by the Month slicer, even though the model is correctly filtered. It would significantly improve UX if the “Between/Before/After” date slicers could optionally auto-sync their visible range with the current filter context. A toggle such as “Synchronize with filter context” would make date filtering behavior more intuitive and consistent across slicer types. ... View more

Hello, I would like to request an enhancement to the Page Navigator visual so that it offers the same layout options available in the Button Segmentation Slicer.                                 Layout options: Orientation: horizontal / vertical / grid Style: blocks / full screen Number of columns Automatic grid Spacing (gap) between buttons Overflow style: paginated / continuous scrolling (scroll)           These same options are not available in the Page Navigator, which limits the use of this visual in reports that rely on button-based navigation. I request the evaluation of this feature, allowing the Page Navigator to offer the same layout configuration options as the Button Segmentation Slicer. This enhancement is relevant in scenarios with a large number of pages, where navigation needs to be intuitive, reducing the need for alternative solutions and manual customizations. ... View more

Im using a design for my power bi reports, in which i allow the user to select what measure they want to look at, from a dropdown, instead of having a new sheet for each measure.  This can lead to some filters becoming redunant for certain measures. As to not confuse the user, I am removing the filter options dynamically, depending on the selected measure, using the "filter on this visual".  If the user already has checked some values and left some unchecked not all values are removed. It would be nice to have the option of removing all filters.  Se this thread for a discussion: https://community.fabric.microsoft.com/t5/Desktop/Dynamically-remove-options-on-slicer-regardless-on-checked-state/m-p/5124123#M1460507 ... View more

In the newer PostgreSQL versions, the "ssl_renegotiation_limit" setting has been removed. The PostgreSQL connector in Power BI is still referencing this setting, so an update is needed for the connector to support encryption with the latest PostgreSQL versions. ... View more

The user wants to customize default questions on Copilot. We believe that Copilot would be more effective if report viewers could select from prompts that the report developer has predefined, rather than having to type their own prompts. ... View more

Currently, Microsoft Fabric supports notifications only at the overall capacity level, which makes it difficult to proactively identify individual artifacts driving high CU consumption. This idea proposes enabling per‑artifact capacity usage alerts for semantic models, reports, and other items. Admins could define CU thresholds at the artifact level and receive notifications when those limits are exceeded. This would help quickly isolate high-impact artifacts, reduce capacity contention, and improve governance and operational efficiency. ... View more

Currently, you can hit weird errors or slow performance when trying to open items in a workspace that is linked to a paused capacity.   It would be a real quality-of-life improvement if there would be a small message or popup showing when a workspace is linked to a paused capacit.   ... View more

One of the most annoying behavior of report designers is to rename fields in visuals in cryptic way without standards and you won't understand at a first sight which field from which table had been used.     AFAIK (without using any external tool or power bi project - just staying in PBI Desktop), the only thing you can do is to hover fields with the mouse and look at the tooltip that shows you the original field/measure home table and name. for further anlaysis you need to move to the data pane and search it manually. Wouldn't it be nice to have a "Go to definition" that points the referenced field/measure in the data pane that you can activate directly in the context-menu right-clicking the field?     ... View more

Currently ms fabric tries to create warehouses and lakehouses with validation on views.  In most cases if view reference items that not exist yet ( example openrowset to files that not yet exist , view ref between 2 warehouses , ... )  Then the whole sync fails. Leaving you in the mid of a sync with no option to at least have infrastructure and all other artificacts available and synced in the workspace.    Some messy intervention is needed to reconstruct.  This makes option as 'checkout to workspace' in many cases impossible.    I believe if auto validation would not be done. Running the pipelines after sync would solve the disconnect And make it possible to solve most of the disconnect in the workspace manually. Making it workable   It would also make azure devops pipelines for automation much easier  ... View more

Description Power BI Desktop loads PBIP report artifacts only at open time. When PBIP files are modified externally (Git pulls, merge conflict resolutions, scripted refactors), those changes are not reflected in an already opened Desktop session, requiring manual close and reopen. This limits the effectiveness of PBIP in Fabric‑first, Git‑based, collaborative development scenarios.   Why This Matters (Fabric & Git) PBIP is foundational for Fabric CI/CD and Git integration. In real-world team workflows: Developers pull changes from Git while Desktop is open Merge resolutions and scripted updates modify PBIP files on disk Desktop cannot reload or apply those changes without restarting This breaks collaborative development, slows iteration, and makes applying Git merges to active reports error‑prone.   Proposed Solution Add an explicit “Reload from Disk” command for PBIP projects in Power BI Desktop. Discards in‑memory state Reloads PBIP artifacts from disk Equivalent to close & reopen, but controlled and safe (Optional future enhancement: detect external changes and prompt the user.)   Impact Enables Git‑collaborative PBIP workflows Allows applying merges and scripted refactors without restarting Desktop Improves Fabric CI/CD and developer productivity Increases PBIP adoption for enterprise teams ... View more

New Desktop app update installed an almost white user interface. There is zero contrast which is not good for the eyes. I see where some people have requested a light interface so incorporate an option to select either light or dark theme like in the Office apps. ... View more

Summary When publishing a report from Power BI Desktop to the Service, the dataset is automatically refreshed if a scheduled refresh is configured. I propose adding an option to disable the automatic refresh on publish, so that publishing only updates the metadata/report, not the dataset. Problem Currently, when a dataset has scheduled refresh enabled, publishing a new version of a report triggers an immediate on-demand refresh in the Service. This behavior is widely observed in the community and is considered standard behavior for datasets with scheduled refresh enabled. However, this creates several problems: Unnecessary refreshes If the dataset is already refreshed (e.g., refreshed locally in Desktop before publishing), there is no need to refresh it again. Long waiting times For large datasets, refresh can take 30–60 minutes or more, delaying availability of small report changes (layout, measures, RLS, etc.). Operational inefficiency In environments with frequent refresh schedules (daily or multiple times per day), triggering an additional refresh on every publish wastes compute resources and capacity. Blocked deployment scenarios Users often need to make quick report or security changes (e.g., RLS roles), but cannot finalize them until the refresh completes. Expected behavior Publishing a report should not automatically trigger a dataset refresh when: A scheduled refresh is already configured, and The dataset does not require immediate data changes. Instead, users should have control over the behavior. Proposed solution Add a setting such as: “Refresh dataset after publish” (On/Off toggle) This could be configured: Per dataset in the Service, or As a checkbox in the publish dialog in Power BI Desktop Default behavior could remain unchanged for backward compatibility, but users should be able to disable it. Benefits Faster deployment of report changes Reduced load on capacity and gateways Better control over refresh timing Improved user experience for enterprise BI teams ... View more

Please include Sunburst Chart similar to what is avble with PowerViz.  This is very useful to show hierarchy level where each fan collapses based on selection. Also, a Spider web chart also is very useful to show element distribution or influence over any one concentrated level.   ... View more

The PowerBI matrix visual only allows users to accurately sort on the leftmost Rows field. Users want to be able to sort the matrix like a table in Excel. They want to be able to sort also on the Values fields to see the highest values for specific metrics to show up on the top. Doing this is not straightforward. It requires users to click through the More Options menu, go to the Sort By menu and select their field name they want to sort by. This still does not produce the intended effect when we also have a field in the Columns section. In our use case we have 4 fields in the values section that are repeated per quarter (using the Date in the Columnn section). Users would like to be able to sort on specific fields for specific dates by simply clicking the column header. However, the leftmost Rows field is the only one which produces the expected sorting behavior. ... View more

Hello Team  Please find the below sugguation where there is no option to monitor the Gateway Usage  Current Gap Fabric admins cannot easily see how many datasets are using a specific On‑premises Data Gateway connection or which datasets/workspaces depend on it. This information is not available in the UI and requires manual correlation using audit logs or APIs. Proposed Enhancement Add a Gateway Usage view in Fabric that shows: Number of datasets using each gateway connection List of dependent datasets and workspaces Last usage / refresh activity Value This improves monitoring, impact analysis, and capacity planning, especially during gateway maintenance, troubleshooting, or scaling decisions. ... View more

Hi We have F256 capacity and we have recently purchased 64 SKUs. Unfortunately, there is no way for us to upgrade the capacity by 64 SKUs, but rather can only jump to the next available one, in your case is F512. This is not feasible option. Provide an option to upgrade the capacity with multiples of 64 SKUs. ... View more

Can we get the Matrix Visual Row and Column Headers Conditional Formating with background color and font color and different font styles in the next power bi update? ... View more

Users or workspace admin need to enable "email subscription" by workspace leve instead of tenant level. This function can provide more flexibility to manage the email subscriptions. Thanks. ... View more

Currently, the source connection for Mirrored DBs is managed through Deployment Rules in data pipelines. There is no way to use Variable Libraries with Mirrored DB, like you can do in CopyJob or Data Pipelines.   Idea: Allow Mirrored DB to use variable library to parameterize connection ID.   My team plans to use fabric ci-cd instead of Fabric Deployment pipelines, so we cannot use Deployment Rules in Fabric deployment pipelines. What we can do is, parameterize the connection ID in GitHub yml file and update on deployment to workspaces.   However, we use Variable Library for CopyJob and Data Pipeline. It would be nice to use Variable Library across the any Fabric ingestion item. ... View more