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
Programmatic point-of-failure recovery for Fabric pipelines
The Fabric monitoring UI already supports Rerun → rerun from failed activity. That capability is only reachable by a human clicking in the portal. Please make point-of-failure recovery available to a...EversonElias17 hours agoRegular VisitorNew16Views1like0CommentsEnable Managed Private Endpoints Support for Microsoft Fabric Capacities Below F64
Managed Private Endpoints in Microsoft Fabric are currently supported only on F64 and higher capacities. Customers using lower capacities, such as F8, cannot establish private connectivity to Azure s...v-tsindhu18 hours agoMicrosoft EmployeeNew9Views0likes0Comments