It would be helpful to be able to set up a distribution list of those to send refresh failure notifications to. Currently, only the owner receives an email, but we have several administrators that re...
melissa2
6 years agoNew Member
When a calculation error exists somewhere in the model, a refresh can't be performed. Suggestions: (a) Check calculations first before refreshing tables to speed up the failure getting returned. (b) Improve error messages so they are much more clear - currently they are very generic. (c) Show a warning indicator at table level if any column has an error, which will save time from expanding every single table to hunt for issues.
Recent ideas
Allow us to rename fabric data agents published to m365
If we use deployment pipelines to promote fabric data agents between dev, test/UAT, and prod fabric workspaces, we need to keep the name of the fabric agent the same in each workspace. If we want to ...PeterDaniels4 hours agoAdvocate IIINew182Views0likes2CommentsMake workspace and item session persistence optional
Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...TeemuMultanen5 hours agoAdvocate INew293Views47likes2CommentsSupport Encrypted Sensitivity-Labeled Excel Files in Power Query
Description Currently, Power Query Online and Power Query in Excel are unable to access encrypted Excel files. Excel files with sensitivity types other than Public or Non-Business can be encrypted a...ewarstdhyjugkhi5 hours agoMicrosoft EmployeeNew21Views6likes0Comments