Fabric Ideas

Can this feature be applied to Excel files like Csv files?? ... View more

The Date filter is not working with the March 2025 Update of Power BI. See attached images.     Works in January 2025 Update.   ... View more

I currently trigger my dataset refreshes using the Power BI REST API. However, to avoid overwhelming the system, I can't refresh all reports at the same time. This means I have to constantly poll the API to check the refresh status of each dataset before triggering more. This approach isn't efficient and puts unnecessary load on both the client and the Power BI service. It would be much better if we had the option to configure a webhook that notifies us when a dataset refresh is completed. That way, we could trigger subsequent refreshes or downstream processes only when needed—without continuous API calls. Please consider adding webhook support for dataset refresh completion events! ... View more

When exporting a Power BI Paginated Report using Power Automate, I would like it to support TSV format as well. Additionally, I want the commas in the numbers to be retained. https://learn.microsoft.com/en-us/connectors/powerbi/#export-to-file-for-paginated-reports   ... View more

I wanted to share some feedback and a suggestion regarding the Purview glossary implementation, based on our experience at our organization. While we appreciate the capabilities that Purview offers for data governance, we've encountered significant challenges with setting up and maintaining the business glossary. Despite the ability to import terms rapidly, there is no automated way to link these terms to the items they represent. Each definition must be manually linked to a data item one at a time, across three screens with multiple user interactions per screen. Given that we have over 28,000 data items in our data warehouse alone, not to mention the additional measures and tables in our Power BI data sets, this manual approach is not feasible for us. The current process significantly hinders our ability to efficiently manage and utilize the business glossary. We believe that an automated feature to link Power BI descriptions to the Purview glossary would greatly enhance our ability to manage data governance and provide a more seamless experience for our users. If this feature is included in the new Purview integrated within Fabric, it would be a significant factor in hastening our move to an F64 capacity. We hope that Microsoft considers this suggestion, as it would be invaluable in addressing the challenges we face and improving the overall user experience. ... View more

Category: Developer APIs / Embed APIs. Description: Currently, when using slicers in the Power BI Angular Component, the Embed API tracks only deselected items explicitly after users choose "Select All." This behavior causes significant confusion and complexity, especially when integrating slicer selections into downstream applications like paginated reports. Specifically, the current implementation: Does NOT explicitly indicate when slicer selections are inverted. Requires developers to manually maintain and subtract deselections from a complete set of potential values, which is cumbersome, error-prone, and difficult to maintain, particularly with large datasets. Proposed Improvement: Introduce an explicit property (e.g., isInverted: true) within the filter response object provided by the Embed API. This would clearly indicate when a slicer is in "inverted mode" (i.e., "Select All" except certain items), significantly simplifying data handling and downstream report processing. Benefits of this Feature: Reduces complexity and improves reliability of the integration with downstream systems, such as paginated reports or middleware. Eliminates manual, error-prone logic currently required for interpreting slicer states. Enhances developer productivity by providing clear and semantic slicer state information. Improves scalability and maintainability, particularly important when handling large datasets or complex reports. Real-World Scenario (Driving this Request): Working closely with a customer (N-able) who has identified this limitation as a significant roadblock, currently requiring substantial development workarounds or middleware logic. Clearer API semantics would greatly streamline their processes and reduce ongoing maintenance overhead. Additional Context & Community Feedback: Community discussions indicate similar frustrations (Example Discussion). A straightforward API improvement here would benefit the broader Power BI Embed developer community. ... View more

With the debut of DAX Query View and TMDL Script View, there should be an API to retrieve these files.   This capability would enable organizations to automate testing and deployments by programmatically accessing DAX Queries and TMDL scripts.   For example, a Notebook could iterate over semantic models in a workspace, retrieve DAX Queries for testing, and execute those tests using semantic-link. If tests fail, teams could take corrective actions based on the results. ... View more

Currently, the scheduled refresh of the usage metric semantic model will be disabled when the refresh fails for 4 conesctive times & we do not have an option to manually re enable it . The only option we have is to delete & recreate the semantic model. This will be challenging if we have custom reports on top of the semantic model. Also, as the failures may occur due to password expirations it would be challenging to delete and recreate the semantic model everytime Hence we would request for an option to manually re enable the semantic model's scheduled refresh ... View more

OPENROWSET function can read the files from Azure Data Lake storage or Azure Blob storage.  It would be useful to enable OPENROWSET to also read files form Fabric One Lake and access the files in Lakehouse /Files area. ... 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

In an App, one can create a section and under that section have several reports. However, there is no second level section. In other words in would be nice to have "sub sections" and organize reports by different areas in a section. For instance, in our company we would like to have something like:   Operations (section)      Drilling (second level section)          Report 1          Report 2          ...           Report n      Accounting (second level section)          Report 1          Report 2          ...           Report n Planning (Section)        USA Planning (second level section)          Report 1          Report 2          ...           Report n       Europe Planning (second level section)          Report 1          Report 2          ...           Report n   That way it is much easier to organize our Apps. ... 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

In our setup, we work with multiple environments (Dev, Test, and Prod), each represented by its own workspace. To streamline deployment via pipelines, we keep Lakehouses and Notebooks named identical across workspaces.   Previously, when opening a Notebook, we could clearly see which Lakehouse it was connected to, including the workspace name it belonged to.  This made it easy to identify if a Notebook was referencing, for example the Dev Lakehousem while working in the Prod workspace. We could then simply disconnect and re-add the correct reference.   However, with recent UI changes, only the Lakehouse name is visible, not the workspace it is contained in. This creates confusion when multiple Lakehouses share the same name across different workspaces. Even when adding a new source, the explorer does not clearly show which reference is from which workspace. This makes it far too easy to mistakenly remove or connect the wrong Lakehouse especially in production environments.   This seemingly small UI regression significantly affects productivity and introduces potential risks during deployment or debugging. Please consider restoring the visibility of workspace names to Lakehouse references in Notebooks.   Before: Screenshot from google E.g: Workspace Dev -LakehouseA -LakehouseB .... Workspace Prod -LakehouseA -LakehouseB ....   After:   Only lakehouse name   We use same lakehouse name in each workspace   ... 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 great if we could specify a folder to create a new item in (such as a lakehouse). Right now it seems you can only create new items in the root folder of the workspace when using the REST APIs. ... 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

Need an API to get the list of  all data sources of the reports  available in the  capacity. ... View more

Problem Statement: Currently, the Azure Data Factory REST API connector only supports REST endpoints that return responses in application/json format. However, many modern and legacy REST APIs legitimately return responses as text/plain (e.g., health checks, keys, tokens, or plain status messages). When using such APIs, the REST connector fails to process the response, making it incompatible with otherwise valid REST interfaces. Although it's possible to work around this by invoking a function activity or using custom logic, this introduces unnecessary complexity and overhead. Proposed Solution: Enable the REST connector to support text/plain responses by: Wrapping the plain text in a valid JSON document (e.g., { "response": "raw text here" }), or Exposing the raw response as a string under a default or user-defined property. Business Value: Simplifies pipeline development: Reduces the need for workarounds like function or web activities. Expands connector compatibility: Supports more REST APIs natively, including those used in DevOps, monitoring, security, and identity systems. Improves performance: Avoids additional activities or dependencies that increase execution time and cost. Enhances usability: Makes ADF more flexible and developer-friendly. ... View more