Currently, Power BI allows the option to “Show items with no data” for certain visuals, but this functionality is limited when using Line Charts with a Continuous axis type.  Allow line charts to display items with no data while keeping the axis type as Continuous. This would help maintain smooth scaling and date hierarchy formatting without forcing users to switch to categorical mode (which changes labels to raw date values). This enhancement would improve parity between visuals and provide better support for scenarios where users want continuous scaling and visibility of empty periods. ... View more

According to the documentation (https://learn.microsoft.com/en-us/power-bi/developer/visuals/enable-sync-slicers) and Microsoft's custom visuals support, syncing slicers is only supported by single-field visuals: The sync slicers feature only supports one field at a time. If your slicer has more than one field (Category or Measure), the sync slicers feature is disabled.   As a custom visuals company who, more often than not, uses filtering in our visuals, we would like them to be able to sync accross pages just like normal slicers do, but our visuals are never single-field. Moreover, we do not see why syncing by a single field could not be possible in a multi-field visual as long as that single sync field is selected; therefore, we would like to suggest voting for this idea to enable everyone make custom visuals more versatile (or rather, catch up with single-field slicers). ... View more

Paginated reports to automatically pick up the refreshed semantic model data without manual intervention. This feature would ensure consistency between semantic model refresh and paginated report output, improving user experience and reducing operational overhead. ... View more

Hi, the deployment pipelines are represented a convenient and useful feature than using DevOps or Git and I hope that they can be improved as soon as possible. I think in order to deploy a warehouse it it very important that a deployment pipeline is able to follow the order of dependencies between warehouse objects without generating any errors. F.e. a deployment pipeline should first deploy the schemas, then deploy the tables and next the views and so on. A view could depend on another view. Thanks ... View more

New Desktop app update installed an almost white user interface. There is zero contrast which is not good for the eyes. I see where some people have requested a light interface so incorporate an option to select either light or dark theme like in the Office apps. ... View more

To address the limitations of our current slicers, which are less advanced and potentially confusing compared to our competitors, a new and enhanced list and dropdown slicer should be designed with a wider range of customization options, incorporating industry best practices, and include innovative features like the ability to copy and paste lists. ... View more

Need Power BI rest api which list all data sources from all the sematic model at tenant level ... View more

I would like to request the addition of a Kintone connector for Power BI. Kintone Official Website (US) Kintone Official Website (Japan)   By enabling seamless integration, we expect to unlock greator value from both platforms - leveraging Kintone's data capabilities and Power BI's powerful analytics and visualization features. In response to customer requests, we developed and provided a custom connector for Kintone. https://cybozu.dev/ja/id/90125c111898e77ad9a26618/ (Japanese only) ... View more

Users working with reports occasionally encounter the error “Query exceeded memory limit.” However, report creators have no way to determine which specific query caused the memory limit to be exceeded. It would be helpful to have a feature, such as in Fabric Capacity Metrics, to identify which queries caused the memory limit to be exceeded. ... View more

Matrix visuals could significantly enhance the user experience by emulating Excel's intuitive sorting, searching, and filtering capabilities, even for hierarchical columns. This idea would the current limitation in Power BI's matrix visuals, which lack a comparable experience to Excel's established standard for data manipulation. ... View more

Summary Add a simple UI to edit small Lakehouse (Delta) tables used for metadata, configuration, and reference/lookup data. Today, even trivial edits require Spark or SQL, which makes managing these simple tables more cumbersome.  Problem Many Fabric Lakehouse tables are: metadata (jobs, tasks, entities, config) small reference or lookup tables These tables are small, hand-maintained, and operational, not analytical. They often need minor row-level edits, but Fabric has no UI for this. Proposed Provide a grid-style editor UI: Read-only by default, explicit edit mode Edit / add / remove rows (with limits) Validation, confirmation, and audit logging Role-based access Edits commit as Delta ACID transactions. Why This improves operability and governance while avoiding ad-hoc notebooks and SQL ... View more

Currently you can't move items either to the front or bottom once created. This makes grouping difficult. It is possible to be thinking along such lines where after creating a variable you be in the position to move it either to the top, bottom or to any position you wish to group them nicely?  And Possibly to activate or Deactivate the variable without necessarly deleting it.   ... View more

Secondary axes are automatically managed by the system in some cases, making it problematic for report creators with no control over intervals, ticks, and other crucial components, limiting effectiveness of various types of analysis. It would be great if the secondary axis included comprehensive format settings so that greater control over displayed data is provided. ... View more

The Fabric Capacity Metrics App currently retains data (Item History, CU% over time, CU by workspace, etc.) only for the past one month, which limits long-term analysis. To effectively track optimization progress, capacity trends, and governance metrics, customers need access to historical consumption data over longer periods.   Instead of extending the built-in timeframe, the idea is to introduce a connector that exposes capacity metrics so customers can store and analyze historical data in their own storage units (e.g. Lakehouse, SQL DB or Data Warehouse). The connector doesn’t need to expose all data available in the Fabric Capacity Metrics App — it could simply provide key summarized metrics sufficient to deliver insights into capacity consumption trends over time across various factors.   This would enable organizations to create custom dashboards and reports for multi-month trend analysis, capacity forecasting, and optimization tracking, greatly improving administration and governance of Fabric capacities.   A similar approach to the Azure Cost Management connector, which enables users to extract and store cost data for custom and long-term analysis, would be highly valuable for Fabric Capacity Metrics as well. ... View more

Description: When editing the Power Automate for Power BI button visual in Power BI Desktop, the flow picker displays only a list of available flows. It does not indicate which flow is currently bound to the visual. This creates confusion when maintaining reports, because: No flow is highlighted, selected, or marked as the existing connection. The ellipsis menu (“…”) also redirects to the same unfiltered list instead of opening the existing bound flow. This makes it impossible to identify the active flow without triggering it, inspecting JSON manually, or exporting the file. This is especially problematic in multi‑flow environments or where flows cannot be executed safely for testing. Expected behavior: The flow picker should preselect or highlight the flow that is currently attached to the Power Automate visual, or the visual should provide a direct link to the associated flow (as Power BI Service often does). Actual behavior: The picker opens with no item selected. All flows appear identical, with no indication of which one is the visual’s active connection. Steps to reproduce: Open a report containing a Power Automate visual. Select the visual and choose Edit from the visual header or pane. Observe that none of the flows in the list are shown as the currently linked one. Impact: Hard to maintain reports with multiple automation flows High risk of editing or replacing the wrong flow Time‑consuming workaround (exporting JSON, PBIP inspection, or triggering flows) Environment: Power BI Desktop (latest version) Power Automate for Power BI visual ... View more

Enable Incremental Refresh for Power BI Pro users, not just Premium. ... View more

We're using Power BI Embedded in the App Owns Data scenario in our web application. In the Embedded Analytics Playground we can see Export Visual Data Summarized Export Visual Data Underlying What we *need* is to be able to call "Export Visual Data with Current Layout" as is provided by the built-in Export Data options menu item, but without making the user of the embedded application go through the UI (and also be able to style the dialog we present, add logging of who exported what etc. etc.) Is this API available, but no documented? Is there some trick that we can use to invoke whatever the built-in export does?   ... View more

We would like information on which characters are supported or valid for workspace names, in the documentation. There should also be a description that gives an overview of the valid characters for workspace names in the Power BI service when creating a workspace. ... View more

Power BI reports currently do not fully meet WCAG 2.2 AA requirements for Keyboard Accessibility (2.1.1). Some interactive elements, such as tooltips or information boxes for data visualizations that appear on mouse hover, cannot be accessed using a keyboard alone. While screen readers can read the content, keyboard-only users who do not use screen readers cannot access this information. Impact: This creates a significant barrier for users who rely on keyboard navigation, preventing them from accessing all report content and functionality. It also means reports cannot achieve WCAG 2.2 AA compliance. Request: Please enhance Power BI so that all interactive elements, including hover-triggered tooltips and information boxes, are fully operable via keyboard navigation. This change would help ensure Power BI content meets WCAG 2.2 AA standards and supports accessible digital services. ... View more