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

Current Pain Point Currently, when using Variable Libraries in Fabric pipelines, each variable must be manually added one-by-one to a pipeline before it can be referenced. This creates significant friction, especially when: Working with libraries containing dozens of variables Adding new variables to an existing library (requires updating every pipeline that needs them) Managing multiple environments with different configurations Proposed Solution Allow dynamic access to Variable Library variables without pre-registering them in each pipeline. Two implementation options: Option A: Link Entire Variable Library Add capability to link a full Variable Library to a pipeline All variables in that library become immediately accessible Option B: Dynamic Expression Function @GetVariable('VariableLibraryName', 'VariableName') Reference any variable from any Variable Library in the workspace dynamically No pre-registration required Enables truly parameterized, reusable pipelines Benefits Benefit Impact Maintainability Add variables once to the library, use everywhere instantly Reduced Errors No more forgetting to add variables to pipelines DRY Principle Single source of truth for configuration values CI/CD Friendly Easier to manage environment-specific configs across deployments Developer Experience Faster pipeline development, less repetitive clicking Use Case Example Imagine a data platform with 50+ pipelines all needing access to common configuration values (connection strings, retention days, environment flags). Today, adding one new variable means manually updating all 50 pipelines. With dynamic access, you update the library once and you're done. ... 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

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

Microsoft Fabric currently provides lineage at the item level (datasets, lakehouses, notebooks, pipelines), but does not expose column-level lineage within Fabric itself. For teams building transformations using: Fabric Lakehouse (Delta tables) SQL Analytics Endpoints Dataflows Gen2 Pipelines / Notebooks there is no way to see how individual columns flow, transform, or propagate between sources and downstream tables/views inside Fabric. Ask: Provide a column-level lineage view directly in Microsoft Fabric, showing: Source column -> target column mappings Transformation paths across notebooks, pipelines, SQL, and dataflows Cross-artifact lineage (Lakehouse -> SQL Endpoint -> Dataset, etc.) Limits: Fabric lineage graph only shows artifact-level relationships No visibility into column-level dependencies Purview does not currently provide complete or end-to-end column-level lineage for Fabric workloads. ... View more

It would be incredibly helpful if Power BI allowed users to share a specific filtered view of a report. Right now, I can open a report, adjust the filters to create the exact view someone needs, and save it as a personal bookmark—but that bookmark is only visible to me. I’d love the ability to save that filtered state as a shareable bookmark and send it to another user without having to engage power BI developers to save the bookmark state as a "global" selection. This would make collaboration faster and eliminate the back‑and‑forth of “which filters did you use?” ... View more

While preparing for the DataViz World Championships, I spent a significant amount of time testing accessibility with NVDA. During this process, it became very clear how important tooltips are for understanding a report, especially when combined with a logical tab order for users with limited vision. Tooltip pages are extremely helpful and visually rich for sighted users. However, in my testing with NVDA, tooltip pages were not accessible at all, as they are interpreted as images and their content is not read by the screen reader. One possible improvement would be to add an alt text field at the page level specifically for pages defined as tooltip pages, with support for dynamic text.   This alt text could describe the tooltip’s purpose and content based on the current context or selection, making the information accessible to screen reader users while preserving the existing visual experience for others. I believe this would be a relatively small addition with a meaningful impact on overall accessibility in Power BI. ... View more

In Power BI Apps, section headers are organizational only, they can’t serve as a clickable destination. To create a “hub” page and still group child items, authors must duplicate the name: once as a section and again as a page/link inside that section. This leads to redundant labels, extra maintenance, and user confusion. Current navigation lets authors add sections, links, and (optionally) one overview page, and the first navigation item becomes the app’s landing experience, but there is no way to make a section header itself open content. ... View more

Power BI should treat A and a differently as mostly these depict different values.    ... View more

With Snowflake's imminent change to deprecating username and password connections later this year, allowing Mirrored database's in Fabric to connect via OAuth would be an essential option for us.   ... View more

The source control panel within a lakehouse lists all notebooks that are new or updated and its not easy to tell at a glance which one(s) you are looking for.  The only fields available are the Item name and Status, and the full name is not visible without hovering over each when there are several similarly named items.     They do not appear to be listed in any kind of date or name sequence, and it is not possible to widen the panel or scroll horizontally to see the full notebook name. Ideally it would be possible to make this panel configurable in size (full window width would be great), and provide extra meta data columns such as the timestamp and user for the last edit, the parent folder, and allow searching/filtering/sorting on these additional columns.  This would make it easy to find and process items when there are many outstanding changes. ... View more

When datasets are created in BigQuery using the BigQuery API without explicitly specifying a location, the API defaults to the US multi‑region. This default behavior causes issues for users need a way to change the default setting ... View more

When I modify the data desination table name in a Git repository and pull the changes into Fabric, running the dataflow from Fabric results in the old table name being used. It's only possible to change the desination table name through the Fabric UI, not the Git code.  ... 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

It would be beneficial if we could connect to the data sources directly from Excel Web. Although this might require the implementation of an on-premises data gateway. By enabling this connection, we can streamline the data work flows and ensure more efficient access to the necessary information. This change could enhance the productivity and allow users to leverage real-time data insights seamlessly. ... View more

Fabric currently supports custom Environments for PySpark notebooks, but Python notebooks (preview) cannot use them. In Python notebooks, the only available kernels are Python 3.10 and 3.11, and the only way to install packages is via %pip install, which is session‑scoped, not reproducible, and not aligned with Fabric’s managed environment model. This creates a major gap for teams who want consistent dependency management across both PySpark and Python workflows. Request Please add support for: Custom Python environments (similar to virtual environments) Attaching those environments to Python notebooks Managing Python‑only dependencies through the Environment UI This would bring Python notebooks to parity with PySpark notebooks and enable reliable, repeatable development without %pip workarounds. Example In PySpark notebooks with an Environment, this works: python from faker import Fakerfake = Faker()fake.name() In Python notebooks, it only works after:   %pip install faker …and must be reinstalled every session. Enabling custom environments for Python notebooks would solve this cleanly and improve the overall Fabric development experience.   ... 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