When there is a dataflow refresh error, it is possible to access the refresh history using the warning glyph - as well as via the "More options" icon/glyph. Being able to access the refresh history using warning glyph is an obvious way to access the history so that you can get to the CSV file with the failure information.
When there is a datamart refresh error, the refresh history cannot be access via the warning glyph.
1 Comment
- fbcideas_migusrNew MemberStatus added:New
Recent ideas
Reintroduce Tenant/Capacity Switch to Control "Users can create Plan items" Post-GA
During the Preview phase of Fabric Plan items, administrators had access to a dedicated tenant/capacity setting: "Users can create Plan items". With General Availability (GA), this granular administr...Sri-Surendra_Ku2 hours agoNew MemberNew100Views14likes1CommentSupport Fabric SQL Database with workspace-level inbound Private Link
Fabric SQL Database supports tenant-level Private Link but not workspace-level Private Link. Securing a small number of databases therefore requires enabling Private Link across the entire tenant, in...WorkFull224 hours agoAdvocate INew9Views1like0CommentsImprove Relationship UI Wording to Better Reflect Filter Propagation Direction
The current relationship dialog can be confusing because the UI labels "From" and "To" do not always align with users' linguistic expectations regarding filter propagation. As per document : Relation...v-varunvv4 hours agoMicrosoft EmployeeNew16Views4likes0CommentsDynamic ADLS-Gen2 path input for Spark Jobs Main definition file
I would like the ability to add a dynamic input box on a spark job definition's "Main Definition File" "ADLS-Gen2 path". this would be useful to set base and variable paths across all spark jobs...mfink_db5 hours agoNew MemberNew224Views2likes1Comment