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

"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

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

Description: I would like to propose an enhancement to the Power BI slicer functionality to allow users to select multiple values using keyboard commands (e.g., Shift) after performing a search. This feature would mimic the functionality available in Tableau, where users can easily select a range of values by using a keyboard command in combination with mouse clicks. Example: In Tableau, after searching for specific values in a filter, users can hold down the Shift key and click on the first and last values in the list to select all values in between. Similarly, holding down the Ctrl key allows users to select or deselect individual values without affecting other selections. Implementing this feature in Power BI would greatly enhance the user experience by providing a more efficient and intuitive way to make multiple selections within slicers, especially when dealing with large datasets. Benefits: Improved Efficiency: Users can quickly select multiple values without having to click each one individually. Enhanced User Experience: Mimicking familiar functionality from other tools like Tableau can make the transition to Power BI smoother for users. Increased Flexibility: This feature would provide users with more control over their data selections, making it easier to analyze and visualize data. Thank you for considering this enhancement. I believe it would be a valuable addition to Power BI's functionality. ... 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

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

We have a dataset which for which I am working on a visualization. With incremental refresh, each time I publish a change I have lost historical data. From what I can see there is no way to run refreshes as if I was starting from a past date. If the data I am looking at is all timestamped, I think it would be a great feature to be able to run the queries on different timeframes in order to populate this historical data ... 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

Hello Team, This is to inform you that when we use the composite model and want to refresh it every 15 minutes, due to limitations, we can only refresh it every 30 minutes. However, in direct query mode, we can refresh the dataset every 15 minutes. We are requesting you to add the same feature in composite mode to refresh the dataset every 15 minutes. Thank you ... 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

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

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

Make it possible to see storage consumption at Item level in the Capacity Metrics App.   At the moment, we can only see storage consumption at Workspace level, and this makes it difficult to pinpoint exactly which items (lakehouses, warehouses) consume most storage in our workspace.   Displaying the storage size (gigabytes) at Item level would increase the usability of the Storage page in Capacity Metrics App. ... View more

In Azure we give our resource a name using a standard naming convention. For Fabric one of our capacities is named something like xxx02prdxxxfab001 (xxx1 = our prefix, prd = production, xxx2 = solution abbrivation, fab = fabric resource, 001 = capacity number 1). We are using this naming convention, because properties of a resource can change and you don't want te get stuck with a resource name with a specific name, that might not be valid in the future.   But this name is now also the name of the capacity in Fabric, where, in Fabric, we actually want to rename it to a name more recognizable to it's properties, like "F64 production capacity". The option is already there in Fabric on the capacity settings, but you can't change the name after clicking the pencil button. We are using multiple capacities, so it would be usefull to have the ability the rename the capacities.   ... View more

Issue Summary: Fabric pipelines cannot be deployed in a specific order, leading to dependency conflicts. This requires manual intervention to ensure pipelines correctly reference each other. Recommended Workaround: Temporarily rename all .platform files for pipelines with dependencies to platform to prevent automatic sync and deployment. Deploy pipelines sequentially, ensuring dependencies are deployed first. For the pipeline you're deploying: Rename its corresponding platform file back to .platform. Update the pipeline-content.json file to use the correct pipeline ID of its dependency (retrievable from the URL in Fabric). Select Update to sync the pipeline from the repository to Fabric. Delete the existing pipeline folder from the repository to avoid conflicts. Commit the updated pipeline from Fabric to the repository, choosing Keep current content. (Note: This process works even if the pipeline ID in the .platform file remains outdated.) ... 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

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

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