As part of the new Recent data module, I would also like to see Recent Connections so that I can connect to another table from the connection I just used. ... View more

Often when I am writing queries I end up having multiple queries within the same script in Fabric Warehouses/ Lakehouse SQL endpoints. This results in this nice dropdown for navigating between each of those queries but as more queries are included in the script, it gets to be a lot. Currently I leave comments in my code like "Result 1: Query Subject" but that means I need to track down which query is which still and if I reorder the queries then I need to update the query numbers. What if there was a command or a wrapper that could be a flag to name these something set by the user (or dynamically) so that it would be easier to click through results?   ... View more

Problem Description When using Microsoft Fabric Data Factory’s Copy Activity with an OData v4 source, any column defined as an enum type in the OData service is silently dropped during schema inference and data ingestion. This occurs because Fabric Copy Activity performs strict metadata‑based type validation and only materializes properties that map directly to supported primitive types. Since OData enums are logical types rather than primitive scalars, they are excluded from the inferred schema. This behavior results in incomplete datasets, unexpected data loss, and inconsistent ingestion outcomes—especially for systems that rely heavily on OData metadata and enum‑based domain modeling. Expected Behavior Power BI, which uses the same OData v4 metadata document for schema discovery, successfully handles enum types by gracefully coercing them into strings when no native type mapping exists. This demonstrates that a metadata‑driven fallback is technically feasible and consistent with Microsoft’s broader OData tooling ecosystem. The expected behavior for Fabric Copy Activity is to follow the same principle: If an OData enum type cannot be mapped to a native Fabric type, Automatically fall back to string, Instead of dropping the column entirely. Why This Matters Many enterprise OData services rely on enums to model business concepts such as status, category, priority, workflow state, and other domain‑specific classifications. Losing these fields during ingestion creates several issues: Data loss: Critical columns disappear without warning. Broken lineage: Downstream transformations and semantic models cannot rely on stable schemas. Inconsistent behavior: Power BI and Fabric interpret the same OData metadata differently, causing confusion for users who expect parity. Workarounds are impractical: Switching to Web API is not viable because it lacks metadata, type information, and relational structure required for OData‑based ingestion. Requested Enhancement Implement a fallback mechanism in Fabric Copy Activity so that: OData enum types are automatically materialized as string columns. Schema inference remains metadata‑driven and predictable. No columns are silently dropped due to unsupported logical types. Benefits to Microsoft Fabric Users Consistent behavior across Microsoft products (Power BI and Fabric). Improved reliability of OData ingestion pipelines. No unexpected schema loss, reducing operational risk. Better support for enterprise OData services, which frequently use enums. Reduced need for custom workarounds, manual schema overrides, or alternative APIs.   Thank you for reading 😉 ... View more

When the user clicks on show as table on a visual in report, and the user does not want to see the total option. Can this be made as customisable? ... View more

Feature Request: Allow Users to Permanently Set the “Simplified” Layout as the Default Title: Add an option to permanently set the “Simplified” layout as the default view on the Power BI Home page Description: Currently, the Power BI Home page displays the new Copilot layout by default. While users can manually switch back to the “Simplified” layout via the selector at the top of the Home page, this preference is not saved permanently and must be reapplied frequently. Recommended apps are not immediately visible to new users. The official documentation only confirms the manual toggle but does not provide a way to persist this setting.  This creates friction for users who prefer the classic, cleaner layout for daily work. Requested Enhancement Introduce a persistent user setting that allows individuals to set the “Simplified” layout as their default Home page view. Optionally, add a tenant‑level or admin‑level setting for organizations that want to define a default layout for all users.  Benefits Improved usability and reduced manual steps A more consistent and predictable user experience Better alignment with user or organizational preferences Enhanced onboarding and orientation for non‑technical users  Background Recommended apps are not immediately visible to new users At the moment, no option exists to make the simplified layout the default. Microsoft documentation mentions only how to switch manually, with no support for saving the preference long‑term ... View more

Description Currently in Power BI, when a visual contains multiple columns or measures, filtering values within that visual often requires writing complex DAX expressions or creating additional measures and calculation logic. I would like to suggest a feature where users can filter values directly within a visual column, similar to the filter/drop-down functionality available in Excel tables, without relying on DAX. Proposed Feature Once a visual is prepared with multiple columns: Each column should have an Excel-like filter option Users should be able to: Include / exclude specific values Apply simple conditions (equals, greater than, less than, blank, non-blank) Filter at the visual level only, without affecting other visuals Example Scenario A table visual contains: Area Town village Activation Count Qualification Status Instead of writing DAX to: Remove blanks Exclude zero values Show only qualified Towns The user can simply apply filters directly on the relevant column inside the visual—just like Excel. Business Impact 🚀 Reduces dependency on complex DAX 🧠 Improves flexibility for business users ⏱ Saves development and maintenance time 📊 Makes Power BI behave more intuitively for Excel users 🔧 Enables faster ad-hoc analysis without model changes Current Limitation / Workaround Requires additional DAX measures Calculation groups or field parameters add complexity Not user-friendly for non-technical report consumers Expected Outcome Power BI visuals become more interactive and flexible, enabling self-service filtering while keeping the data model clean and simple. ... View more

From the Fabric Monitor, we need an option to either select ALL pipelines or select multiple pipelines at once, with the ability to perform bulk actions such as Cancel or Rerun. This feature would greatly improve operational efficiency, especially when managing large workloads or responding to failures across multiple pipelines. Thank you! ... View more

It would be very useful to make the Power BI Desktop role management window modal and resizable so that the names of the RLS, the roles, and the involved resources can be displayed correctly and fully.   https://community.fabric.microsoft.com/t5/Issues/The-Manage-Security-Roles-window-in-Power-BI-Desktop-should-be/idi-p/3174180       ... View more

Enable defining multiple named color palettes within a single theme file. Additionally, allow assigning a specific palette to individual visuals, so different visuals in the same report can use different predefined color pallete. ... View more

Allow adding custom named colors to the theme file, in addition to the built-in structural colors. These custom colors should be accessible: In Power BI Desktop UI to pick the colors In DAX expressions by referencing the defined color name ... View more

The theme JSON file allows defining color palettes with more than 8 colors. However, Power BI Desktop UI only supports up to 8 colors when creating and selecting theme colors. Please extend the Desktop UI to support longer palettes, including: Creating and editing palettes with more than 8 colors More importantly picking from the full palette when choosing individual color ... View more

One major pain point for Power BI developers is the current workflow when working with live enterprise data via the Service. Currently, if the data resides on-premises and is only accessible through a gateway, developers have to: Build a report locally in Power BI Desktop Publish it to the Power BI Service Connect it to the customer’s gateway for live data Make query or transformation changes in the Service Download the updated report back to continue development This back-and-forth is cumbersome, time-consuming, and breaks the natural local development workflow. Proposal: Allow Power BI Desktop to directly leverage the On-Premises Data Gateway. Developers could work locally against live data, edit queries and transformations, and test reports without constant uploads and downloads, while still maintaining enterprise security. This small change would greatly streamline development, improve efficiency, and make working with live enterprise data much more intuitive. ... View more

Please enable on the web version being able to Copy format and paste it in any other chart. It's very basic but so time saving since I use the web version only  ... View more

Hello,   I have been exploring options in Power BI for creating reports with GIS data for plotting markers as well as shapes, both representing different features from a table. Something like this:     1. Shape maps: I could not find an option for markers in Shape Maps even though it let me add a custom map using a TopoJSON file.   2. Azure maps: Allowed either markers or boundaries at a time. There is a Reference Layer field under Format visual tab, which has Polygons and Points sections, but I did not find an option to display both of them together on my custom GeoJSON. Also, the legend parameter, which decides which feature gets different shades, allows only one feature at a time.   3. I have also tried the trial version of ArcGIS Online (Organizational Account) but could not find options for displaying differently shaded points and polygons, simultaneously on a custom GeoJSON. I have tried the join layer as well.   If articles for this already exist, please point me to them! I have come across a similar question in Power BI Forums so maybe it would be worth implementing? ... View more

@power BI  I would like the option to save to a single file someplace the default options for visuals I use often.   I prefer the dropdown for slicer. If I can have my preferred settings saved (with the file imported on opening PBI) it would save me opening an older report (or template) and fishing for that tweaked visual that worked so well. Recreating when you can't remember where that example is can be time wasting.   Something as simple as my default numeric display format is 0,0.00;(0,0.00)  and I would always like decimal numbers in my matrixes to default to this. One saved option per visual, ability to assign to the profile open kind of thing.   Or take an example from the older Delphi methodology and allow me to save a visual with current settings to a personal list (as another tab on the Build panel) with a name associated, such as a Matrix saved as AcctMatrix. (All those stored in a single file I can tuck away somewhere that can be shared among users who feel the same or want to use the same options. Clear text edited XML or something would be bonus.) ... View more

Currently, ownership assignment is not supported while creating new goals via Rest API. This can only be done by editing the newly created scorecard from the Power BI UI and then assigning user/users. We require a feature where we would be able to assign an owner to the goal while creating the same via REST API. ... View more

I need to be able to isolate AMD server vs Intel bookings and billings per week. Currently, I can get the server data inside of the Supplier Manager Operational Metric Dashboard. I would like to be able to see the AMD vs Intel. Thank you!  ... View more

Currently in Microsoft Fabric/PowerBI dashboards, it is only possible to lock all objects at once. This can be limiting when working with complex dashboards that contain multiple overlapping or closely aligned elements. I would like to suggest the ability to lock individual objects (e.g., tiles, visuals, text boxes, images) instead of only providing a global “lock position of all objects” option. This feature would provide the following benefits: Prevent accidental movement of specific visuals while editing other elements Avoid unintentionally selecting objects that are layered behind others Improve precision when designing complex dashboards Increase overall usability and efficiency during dashboard editing A per-object lock option (for example via right-click menu or properties pane toggle) would significantly enhance the editing experience and reduce frustration caused by accidental changes. ... View more

I would love to be able to add a URL link in Fabric Task Flow comments. Then I can link to my Azure DevOps board, or other project management or documentation tools from within the Fabric Task Flow.   At the moment, I can paste a link, but it doesn't become something that I can click on. ... View more