In working with large data sets, it takes a long time to set up the queries and then apply them to the model, just to do some testing or basic report construction. While it is possible to filter the ...
beneuto1
6 years agoNew Member
At present with any change made you are forced to refresh data before you publish otherwise the changes will not be published. This can be very time consuming and resource intensive for large queries particularly as they end up running twice - once locally and again after the report is published. It is particularly frustrating when running on a low spec PC (e.g. tablet). Please allow for query changes to be published without having to refresh data first.
Recent ideas
Option to Stop Fabric Planning Billing Session After Plan Item Deletion
Currently, a Fabric Planning session remains active for 30 days once triggered. If a user creates a Plan item only for testing and deletes it the next day, the billing session still continues and c...v-dugumarrir139 minutes agoMicrosoft EmployeeNew41Views10likes1CommentAllow Managed Private Endpoint to be disabled/enabled per notebook
Could notebooks have an option to use or not use the workspace's Managed Private Endpoint (MPE)? MPE can significantly increase notebook startup time, even for notebooks that don't need private conn...frithjof_v1 day agoCommunity ChampionNew25Views1like0CommentsJustification Prompts When Downgrading or Removing Sensitivity Labels in Power BI Desktop
Description Currently, organizations can configure Microsoft Purview sensitivity label policies to require users to provide a justification when removing a label or lowering its classification. T...vvargasv2 days agoMicrosoft EmployeeNew12Views0likes0Comments