Business Justification: Tableau has an inbuilt functionality of ‘underlying data export’ at visual level. This is a very useful feature for many users across the organization as they can analyze specific data that was used to calculate a measure or get details on any data point in question. In PowerBI, many users without pro license can also benefit from this feature as they will not have any other way to analyze actual dataset, if need be ... View more

The selected theme is applied to all the pages in the book, but there is no option to apply it to only the current page. It would be great to include an option to apply a theme either to a selected page or to the entire book.     On the Fabric Idea page, I can see a lot of ideas. If I want to check whether someone has already submitted an idea similar to mine, there is no option to search through all the existing ideas. All the ideas are listed on the page, but I don't want to go through each one manually. I would suggest adding a search option so users can quickly check if their idea has already been submitted. ... View more

In Power BI reports that include integrated Power Apps visuals, the deployment pipeline currently updates the dataset connection from test to production environments seamlessly. However, the Power Apps visual does not follow this transition — it remains linked to the original (test) environment and requires manual reconfiguration after each deployment. This creates friction in the deployment process and increases the risk of errors or inconsistencies between environments. Request: Please enhance the deployment pipeline to support automatic environment switching for embedded Power Apps visuals, similar to how dataset connections are handled. This would greatly improve CI/CD workflows and reduce manual overhead for enterprise deployments. ... View more

Hello,   a system variable that contains the timestamp of the schedule (not the actual fired time) would be very useful. Currently, workarounds are needed to store this timestamp. In a data warehouse (lakehouse) environment, this information is very helpful. Example: A Pipeline is scheduled two times a day: 1430 and 2330 This timestamp would be useful as a variable. (At least i could not find it) ... View more

When developing tables in PQ, it's helpful to see columns in a particular order. It's annoying to have to drag...and drag...and drag columns to get them reordered, and tedious at best if you do it in M. (And yes, those steps get removed before going into prod.)   Please add a "Reorder column" option to the the "Choose columns" command options. This would use the same basic dialog as the "Choose columns" command, but would let you drag the column names up or down or have up/down arrows in it. Smaller real estate to drag and faster response because it wouldn't be happening "live," but after you click ok. ... View more

When updating a fact table, particularly when field headers change due to modifications upstream, any dependent measures or calculated columns that reference those now-missing fields can result in errors. Currently, Power BI only displays these errors at the individual measure or column level, requiring users to manually open each folder to identify broken items. It would be highly beneficial to introduce an error indicator at the folder level within the Fields pane, allowing users to quickly see which folders contain errors and efficiently identify and resolve issues caused by schema changes. ... View more

Currently, Power BI does not support manual line breaks in column headers for Table and Matrix visuals. Attempts to insert line breaks using ALT + ENTER, UNICHAR(10), or other newline characters are ignored. This limits the ability to format headers efficiently, especially when trying to save horizontal screen space or improve readability in compact layouts.   Suggested Improvement: Enable support for manual line breaks in column headers, either through: Recognizing ALT + ENTER during column renaming Supporting UNICHAR(10) or similar in DAX expressions used as headers Providing a formatting option in the visual settings to insert line breaks This feature would greatly enhance layout flexibility and improve the user experience when designing reports with limited space. ... View more

When you use the "Visualize this list" feature in Microsoft Lists, the report is created directly in the Power BI Service, but there’s no way to download the .pbix file. This makes it hard for users to make changes in Power BI Desktop, add more data, or keep track of versions. A helpful solution would be to let users download the .pbix file, just like with other Power BI reports. This would make it easier to edit, reuse, and customize the report, and would make the connection between Microsoft Lists and Power BI much more useful. ... View more

Currently, slicer synchronization works only when both slicers contain identical data. However, there may be use cases where we want to synchronize filters even when the selected data in each slicer is different. The goal is to have a setup where selecting a value in one slicer automatically selects a predefined corresponding value in the other slicer, even if the slicer data sets are not the same. Proposed Synchronization Approaches: Option 1: Predefined Value Mapping Create a predefined mapping between the values in both slicers. When a user selects a value in one slicer, a corresponding predefined value in the other slicer will be selected automatically. This can be achieved through DAX logic or using a supporting table with relationships to drive the selection behavior. Option 2: Overlapping Slicers with Hidden Layering Place the two slicers on top of each other, matching their size, dimension, and design. Configure them such that selecting the first item in the top slicer triggers selection of the first item in the bottom slicer (and so on). Set the top slicer’s transparency to 0% so that it hides the slicer underneath, effectively making the user interact with only one slicer visually while syncing both behind the scenes. ... View more

When Power BI executes queries against SQL Server, it connects using the Mashup Engine or Mashup Engine (%HostContext%)) as program_name. In a crowded environment, it can be difficult to identify which semantic model is responsible for activity or issues on the SQL Server side. The desired outcome is to be able to run sp_whoisactive (or query sysprocesses) and see the semantic model name in the program_name column (or something that easily idenfity the source of the query). For example:   Mashup Engine - Semantic Model "Sales_Model_A" (Name or GUID) ... View more

When we create a report in Mobile layout in Power BI desktop and open the report in Mobile browser or Power BI Mobile application, we see that when we double click on any point of the report it gives us a magnified view.   This same behaviour is observed when a report is embedded in any application using the Embed token from Power BI. We would like to have an option in Power BI desktop to disable the double tap behaviour of the reports as by mistake users may click and get this unwanted behaviour. ... View more

In Power BI Desktop, numeric fields are automatically set to "Sum" when added to visuals. While this is useful in many cases, it can be frustrating for users who frequently work with data that should not be aggregated. Feature Request:  Please add a global or report-level setting that allows users to set the default summarization behavior for all fields—especially numeric ones—to "Don't Summarize". Why This Matters: Saves time by reducing repetitive manual changes. Prevents accidental misinterpretation of data due to unintended aggregation. Improves usability for users working with detailed or non-aggregated datasets (e.g., IDs, reference numbers, or pre-aggregated values). Aligns with user expectations in scenarios where summarization is not appropriate. Suggested Implementation: A toggle in Options > Report Settings or Data Load to choose the default summarization behavior. Alternatively, allow setting summarization preferences at the column level in the data model. This small change would significantly improve the user experience for many Power BI users ... View more

Hello Power BI team, As a frequent user of Power BI for business reporting, I truly appreciate the convenience of the "Apply All Slicers" button, which helps streamline the filtering process across multiple slicers. However, in real-world scenarios, there are cases where certain slicers should be excluded from this global apply action. For example: A date slicer might need to apply immediately upon selection. A region slicer might be part of a group that requires manual confirmation via the "Apply All" button. To support such use cases, I would like to request a feature that allows selective exclusion of slicers from the "Apply All Slicers" functionality. Suggested Enhancements: Add an option to exclude specific slicers from the "Apply All" action. Allow slicers to be grouped or tagged for selective application. Enable slicers to be set as auto-apply or manual-apply independently. Support this configuration via the UI or through DAX/JSON settings. This feature would greatly enhance flexibility in report design and improve the user experience for interactive dashboards. Thank you for considering this request! ... View more

We would like to have a Dataflow REST API that retrieves only the data sources actually associated with the given dataflow. With the current API, [Dataflow - Get Dataflow Data Sources], when the same connection information is defined across multiple gateways, all matching data sources appear as candidates—even if only one is actually used in the dataflow.   Related information:  https://community.fabric.microsoft.com/t5/Issues/Incorrect-Gateway-Datasource-Lineage-for-Dataflow-Datasources-in/idi-p/2590034 ... View more

Currently, there is no clear notification mechanism when throttling occurs in Microsoft Fabric capacity. While the admin portal allows setting up alerts based on thresholds to help prevent throttling, there is no direct way to be notified when throttling has actually happened. The only method to detect it is by manually checking the Capacity Metrics app, which is not efficient for real-time monitoring. It would be helpful to have explicit notifications—such as alerts stating "Throttling has occurred"—to ensure timely awareness and response. ... View more

Currently, there is no simple way to check the total storage usage across all workspaces in Microsoft Fabric capacity. The only available method is to manually check each workspace and sum up the usage, which is time-consuming and inefficient. A centralized view or dashboard that shows the total storage usage at a glance would greatly improve usability and management efficiency. ... View more

Currently, auto-scaling is not available for Microsoft Fabric capacity, unlike in Premium capacity. When throttling occurs, there are limited mitigation options, which can impact performance and user experience. It would be beneficial if Fabric capacity could support auto-scaling similar to Premium, ideally with configurable triggers—such as activating auto-scaling when an Interactive Rejection occurs. ... View more

Currently, when using Microsoft Fabric capacity below F64, a Power BI Pro license is required to share reports. Once we scale up to F64 capacity, we no longer face functional limitations, but we encounter a new challenge: there are very limited options for purchasing additional capacity beyond F64. We would like to see more flexible purchasing options offered—specifically, the ability to add smaller increments of capacity even when using F64 or higher tiers. This would help organizations scale more efficiently without being forced into large and costly capacity jumps. ... View more

It would be helpful to have expanded formatting options for individual columns in Table and Matrix visuals—beyond what’s currently available. I’m proposing the following enhancements to the Specific Column Formatting settings: 1. Bold Text Option Allow users to apply bold styling to individual columns. Use Case: When using data bars inside a column, bold text improves contrast and supports accessibility standards, helping key values remain visible. 2. Font Type and Size Control Enable control over font family and font size at the column level. This would improve readability and further support contrast requirements for accessible design.   In the screenshot below (sample data shown), I used a table visual to surface survey items where bar charts weren’t feasible due to the lack of wrap text on y-axis labels. Table visuals allow values to display without truncation. Using Cell elements > Data bars visually illustrates variation across items—making it even more important that column-level text formatting is accessible and customizable.     ... View more