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

OpenLineage lets you trace a large number of ETL jobs that mutates tables, letting you trace changes to tables significantly easier. Databricks Unity Catalog has support for Column Level Lineage and it's highly useful: View data lineage using Unity Catalog - Azure Databricks | Microsoft Learn Databricks Demo   AWS also supports OpenLineage:  Amazon DataZone introduces OpenLineage-compatible data lineage visualization in preview | AWS Big Data Blog It's actually quite easy to get OpenLineage working in Fabric Spark since you already have the JAR pre-installed: Column level lineage in Fabric Spark with OpenLineage and stashing the lineage in Delta Lake | Raki Rahman   All we need is a way to store and query historical state (e.g. in Delta Lake), and a UI component that hooks into the Lakehouse catalog and offers an API on top of OpenLineage schema. The OneLake Catalog UI could look like this:       ... View more

Adding Page-Level Conditional Formatting Rules in Power BI, a feature that allows users to define one rule and have it automatically applied across all visuals on the page. Ideally, it should also support applying the rule across all fields in a row for consistent, row-level highlighting. I’m suggesting this idea because I’ve personally struggled with managing conditional formatting efficiently in my reports. When I need consistent highlighting across a dashboard, for example, marking negative values or high-risk records, I have to repeat the same formatting steps visual by visual and column by column. This becomes time-consuming and hard to maintain. This feature would also help address another limitation: Power BI currently doesn’t support row-level conditional formatting. Page-level rules would be a practical solution that simplifies the process, ensures consistency, and reduces repetitive work for report developers like me. ... View more

Currently, when creating connections for Trusted Workspace Access via Manage connections and gateways, the only supported authentication method is Workspace Identity. Attempts to use Organizational Account or Service Principal authentication result in failed test connections it will be usefull if Organizational Account and Service Principal Authentication are supported for Trusted Workspace Connections ... View more

We need to be able to attach default and non default lakehouses to notebooks in bulk in deployment pipeline rules. It's not scalable to have to select each and every single notebook in a workspace to make the deployment rule, which is the case today. We should be able to select multiple notebooks and make the deployment rule or something similar. Currently we have to run a script after a deployment from dev to tst to prd, in order to change the attached lakehouses. This isn't ideal to say the least. ... View more

Hi We have F256 capacity and we have recently purchased 64 SKUs. Unfortunately, there is no way for us to upgrade the capacity by 64 SKUs, but rather can only jump to the next available one, in your case is F512. This is not feasible option. Provide an option to upgrade the capacity with multiples of 64 SKUs. ... View more

One of the most annoying behavior of report designers is to rename fields in visuals in cryptic way without standards and you won't understand at a first sight which field from which table had been used.     AFAIK (without using any external tool or power bi project - just staying in PBI Desktop), the only thing you can do is to hover fields with the mouse and look at the tooltip that shows you the original field/measure home table and name. for further anlaysis you need to move to the data pane and search it manually. Wouldn't it be nice to have a "Go to definition" that points the referenced field/measure in the data pane that you can activate directly in the context-menu right-clicking the field?     ... View more

Currently, there is only REST APIs to add users to the dataset(semantic model)'s direct access.   To add users, please refer to the API: Datasets - Post Dataset User - REST API (Power BI Power BI REST APIs) | Microsoft Learn To add user in groups, please refer to the API: Datasets - Post Dataset User In Group - REST API (Power BI Power BI REST APIs) | Microsoft Learn   User needs REST API to add users to the report's direct access. This function is needed for automation of adding users to report's direct access.     ... View more

Power BI currently clears selections in one table visual when a selection is made in another, preventing independent multi-visual filtering. Requesting a feature that allows table (and matrix) visuals to retain their own persistent selections so users can click a row in multiple visuals and have all selections remain active simultaneously. This would enable combined filter context across visuals without requiring Ctrl‑click or merging data into a single table. ... View more

Hi all,   It would be lovely if you could setup a linked service between workspaces for Fabric warehouses.    That would mean I could fetch data from multiple workspaces within one stored procedure.    Br,   Emil ... View more

Microsoft added or revamped the "design experience" down to two options only: Power BI and Fabric. Fine. Suggestion #1: Get it to REMEMBER the state I left it in when I closed the browser. I'm starting to drift toward the Fabric experience, but I have to SELECT it every time I open the browser.   Seggestion #2: I like that I can have multiple Workspaces available in the left side navigation. But when I click on one I was hoping to have it OPEN SAID WORKSPACE, NOT give me a hierarchy view which includes ALL OPEN Workspaces. I have to now FIND the workspace I JUST CLICKED ON in that side navigation, and CLICK IT AGAIN. Just open the workspace for me! Even if there is only ONE workspace open, it is still TWO CLICKS to get to the full workspace view.   In the Power BI Experience, ONE CLICK on the Workspace in the side navigation brings up that workspace.  ... View more

Today, Power BI semantic models (datasets/DAX) work well when Power BI is the only BI tool. However, many organizations use Databricks as their lakehouse and need consistent, governed metrics across multiple BI tools, ML pipelines, and APIs. When the semantic layer lives only in Power BI: Logic is duplicated across datasets and tools Governance/security (RLS/CLS, masking) is fragmented Schema changes in Databricks break reports ML/AI pipelines cannot reuse business logic from Power BI models Proposal: Enable native Power BI integration with Databricks Metric View ... View more

There is a system storage option in the workspace settings that displays the size of the semantic model. This feature was available at the workspace level, but we need an option at the tenant level that displays the size of all semantic models across the tenant. ... 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

In one of the projects I'm involved in, we found out that deleting an item is irreversible. When you hit delete, the item is gone and all the data in it as well. There is a retention period for workspace deletion but, unless I've missed something, not for items. In the discussion with the client, we found that a very elegant solution would be to create a separate role that allows for deletion of items. Or, as an alternative, introduce the delete locks as seen within Azure.  In both cases, deleting items will become harder and that is the exact point. I think the option to enable delete protection is something for the admin portal. It should only apply to non-personal workspaces and, from the admin portal, workspaces can be exempted from delete protection. This way, dev workspaces can be a 'free for all' whereas QA and Production are heavily protected against accidental deletes. If you want to go really granular, there could be an option to select Lakehouses to be protected, but notebooks can be deleted. ... View more

Buenas tardes a todos, me gustaria tener un reporte de uso modificacion y creacion de algun archivo de BI ... View more

It would be super helpful to get a connection string in SSMS with the workspace name instead of the very cryptic string you get today : Imagine being able to see: server name : WorkspaceNameDev server name : WorkspaceNamePrd That would greatly improve this experience. I know that you can manually rename them in SSMS, but that is not really good in a larger team setting and makes onboarding of new developers a pain. ... View more

Currently, there is a known limitation where the Download option is greyed out or unavailable when a report or dataset is part of a deployment pipeline and has been deployed from one stage to another. We would like this functionality to be supported, as it would allow us to download the report from a specific pipeline stage and deploy it to other workspaces as needed. ... View more

we have sql endpoint for the lakehouse our workspace identity is added as user in lakehouse of source team, unsure of workspaceid or name, want to connect to it in fabric notebook. Please help ... View more