Fabric Ideas

Hey everyone,   We all know the truth—pie charts are technically allowed, but should they be? Absolutely not. That’s why I’m proposing a new feature for Power BI: Auto-Swapping Pie Charts. Here’s how it works: Whenever a user hovers their mouse over a pie chart, it instantly swaps places in the report grid with a more appropriate visualization that does make sense (like a bar chart, scatter plot, or anything that actually communicates data effectively).   Bonus Features: - If a user insists on bringing back the pie chart, Power BI will dim their screen and play a 30-second TED Talk on why pie charts are misleading.   As a start, we can implement this as an April Fool’s joke, and if the community response is overwhelmingly positive (as it should be), we can consider making it a permanent feature. ... View more

Currently, the Microsoft Fabric Data Warehouse supports metadata-based backup capabilities, which are effective for recovery in the event of failures. While Disaster Recovery (DR) provides fault tolerance, its high cost makes it challenging for organizations with limited budgets to implement. To address these limitations and provide a more cost-effective solution, we strongly request the addition of a feature to directly export or back up tabular data stored in OneLake in the Delta Parquet format as part of the Data Warehouse functionality. Furthermore, implementing backup options such as "full" and "differential," similar to those available in SQL Server, would improve flexibility and operational efficiency. Introducing these features would significantly enhance Fabric's backup and recovery capabilities, providing users with a robust and cost-effective data protection solution. ... View more

Would be great if we can format colours on error bars. ... View more

Many of the layer types on an Azure map visual in Power BI allow for conditional formatting of color, including the bubble layer and an imported reference layer. It would be nice if paths could also have conditional formatting of color. At present, path layer colors can only be set statically based on legend or path IDs which is not very flexible.  ... View more

Could Microsoft support SQLMesh project so that they provide good compatibility against Fabric warehouse and lakehouse (via Spark)? Could SqlMesh be added as Fabric native workload to get it as service since this kind of sql modeling functionality with web UI is missing? Add support for Microsoft Fabric · Issue #3374 · TobikoData/sqlmesh ... View more

The matrix visual is currently set to around 100 columns. I have a report of Air Quality permit numbers that ranges up to almost 140. The matrix will not show all of the columns, so the customer has to filter the list with slicers the get the display to below 100 columns. This report has been un use for several years, and I would like to see it work correctly.    Thank you. Johnny Jones   johnny.jones@deq.nc.gov   ... View more

I propose adding a "freezable header" section to Power BI report canvases. This would function similar to the frozen header rows in Excel or fixed navigation bars on websites, allowing report creators to designate a portion of the canvas as a persistent header that remains visible while users scroll through the rest of the report content.   Currently, when designing reports with multiple visualizations that extend beyond a single screen view, important interactive elements like slicers, filters, or key metrics disappear as users scroll down to view content lower on the canvas. This creates a disconnected experience where users must constantly scroll back up to adjust filters or reference key information.   The solution would involve:           A new canvas section option that allows report designers to define a "header area" at the top of the report page           Controls to set the header height and content that should remain fixed           The ability to place any Power BI visualization in this area (slicers, KPIs, navigation buttons, etc.)           Automatic scrolling behavior that keeps the header visible while the report body scrolls independently   This feature would transform how users interact with Power BI reports by: Creating a more intuitive, webpage-like experience where navigation and filtering controls remain accessible at all time Allowing users to see the impact of slicer selections on visualizations without losing sight of either element. Enabling report designers to create more cohesive narrative flows through data, as key contextual information can remain visible throughout the exploration process. Reducing user friction and the cognitive load of remembering filter states when scrolling through extensive report The implementation would need to handle responsive design considerations and potentially interact with existing features like drill-through filtering. The header area should remain responsive to different screen sizes while maintaining its fixed position during scrolling.   This feature would be particularly valuable for:             Dashboards with multiple related visualizations that require consistent filtering             Reports with extensive content requiring scrolling             Interactive presentations where presenters need persistent access to controls             Executive dashboards where key metrics should remain visible while exploring supporting details This enhancement would significantly improve the usability of Power BI reports, bringing the interface more in line with modern web design practices and user expectations for interactive data experiences. ... View more

It should be possible for admin to monitor and manage the personal bookmark created by end users. ... View more

Currently we're getting Power BI audit data using shell script per Workspace, App and Report Name. We don't get Page Name. However, we do get usage per page name in usage metrics in PoweBI web.   Need to add Page Name column in audit data to tack usage per page  ... View more

The current card visual forces users to overlap elements or waste copious amounts of time creating custom visuals. The new card feature should give users the ability to create multiple cards in a single container and provide a greater level of customization. ... View more

It would be beneficial to incorporate features from Pivot tables that allow for the expansion and collapse of columns and hierarchical column groups within tabular visuals. This would not only solve the current limitations of matrices but also provide report creators with the flexibility to hide and show rows and columns, saving these settings for future use, thus eliminating the need to scroll through irrelevant data. ... View more

Enabling customized calculations at the query level for subtotals and grand totals would offer greater flexibility in reporting and preserve performance. Efficient organization of control settings to modify the style of these totals separately will empower report creators to achieve their desired appearance, while addressing their need for more control and customization in reporting. ... View more

Imagine a world where report creators can automatically apply slicer and filter selections based on specific logic, revolutionizing data analysis and user experience. This innovative approach eliminates any need for complex workarounds, optimizes slicer functionality, and paves the way for more efficient and effective data reporting. ... View more

When connecting to Power BI Desktop with Snowflake as the data source, queries using the time zone display differently than queries with Snowflake.   We have confirmed that Power BI Deskotp currently restricts the display of time zones in Snowflake, so we would like to be able to import Snowflake queries into Power BI Desktop without differences. ... View more

I would like to request an update to the public information attached below in the Japanese version. The English version is up to date, but the Japanese version has not been updated since 2024/11/20.   JP URL: https://learn.microsoft.com/ja-jp/fabric/database/mirrored-database/azure-databricks-tutorial EN URL: https://learn.microsoft.com/en-gb/fabric/database/mirrored-database/azure-databricks-tutorial   Reason for updating: I confirmed in the English version that a new "Prerequisites" was added. The Japanese version does not have this notation, so customers cannot test it following the correct procedure. ... View more

Millions of whole numbers is insane to scroll through. The only work around is showing the filter pane, which is a whole issue with what they then can see and do and what that affects. If you hide each individual filter except just that one then you have to maintain that across all pages. Plus the Filter pane looks horrible compared to slicers especially the newer slicers. Excel has had a search with whole numbers since it came out. I don't understand why this is so hard to implement. Can you please roll out a search within a slicer for numbers, espcially whole numbers like document numbers or transaction numbers etc. ... View more

Interpreting visuals without a clear legend to indicate logic behind specific styles can lead to confusion and decision-making errors. An idea to enhance clarity and transparency by ensuring legends and tooltips accurately display colors, patterns, and other visual components influenced by logics, would enable report consumers to easily understand the applied logic and make more effective decisions. ... View more

Power BI - MS announcement regarding upcoming events or furute updates are great but it will be also appreciated if company announcement will be possible ... View more

I would love to be able to show/hide a visual based on conditional formatting from a measure. Say I only want to show the tables or matrix on the page if a person is selected from a slicer. I would create measure "Person Filtered = ISFILTERED(Person[PersonName])" Having a formatting option on the whole visual to "show/hide" visual based off this measure would be helpful. The current option I've found is to create a shape object to put on top of the visual and then add a measure to the background color of that shape to make it transparent if a person is selected. The problem with this work around is that you can no longer interact with the visual due to the shape being arranged in front of the visual. ... View more