I'd like to see incremental load for Dataverse.   My specific case - Dataverse is located in another region than my Power BI tenant (that is not going to change in the near future). I have change tracking activated on all tables in Dataverse, so there are plenty of possibilities for the copy job to catch on to that.   We have some transactional tables in Dataverse that makes little sense to full load every time. ... View more

R visuals incorporated into Power BI Desktop is a great feature to have. However, I'm limited by 150,000 rows of data and constantly need to verify or put an alert if certain queries will exceed 150,000 row count to plot / summarize in a specified R visual plot.    Will there be plans to increase 150,000 row count limit in R visuals within Power BI?    ... View more

The new right‑pane auto‑hide layout severely reduces productivity. The old fixed/collapsible panes allowed faster visual editing and better usability. Please allow users to revert to the classic layout or customize pane behavior. ... View more

Currently we can create a shortcut from a lakehouse to an exel file in sharepoint.  However we have to keep refreshing the shortcut to keep it up to data with the data. Can we have an activity type in Data Factory so we can trigger the refresh from a pipeline, similar to the refresh sql endpoint and refresh materialized views activities. ... View more

It would be great if there was an option for admins to have a setting to automatically rerun failed refreshes if they are for specific errors such as the Gateway is unavilable, and for Gateway Timeout errors.  This would help with the need to constantly monitor refreshes and check the error and then rerun.  Another piece to this would be to have a setting to hold off launching scheduled refreshes if the server is busy, this would also cut down on Gateway unavailable and timeout errors. ... View more

Keeping semantic layer open is a future-proof decision. It's the common layer that users and agents need to produce trusted, consistent results. AI/BI dashboards and a whole host of third party tools work natively with Metric Views today.  Regardless of your go forward plan, your semantic layer should work with whatever tools you use.  ... View more

Hello,   It would be good to have the next refresh for dataflows with the REST API. Currently we only get the time of the last refresh but it could be optimal to have also the schedule for further insights.   Thanks ... View more

A standardized naming framework through centralized management for Fabric items similar to one in SQL Server Policy Based Management that enforces naming standards and naming conventions compliance defined by the policy. ... View more

Probelm: I have users who have created Mirroring from Azure SQL DB's (although this problem exists with all mirroring) and if they dont log into fabric often the mirroring breaks.  While best pratice, now, is to use a servce account when creating these types of artifacts.  There isnt any warning when creating them and at this point the only way to correct is to recreate the artifact which breaks things attached to it.   Suggest Solution: Please let me reassign all artifacts to a diffrent owner. ... View more

The ai.translate supports specifying the output language, but the input language can only be inferred, which is prone to errors. It would be nice to have the option to also specify the input language. It could also support a list of input languages for the cases where a column might contain multiple languages. This could help the AI better detect the input language(s) and improve accuracy. ... View more

There must be a way if we download the power BI desktop and be able to publish the report in the workspace where it creates the semantic model for us to repurpose. Helps To minimize Fabric configuration and refresh issues, the Live Connection report should be deployed to the same workspace as the semantic model. Live‑connected reports do not benefit from duplication across workspaces and are tightly coupled to the source model’s security and connection settings. ... View more

Description Current behavior In Microsoft Fabric, workspace retention and recovery settings are configured at the tenant level through the Fabric Admin Portal. The retention period for deleted collaborative workspaces can be configured between 7 to 90 days. This configuration applies uniformly across all workspaces in the organization. There is currently no supported capability to define different retention policies per workspace or per capacity (based on the available documentation and admin settings scope). Additionally: Personal workspaces (“My workspace”) have a fixed 30-day retention period that cannot be modified. Problem statement This tenant-wide configuration introduces limitations for organizations with diverse governance, compliance, and operational requirements. Examples: Some workspaces (e.g., production or regulated environments) require longer retention periods for compliance or auditing. Other workspaces (e.g., dev/test environments) may require shorter retention periods to optimize cost and lifecycle management. Large enterprises operating multiple business units or environments cannot apply differentiated policies aligned with their governance models. Impact Lack of flexibility in governance and compliance enforcement Increased operational overhead (manual processes or workaround strategies) Difficulty aligning Fabric retention behavior with enterprise data lifecycle policies Potential risk of either: Data being deleted too soon, or Data being retained longer than necessary Suggested improvement Provide the ability to configure retention policies at a more granular level, such as: Workspace-level retention configuration Capacity-level retention configuration Priority-based or tag-based retention policies (e.g., Prod vs Dev) This would enable: More flexible governance models Better alignment with enterprise compliance requirements Improved lifecycle management of Fabric assets ... View more

In Power BI Desktop, there is currently no built‑in feature to automatically select a related value in one slicer based on the selection made in another slicer. There is no native capability in Power BI Desktop for one slicer to automatically set the selected value of another slicer. Example: A one‑to‑one relationship between State and State_Capital where selecting State should auto‑select its capital. This requires either: Slicer‑to‑slicer binding DAX‑driven slicer default selection Or interaction‑based auto‑selection logic Currently, filtering alone does not solve this scenario. Power BI currently allows slicers to filter each other but does not allow automatic selection of a related slicer value. Example: Selecting State should automatically select its corresponding State Capital in another slicer. This would improve guided analytics and reduce unnecessary user interaction. ... View more

Ability to browse a report as another user by admin indstead og browsing the model, add an ability on the reports ... View more

When using scorecards in my organization a common use case is to track KPI trends that don't have a due date.  For example sales revenue doesn't have a due date because we aren't planning to go out of business.   Having the ability to turn off due dates or leave them blank for individual KPIs would cause less user confusion.   We finde we either need to maintain the due date, set the due date out to a year we figure "I will be retired or dead by then", or we just tell people to ignore it and have to explain that every time we have a new hire.   I would go as far as to say most scorecard items in organizations I work with don't have due dates. ... View more

I started working with version control and encountered the following error while loading a report from a historical commit. "There's a problem with the definition content in your Power BI Project. Column ‘X’ in Table ‘TableX’ contains a duplicate value ‘’ 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. The current operation was canceled because another operation in the transaction failed" Using version control doesn’t make sense with errors like this. The historical commit contained a different table layout that joined to the fact table via a different column, which made sense and worked in the previous version. In the latest commit, I made changes—the table was restructured in Power Query, and the join is now performed via a different column. The model has been changed. After closing the report and setting the checkout to the historical commit, the report does not open and returns an error, as it was unable to recreate the model and connections saved in the historical commit.   ... View more

Just add a little 'refresh' icon that's crossed out when you disable a query in powerquery with the "Include in report refresh" option. I had a report where one of the tables unknowingly did not refresh for months, leading to some frustrations. Just a simple visual (like when you disable a query loading) would help quite a lot. ... View more

As described here, Solved: Re: Plan module (used to be powertable), single se... - Microsoft Fabric Community I have found an issue with the sorting columns in the plan/powertable module. In a SKU:F8 North Europe, we have master_data_table for our employees, enriched with multiple lookups from other tables. When sorting by a column the plan/powertable module fails to render the field data. ... View more