When a report is marked as "completed" by yourself, there should be an option to review the report from the data source level down to individual fields. This review should help identify which elements—such as tables, columns, and field values—have not been used in the report. You should then be given the option to delete these unused elements to improve performance.
At the outset of building a report, it's not always possible to know exactly which fields you will or won’t end up using. The larger the report becomes, the more challenging it is to manage this. I don't want to manually select and recall every field afterward.
No CommentsBe the first to comment
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_Ku54 minutes agoNew MemberNew84Views10likes1CommentSupport 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...WorkFull222 hours agoAdvocate INew4Views0likes0CommentsImprove 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-varunvv3 hours agoMicrosoft EmployeeNew13Views4likes0CommentsDynamic 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_db3 hours agoNew MemberNew223Views2likes1Comment