I would like a style slicer that pops up a calendar that allows selection by a single date, rather than a range of dates. ... View more

Problem: Currently, when a dataset is connected to a Lakehouse as a datasource in Power BI Fabric, it defaults to a cloud connection mapped to SSO. In embedded mode, reports built on these datasets fail due to a lack of identity, as they do not inherit authentication from the service principal. To resolve this, users must manually adjust the datasource settings via the Power BI service https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-fixed-identity   Proposed Solution: Introduce a new REST API or extend the current API functionality to allow programmatic setting (or re-setting) of the connection to the service principal, including updating datasources. Benefits: Automates the process, reducing manual intervention Minimizes downtime for embedded reports Enhances developer experience and deployment efficiency Ensures consistency in authentication settings across different environments Impact: This feature will significantly improve the workflow for organizations embedding Power BI reports using service principals, ensuring seamless and automated datasource authentication. ... View more

"Copy visual as image" feature available for the report in the Power BI service where as it is not available for embedded report. Need to implement "Copy visual as image" feature in the embedded report ... View more

Make it possible to write SparkSQL without having a Default Lakehouse.   With 3- or 4- part naming, i.e. [workspace].[lakehouse].[schema].[table]    there should be no need to attach a Lakehouse in order to use SparkSQL.   Needing to attach a Lakehouse is annoying and adds extra complexity. ... 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

Fabric Data Warehouse allows reading Parquet and CSV files using the OPENROWSET function. However, it does not support external tables that reference Parquet or CSV files (CREATE EXTERNAL TABLE (Transact-SQL) - SQL Server | Microsoft Learn). This limitation hinders the straightforward migration of Polybase external tables from Synapse dedicated/serverless pools or SQL Server. The only available workarounds for migration involve either converting Parquet/CSV files to Delta Lake format or rewriting the code to use OPENROWSET, which lacks the same security model. As a result, migrating from Synapse or SQL Server to Fabric Data Warehouse requires data or code conversion.   Supporting external tables with Parquet and CSV files is crucial for seamless migration and ensuring compatibility with other SQL Server/Data Warehouse offerings. ... 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

It would be really useful to have security settings to show or hide individual report pages. Currently, audiences control access only at the report level, not per page. ... View more

PBIP Format is available since 2023 for Power BI Desktop regular version. Power BI Desktop for Report Server is missing this new Format, forcing developers still to use PBIX Format. Supporting PBIP for On-Prem Development would enable teams to use git for their development process. ... View more

This idea is about requesting navigation between the item types report, notebook, and real-time dashboard (rti-dashboard). The following chapters detail why this feature is important for "report navigation." Some more details The new item-type org app is great by itself, but there are two reasons why it stands out, at least from my point of view. The possibility of having multiple org apps inside a single workspace will make architecting solutions for large audiences more simple. However, being able to leverage the "mechanics of sharing" that we Power BI people know (and after all these years, I'm still impressed by its simplicity) will make consuming the new item types real-time dashboards (rti-dashboard) and Fabric notebooks a breeze. Power BI's "mechanics of sharing" will make Fabric's item types consumeable by audiences that have not been using Power BI in the past or are missing content that is different from the item types report or dashboard. Cross-item communication   But then I think "communication" between the item types report and rti-dashboard, report and notebook, and notebook and rti-dashboard is vital to close in on decision-making excellence even in the age of LLMs and Copilot. I imagine actions that allow users to navigate from a report to a notebook or to a real-time dashboard, but it's not just the navigation that I imagine; I also imagine passing the current filter context to the notebook or the rti-dashboard. Some reasons why cross-item navigation is useful These are only some possible use cases that could be answered if this communication is possible. What is the current state of ... passing the filter context from a Power BI report to an rti-dashboard When is the next breakdown expected ... passing an object of interest to a notebook that executes complex algorithms to predict an outcome  ... ... View more

Power BI's alerting feature can send notifications when a set condition is met, but it should be able to send notifications again when a condition changes from a set condition to a further set condition. ... View more

System tables on the data flow should be excluded when the user retrieves data. These system tables pertain to implementation details rather than the information itself. ... View more

Currently, when connecting to a lake house from the OneLake data hub in Power BI Desktop, it is not possible to display a data preview of each table.   It would be helpful if real-time data, such as that from the data hub, could also show a preview of the retrieved data at that moment, so I hope you will consider expanding this functionality. ... View more

We need insights into the storage consumption of active files and soft deleted files.   The Capacity Metrics App's Storage page should have the ability to show the storage size of soft deleted files and the storage size of active files. And the total.   Today, it is not possible to differentiate between storage size of soft deleted files and active files in the Capacity Metrics App. ... View more

The primary axis are outdated and require significant improvement when compared to Excel. This makes it difficult for report creators and often leads to problems when trying to manage and style them effectively. By offering more format settings, greater control over displayed data can be provided, especially if axis ticks, new gridlines, and separators are also included. ... View more

Currently the server name for SQLDB (and DW) is a double GUID of {tenant-Id-workspace-id.}database.fabric.microsoft.com   This causes a lot of issues as 1. This is impossible to remember 2. We ahve no way to distinguish test from PRD   We request user frirnedly DNS Names like  Prodata-Sales-DEV.database.fabric.microsoft.com   This would help clearly label an worksapce as DEV or PRD and avoid confusion and make the platform easier to work with., ... View more