We have configured the table to filter the updateddate on rangestart and rangeend parameters. We have updated the incremental refresh settings on the table. After publishing the dataset for first time it refreshes, later when we do a scheduled refresh of dataset it says one of the key column contains duplicate value. But when i query from the database(synapse) table there are no duplicate records of this value, what could be the root cause? Any suggestions.   Column '<oii>id</oii>' in Table '<oii>ticket</oii>' contains a duplicate value '1FA4377D-4CE2-F011-8543-7C1E52274619' and this is not allowed for columns on the one side of a many-to-one relationship or for columns that are used as the primary key of a table. ... View more

Hello,   I am looking for a way to customize the background color of the Plotarea on a column chart. I need to apply gradient background colors that are dynamic at the same time. I have tried the workaround of importing an image with gradient, but it is not enough unfortunately. Any other ideas or solutions?   Thanks ... View more

In flat table visualization (standard excel export) data is truncated when number of rows exceeds 150k. Only small, easy to overlook info is present at the bottom of excel file "Exported data exceeded the allowed volume. Some data may have been ommited"   In matrix visualizations, the problem with Excel export is exacerbated because Power BI cuts off data not just at the 150,000 rows limit, but it counts the rows multiplied by columns. This means that even at a few hundred rows count excel can be truncated if there are many attributes in the query or a 12-month time series.   It would be extremely helpful to have an interactive warning pop up when the export button is clicked, or to have the information about the data truncation prominently displayed at the top of the Excel file, rather than at the end. ... View more

We are attempting to deploy the semantic model from the Dev stage to the Test stage, but we are encountering an error stating that the dependent artifacts must be deployed first to the target stage. In our case, some of these dependent artifacts are in different workspaces and have different owners, which makes this requirement impractical in many scenarios. If this restriction could be removed, it would make working with the deployment pipeline much easier. ... View more

The user wants to customize default questions on Copilot. We believe that Copilot would be more effective if report viewers could select from prompts that the report developer has predefined, rather than having to type their own prompts. ... View more

  The Problem: The "One Active Relationship" Constraint Currently, Power BI enforces a strict rule: only one relationship can be active between two tables at a once. In complex models (like Fleet Management, HR, or Finance), we often have multiple dates for a single transaction (e.g., Order Date, Ship Date, Delivery Date, and Payment Date). To report on these, we are currently forced to: Duplicate Dimensions: Create "Role-Playing Dimensions," which bloats the model size and confuses end-users. DAX Measure Bloat: Use USERELATIONSHIP to manually activate a path. If I have 10 core metrics and 4 date paths, I have to write 40 measures. This is a maintenance nightmare and makes the field list impossible to navigate. The Proposal: Relationship Profiles I propose a new feature called "Relationship Profiles." Within the Model View, a developer could define and name a "Profile" that specifies which relationships are active for that specific context. How it would work: In the Model View: A new manager to save "Relationship Sets." In the Report View: At the Visual, Page, or Report level, a new property in the Format Pane would allow us to select a "Relationship Profile." The Engine's Logic: When a profile is selected, the engine treats those specific relationships as the "Active" paths for all calculations within that visual’s scope. Real-World Application (Fleet Management): Imagine a Fleet manager wanting to see "Total Expenses." One chart needs to show expenses by Service Date, another by Payment Date, and a third by Disposal Date. Instead of 3 different DAX measures, they would use one single measure and simply toggle the "Relationship Profile" for each visual. The Current "Pain Point" (DAX Example) " Total_Expenses_by_Service_Date = // Purpose: Forces the engine to use the 'Service Date' relationship instead of the default 'Transaction Date'. // Logic: I'm using CALCULATE to override the default active relationship. // The USERELATIONSHIP function is explicitly telling the engine which path to take between the Fleet table and the Calendar table. CALCULATE( SUM( 'Fleet_Expenses'[Amount] ), USERELATIONSHIP( 'Fleet_Expenses'[Service_Date], 'Date_Table'[Date] ) ) " This is the repetitive code we have to write today for every single metric in our model. My proposal would make this redundant! The Value to Microsoft and the Community: Model Efficiency: Drastically reduces the number of measures required in a model. Simplified UX: Clean field lists make it easier for "Citizen Developers" to build reports. Performance: Potentially allows the engine to optimize paths based on predefined profiles rather than dynamic DAX overrides. What do you guys think? Is it time to move past the "one active relationship" limitation? ... View more

At times, the Drill through spills over to a visual since the Drill Through field is used in a different context.  It may not be appropriate to drill through for a different visual.  This can happen when there are multiple visuals which use the Month as an X-Axis.  Blocking the ability to Drill through would be a benefit. ... View more

Hi, Power BI signatures sends emails in English. Please, translate the signature email scontent into Power BI PBIX LOCALE. In the example bellow, it should be pt-BR,    ... View more

It would be nice to be able to copy/duplicate an existing report subscription within in the same report so that information doesn't need to be repeatedly entered manually.   Business case: I have a report with 18 identical subscriptions. The only thing that changes is the recipients and one field filter. Otherwise the date, time, and message is the same. It would have saved me 15-30min if I could have just copied the first one instead of having to create 18 near-identical subscriptions, manually. ... View more

Description Power BI Desktop loads PBIP report artifacts only at open time. When PBIP files are modified externally (Git pulls, merge conflict resolutions, scripted refactors), those changes are not reflected in an already opened Desktop session, requiring manual close and reopen. This limits the effectiveness of PBIP in Fabric‑first, Git‑based, collaborative development scenarios.   Why This Matters (Fabric & Git) PBIP is foundational for Fabric CI/CD and Git integration. In real-world team workflows: Developers pull changes from Git while Desktop is open Merge resolutions and scripted updates modify PBIP files on disk Desktop cannot reload or apply those changes without restarting This breaks collaborative development, slows iteration, and makes applying Git merges to active reports error‑prone.   Proposed Solution Add an explicit “Reload from Disk” command for PBIP projects in Power BI Desktop. Discards in‑memory state Reloads PBIP artifacts from disk Equivalent to close & reopen, but controlled and safe (Optional future enhancement: detect external changes and prompt the user.)   Impact Enables Git‑collaborative PBIP workflows Allows applying merges and scripted refactors without restarting Desktop Improves Fabric CI/CD and developer productivity Increases PBIP adoption for enterprise teams ... View more

A 'select all' function in filters could be very useful. Currently, this function only works for all available values, and unfortunately, it doesn't work after a search; you have to manually select the values ​​you've found. Such a 'select all' function after a search would make working with filters much easier. ... View more

1) Allow User Data Function (python) to be a source type for COPY JOB <== Python is the best to ingest REST API data ( aka the big JSON as result) <== Python deals with Oauth2 access token , loop from parent API , continuation token , block chunks etc ..) <== Copy job mapping interface is mandatory for ERP data ingestion projects   2) Improve the MAPPING interface <== Modernize the schema change management   3) Automatically archive processed flat files on a Bucket <== OK  done folder <== KO problem folder  (add error explanation columns)  ... View more

Problem Enterprise teams need to deploy Power BI/Fabric semantic models via CI/CD and set Snowflake credentials programmatically. Today, key pair (RSA) and robust OAuth setups can be configured interactively, but can’t be provisioned end-to-end through a supported public API in a way that enables fully automated, non-interactive deployments. Missing feature Extend the Power BI/Fabric REST APIs (connections/datasources/credentials) to support: Key Pair authentication (ie Snowflake ) OAuth authentication (ie SharePoint) that works for automation (service principal / non-interactive flow), including a supported mechanism so scheduled refresh does not break due to short-lived tokens. Why it matters Enables real CI/CD for semantic models: create → bind → set credentials → schedule refresh, without manual portal steps. Meets security requirements: eliminate stored passwords; align with modern MFA/SSO policies. Reduces operational risk: repeatable deployments across Dev/Test/Prod, easier credential rotation. Acceptance criteria A documented REST contract to create/update Snowflake datasource credentials with credentialType: KeyPair (and required fields). A documented REST contract for OAuth where refresh/scheduled refresh remains functional without manual re-auth. Example use case Deploy a new workspace + semantic model nightly from Git, then set Snowflake credentials automatically and run a refresh—no human sign-in, no passwords, no manual UI clicks. ... View more

Url option to add as formatting in matrix visual to a particular column option not available. I checked and there is no solution other than adding a column as Hyperlink/url ... View more

It would be great to have a subscriptions button on report objects in workspaces.  It could be grayed out if no subscription was present.  This would allow you to edit the subscription without opening the report or navigating to the notificaitons setting and trying to find there. ... View more

Because there are API limits to calling the Power BI API, it would be great to simply dump this data by default to a lakehouse in the tenant? ... View more

Direct lake semantic models do not automatically reflect schema changes in the underlying lakehouses. (Link)   Metadata can be refreshed by editing the model tables, refreshing the table list, and then saving. Opening and editing all semantic models downstream of a lakehouse every time a change occurs is not a scalable solution.   Please provide a simple way to programmatically refresh this metadata in Semantic Models via a REST API call or similar. ... View more

When you click a visual in Power BI Desktop, it would be really useful to have an option to show only the fields/measures used by that visual in the Fields pane.   At the moment, even with a visual selected, the Fields pane still shows the entire semantic model. In larger models (or when working with shared datasets), it’s hard to quickly see: which tables are involved which columns or measures the visual is actually using   I’d love a simple toggle in the Fields pane, something like: Show all fields Show fields used by selected visual     This would make it much easier to: understand existing reports work with inherited/shared models debug or refactor visuals onboard onto someone else’s report   Feels like a small UX change that would save a lot of time day to day. ... View more

Please make the activties rectangles within a pipeline to be resizable (or at least reponsive to include whole text)   It is relly annoying I can't know which invoke pipeline is which by just looking at the current pipeline without hovering and see the full name.   ... View more