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

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

Need to get an warning before starting the fabric trail while working with reports, as after clicking alert icon trial automatically started. ... View more

Need API or Powershell cmdlets which fetches the names of all workspaces and reports, including the users who have access to those reports to CSV file. ... View more

🔹 Problem: Power BI users often need to document transformation steps, DAX logic, and analysis notes, but there’s no built-in way to add comments or notes inside Power BI. This makes it difficult to track changes, collaborate effectively, and maintain reports efficiently. 🔹 Idea: Introduce a "Comment" or "Notes" panel to allow users to: ✔ Add personal notes on transformation logic in Power Query. ✔ Document key insights in data model relationships & measures. ✔ Attach questions & hypotheses for further analysis. 🔹 Impact: 💡 Enhances workflow tracking & report maintenance. 💡 Reduces reliance on external documentation. 💡 Improves team collaboration within Power BI. ... View more

There should be a secure way to pass secrets or keys when making an API call (e.g. web.contents) in Power Query M.   Suggestions:   A) Make it possible to enter and edit secrets in Power Query, similar to how we enter and edit data source credentials in Power Query. Make these secrets encrypted and redacted. The secrets should be available to use as variables in the M code. When entering a secret, we would give it a name, which we can reference as a variable in the M code. We would only see the name, but the value would not be visible (the value would be redacted).   B) Make an Azure Key Vault connector for Power Query, that will make it possible to fetch secrets from AKV and assign the secret to a variable in the M query. This variable can be passed as part of the header in an API call.   C) Make it possible to redact some variables in M, so that we can use secret variables without the value being visible in the Power Query user interface.    The main point is that we want a way to use secured and hidden secrets as part of API calls in Power Query. ... View more

Hi Team,   It would be great if we had full control over choosning the border colour for slicers. (its that grey border) ... 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 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

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

Schema options on publish only apply when the update method is replace. we need same When we append data, changes to the schema should be possible. ... 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

When reserving 64 CUs or more, we should be able to use the F64 benefits (Copilot, report readers without pro license, etc.) on any workspaces assigned to capacities which are backed by the reserved CUs.   Even if we create 2xF32, the workspaces assigned to those F32 capacities should get F64 benefits because these capacities are backed by 64 reserved CUs. ... 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

This idea is a request to provide cross-report drill-through capability for org apps. This means being able to navigate between reports hosted in different org apps. The following sections detail why this feature is important for "report navigation." # Some more details We understand a Power BI report as an item that provides users with insights regarding a specific topic. Sometimes, this report contains a semantic model; sometimes, it does not. Sometimes, the group of users is large, and sometimes, it's just me. This is about the relationships between reports and their connectedness. What this idea is not about: This is not about semantic models or the size of the group of users. This is also not about the seemingly everlasting question of whether to create multiple reports with a couple of pages each or one report with all the pages (on a personal note, I consider a one-report solution worse than the dreaded one-table semantic model). From my experience, it seems that when the number of pages gets beyond 12, it makes sense to spread the pages across multiple reports. # Navigating reports, or supporting the decision-making process of report users One of the many reasons reports exist is the simple fact that they are supporting decision-making. Many of my colleagues have feedback that using the cross-report drill-through feature makes it easy to navigate between reports inside the same app. This is important as it prevents "losing thoughts" because a user has to remember how to get to the next level of detail, look at the current context (the current filters) from a different perspective, or ... With org apps new capabilities will become available that will create even more meaningful solutions, but from my perspective it is necessary to enable navigation between reports located in different org apps but inside the same workspace. # Some reasons to spread pages across multiple reports This is a list of reasons why I suggest using multiple reports to my colleagues (not exhausting): + Completely different semantic models, except a few common dimensions like calendar, organization, or ... + I want to share reports with different audiences, but create only one app (currently I'm creating workspace apps). + Multiple report developers build the solution at the same time. + ... # Resources + https://learn.microsoft.com/en-us/power-bi/create-reports/desktop-cross-report-drill-through ... View more

I would like to be able to enter default values ​​that change depending on the period and without it "locking" the user to the default dates. For example: I would like my report to always display data from the beginning of the current year to the end of the current year and yet allow the user to switch to see the data for 2024 or only certain months in 2023 for example. And if we reached 2026 I would like the default dates to be between 01-01-2026 and 31-12-2026 ... View more

Since Power BI allows the creation of vertically scrolling dashboards, it would be very useful to have an option to pin elements (such as headers, filters, or key metrics) so they remain visible while scrolling. This feature would improve usability and navigation, making dashboards more user-friendly and efficient. ... 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