I see there are threads about this from years ago but it's still not really sorted. My team all need to work on a .pbix file, not necessarily at the same time, but due to home working and not being visible to each other, that has happened on occasion. Why does Microsoft not use the "Somebody is currently working on this file. Open a read-only copy?" in Power BI that they do in Word and Excel? It would save a lot of trouble for us when multiple people are inadvertently working on the file at the same time and one person has to exit without saving and redo their work. ... View more

Currently, Power BI Table and Matrix visuals always open scrolled to the leftmost column by default, which is inconvenient for reports where the most important data is on the right side. Please add an option to: Set the default scroll position (leftmost, rightmost, or specific column). Remember the last scroll position when navigating between report pages. This feature would significantly improve usability for wide tables and financial or time-series reports. ... View more

  Hello everyone, I've been working on a Microsoft Fabric pipeline that dynamically triggers different activities (like notebooks or dataflows) based on parameters passed into it — specifically using item IDs to determine which path to execute. Everything works perfectly when CI/CD is not enabled on the dataflow. I am able to pass in the Dataflow ID dynamically through a variable, like so:    @variables('gold-dataflowid') However, once CI/CD is enabled on the dataflow, the exact same pipeline setup fails, even though: The Dataflow ID is correct The workspace ID is properly set The pipeline logic is unchanged The activity is using the proper variable references The error returned is a generic failure message that provides no clear insight into the issue. Even manually executing the dataflow (with CI/CD enabled) using dynamic input fails in the same way — suggesting that the issue is tied directly to CI/CD behavior. 🔍 What I’ve Observed: ✅ Dynamic execution of dataflows via variables works when CI/CD is disabled ❌ The same approach fails when CI/CD is enabled ❌ Manual runs in CI/CD mode also fail ⚠️ There is no clear error output, making this difficult to troubleshoot ✅ Why This Matters: Dynamic pipelines are a key part of reusable and scalable data engineering workflows. Not being able to trigger dataflows dynamically when CI/CD is enabled significantly limits: Multi-environment support (dev/test/prod) Modular pipeline design Automation workflows in modern dataOps strategies 🙏 Feature Ask / Bug Fix: Please consider: Clarifying whether this behavior is expected or a limitation Providing more descriptive error messages when dataflow execution fails under CI/CD Enabling support for dynamic dataflow execution with CI/CD enabled, similar to how notebooks or other activities can be driven with runtime variables Let me know if anyone has encountered this issue or has found a workaround!   Note: I used chatgpt only to paraphrase the context so people would better understand it. I didn't generate the whole idea out of chatgpt. Thanks, Charan Basireddy ... View more

Auto-saved options are not that good, we need to go back to older versions if someone messed up.   Version history should be there ... View more

Dear Power BI Team, I would like to propose a new feature for Power BI Desktop: the ability to manually refresh metadata used by INFO.VIEW functions (such as INFO.VIEW.COLUMNS, INFO.VIEW.MEASURES, etc.). Currently, when I update metadata in my model (e.g., a column or measure description), changes are not immediately reflected in summary or dictionary tables built with these functions. The only ways to force a metadata refresh are by making and undoing a change in the model, or by closing and reopening the file. This can be disruptive, especially when frequently updating documentation or model details. Suggested functionality: A manual "Refresh Metadata" button or command allowing users to instantly update all INFO.VIEW-related metadata views without needing to reload data or restart Power BI Desktop. Alternatively, automatic refresh of metadata whenever there are changes to descriptions, expressions, or other model details visible to these functions. This feature would improve workflow efficiency for documentation, QA, and model governance, especially for large or frequently changed models. Thank you for considering this enhancement! ... View more

Why should it be a guessing game as to which DAX queries work in Direct Query mode in Power BI. We often build our dev models in Import mode (it's too time consuming to use direct query for this), but then find some DAX queries no longer work.  I looked for a list of DAX queries that are supported in Direct Query mode only to find that this information does not exist.  This is basic level technical documentation that should be made available to users. ... View more

can you kindly look into the case sensitive & case insensitive issue between desktop & query editor, where query editor can able to recognize the difference between upper & lower case characters/string, however when it comes to desktop it is considered as one single record by default, hence we are loosing the records in such case. kindly look into it please ... View more

It would be really useful if every Visual came with an ID and that in Dax there was a function which could pull current ID of the visual it runs in.    Within the formatting of the visual would be It's ID number automatically generated.  Then there would a function say VisualID() with following format: - VisualID(ID of visual) This could then be used to allow if\switch statements to execute based on visual they are in.  This would allow Measures to be created for example which change the title of a visual, without the need for multiple measures. (Or creating a table just to differentiate between each visual.) See code below as an example: - Switch( True, VisualID = 1, "Active Tickets", VisualID = 2, "Closed Tickets", VisualID = 3, "On Hold Tickets", ) ... View more

Description: Currently, Power BI does not offer a direct way to set fixed column widths for individual columns in a Table visual through the Format pane. Users must manually resize columns or resort to editing the report.json file in .pbip projects, which is not user-friendly or scalable. Proposed Enhancement: Introduce a “Column Width” setting under the Format > Specific Column section for Table visuals. This would allow users to: Set a fixed width (in pixels or DIUs) for each column. Optionally toggle auto-sizing on/off per column. Preview column width changes in real-time. Apply consistent formatting across reports without manual resizing. Benefits: Improves usability and precision in report design. Reduces reliance on manual tweaks or metadata editing. Enhances accessibility and layout control for enterprise reporting. Aligns with formatting flexibility already available in Matrix visuals. Use Case Example: A user wants to align multiple table visuals across a report page with consistent column widths for better readability and visual harmony. Manual resizing is error-prone and time-consuming, especially when dealing with dynamic data or multiple visuals. ... View more

Currently, the following public documentation provides a list of operations that are recorded in Microsoft Fabric audit logs: https://learn.microsoft.com/en-us/fabric/admin/operation-list   However, all operations are listed in a single table without being categorized by item type (e.g., workspace, report, dataset, etc.), which makes it difficult to locate specific operations.   It would be extremely helpful if Microsoft could provide a version of this documentation where operations are organized by item type—similar to how audit log activities are categorized in Microsoft Purview. Such a structure would greatly improve usability for audit analysis, access control, and operational planning.   Thank you for considering this enhancement! ... View more

While AI Insights support is available in Dataflow Gen1, it is currently not supported in Dataflow Gen2. Since enabling AI Insights in Dataflow Gen2 would make it a more useful tool, we propose this as a feature improvement. ... View more

Add targets within the Pins dashboard. currently shows growth unit and pins but nothing in relations to targets.  ... View more

We are in the process of on boarding a new supervisor and changing schedules around at our Smuckers/Palumbo site. Per Tyler Abbot, he wanted us to submit for this change here.   Current Assignments: First Shift - Paula Mcnally Second Shift - Jason Bush Weekend Shift - Michael Feller   Needed Changes: First Shift - Michael Feller Second Shift - Will Hicks Weekend Shift - Jason Bush   Let us know if you need anything from our end. These changes have already occured in the LMS environment.   Thank you! ... View more

A Drill-Down action that expands the heirarchy of a Matrix table - this can be used to configure a button. Currently, the drill-down buttons are very hard for users to see/navigate to in the Web.  ... View more

See Attached Image. Quick Overview When working on large Power BI models, it’s easy to end up with 50, 100, or even more queries in Power Query. These come from all kinds of sources and transformation steps, and the list gets long fast. At that point, just finding the query you’re looking for becomes a real hassle. Right now, the only option is to scroll through the list manually—and in big projects, that’s just not practical. Why This Would Help Models grow quickly: staging queries, reference layers, intermediate logic—all stack up fast. Scrolling through a huge list every time to find a query breaks flow and wastes time. A simple search/filter option in Queries Pane would make it way easier to work efficiently, especially under deadlines. The Ask Would love to see a search bar added at the top of the Queries pane in Power Query. Just something lightweight to help quickly jump to a query by name. That’s it—nothing to do with loading data or transformations, purely about improving authoring experience. I've included a screenshot as well to help visualize the idea. ... View more

In the current configuration: Dataset is hosted in a Premium Per User (PPU) workspace. Report is deployed to an Embed Capacity (A1) for embedding into a website. This setup leads to inconsistent behavior due to resource governance limitations: Although PPU allows up to 100 GB per dataset, the semantic model memory limit in A1 capacity is capped at 1 GB. When the report accesses the dataset from PPU, the embed token generation process is constrained by the PPU capacity limits, resulting in failures and unreliable embedding. Additionally, this architecture causes inefficient license utilization: Internal users with PPU licenses are underutilized because the embedding relies on A1 capacity, not leveraging the full benefits of PPU. ... View more

Currently, it's confirmned that fabric operates in UTC. This causes issues when hosting few paginated reports which are time sensitive, causing confusion in the report audience. Should have an option to set the timezone in fabric so it matches with local time (like the option for subscription time zone) ... View more

Please do what you can to make EVERY connection type in Fabric support Service Principal authentication, AND make it so that the Secret (Service Principal Key) can be stored in an Azure Key Vault. Many Fabric solutions involve connections to other data sources inside an organization's data landscape. Right now, there is a mix of authentication types available to the various connections. Service Principals are great, but they secret has an expiration date. When that expiriation is met and a new Secret generated, EVERY connection that uses that Service Principal need to be updated. For a moderately sized solution, that could be several or dozens of connections. Needing to edit the Secret on each one is not sustainable. But by allowing the Secret to be stored in an Azure Key Vault, and making that Key Vault reference available in Fabric, now there is only ONE place to refresh that Secret and all (Service Principal) Connections can utilize it. ... View more

We are having issues inititiating the mirrored tables for large tables. There is very little info on the net about removing the timeout. It would be nice if that is not a restriction for seeding new large tables ... View more