Fabric Ideas

Need API for Power BI gateway creation for Sql connections while using authentication method – service principals ... View more

There is no way to monitor the load times at the moment for paginated Reports as the Load times of Paginated Reports are not integrated into the Usage Metrics. Idea: Please incorporate the Load Times of Paginated Reports into Usage metrics or provide another way to monitor these times ... View more

When exporting to an Excel file with “Data in current layout” in the report visual, I do not want the row with the filter content to appear in the bottom row. ... View more

Fabric Warehouse currently supports the OPENROWSET function, which allows you to read CSV files directly. However, when it comes to reading JSON files, you need to use a workaround. This involves treating JSON files as text or CSV files and then using OPENJSON and JSON functions to parse the JSON documents. While this method works, it is considered a hacky workaround and not very elegant. To improve this, Fabric Warehouse should add a native support for JSON in the OPENROWSET function. This would eliminate the need for tricks with OPENJSON and JSON functions, making the process of reading JSON files more straightforward and elegan.   The current workaround for reading json is: SELECT TRY_CAST(JSON_VALUE(jsonContent,'$.orderId') AS INT) AS orderId, JSON_VALUE(jsonContent,'$.orderDate') AS orderDate, JSON_QUERY(jsonContent,'$.orderDetails') AS orderDetailsObject, JSON_QUERY(jsonContent,'$.deliveryAddress') AS deliveryAddressArray FROM OPENROWSET( BULK 'https://<storage>.dfs.core.windows.net/datalakehouseuk/raw/json/orders.json', FORMAT = 'CSV', FIELDTERMINATOR ='0x0b', FIELDQUOTE = '0x0b' ) WITH ( jsonContent VARCHAR(500) ) AS r;   ... View more

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

I have three workspaces -- DEV, UAT, and Prod.  Within these workspaces, I have several independent projects - each with their own deployment schedule and processes. The current pipeline process makes it nearly impossible to deploy these projects independently of one another because a human being has to rebuild the pipeline for every deployment.  Not only that, but the difficulty in rebinding notebooks, semantic models, etc as part of the deployment makes the whole pipeline process a non-starter. It would make the deployment pipeline process much easier/better if I could: 1) specify what data pipelines, data flows, notebooks, semantic models, reports, environments, and lakehouses need to move between workspaces 2) specify what data within lakehouses needs to be copied 3) rebind any notebooks, semantic models, and reports In short, I want a pipeline package for each project that I can define within the source workspace(s) ... 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

Events should trigger when a date is selected from the slicer using dataselected/visualClicked event ... View more

I have a Fabric Application containing a number of related Dashboards.  I would like to be able to set filters at the application level that work as though they are passed into each PowerBI dashboard on the URL string as a ?filter= query string parameter. This will enable me to have the application pre-filter each dashboard without having the end user have to go in and filter each one independently. ... View more

As a capacity administrator, it would be extremely helpful to see all the scheduled notebooks/refreshes/dataflows/pipelines/etc in one place -- ideally with a perspective on what impact these jobs may have on the overall capacity of the workspace. Right now, anyone can set up a job to run whenever they want... and most everyone just leaves it at default -- which means twice a day (1am Pacific Time and India Time) my capacity gets dropped to its knees. Knowing what's scheduled (and who scheduled it) will enable me to mitigate this issue. ... View more

When I write a spreadsheet into my lakehouse files folder, I would like to be able to download it without having to install the onelake storage explorer.  Please provide a download link for files in the lakehouse files folder! ... 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

"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

Hi Team,   Can we replicate the ADLS Gen2 Lifecycle Management options to OneLake please.   eg If a customer wants to build an archival type solution with data retension policies we can't recommend using OneLake as an alternative to ADLS Gen2 storage account as it doesn't have the same lifecycle policies to allow us to delete files.   We have this idea to bring add ability to do tiers but we need the liefcycle policy option on top please https://community.fabric.microsoft.com/t5/Fabric-Ideas/Add-storage-tiers-to-Fabric/idi-p/4508264   Thanks, Darren ... View more

On behalf of user request posting the idea into this forum. Reference thread link: You guys memorize your workspace guids? - Microsoft Fabric Community   Users are struggling with workspace visibility — especially when switching between dev and prod environments. The current setup hides workspace names, leaving users to rely on GUIDs in the URL, leading to mistakes and frustration. Key Issues: Workspace names are hard to access, disrupting workflow. Users resort to memorizing GUIDs to avoid errors. Frequent environment confusion increases the risk of production mistakes. Suggested Improvements: Color-coded environments (e.g., red for prod, green for dev) for instant recognition. Persistent workspace name display in a visible, fixed location. Replace GUIDs with readable names in URLs for better clarity. These changes would improve user experience, reduce errors, and create a safer, more efficient development process.   ... View more