Anonymous
8 years agoNot applicable
Status:
Needs Votes
Add Step Name field when creating Applied Steps
Provide a Step Name field when doing things like adding a column, which automatically names the Applied Step. Make this optional, defaulting to the existing default values if not used.
6 Comments
- a-bsonNew MemberBeing able to see what the "Applied Steps" is being applied to would really help. I cannot keep track of when I removed which column or which column split.
- nishalitNew MemberPowerQuery queries tend to get quite long. Some suggestions on auto-naming improvements that may help manage all the steps: When creating Custom column rather than naming step "Added Custom" use the name of the column set by the user (example user adds column "Difference", the step should read "Added Difference" The same goes for Invoke Custom Function. Add either column or function name into auto generated name For MergeQueries use name of QueryMerged ("Merged Mapping" instead of "Merged Query") Add a setting to remove all spaces from auto names in steps. This will be useful when writing code, as you don't have to use #"" (ex. you can use AddedCustom, not #"Added Custom"). When uding "Group by" function please add automatic name generation for aggregates. It can use the same algorithm as PivotTables use (ex. if we take Sum of column "Value" it shoud automatically populate the name as "SumValue"). Sometimes you need to make Group by with 15+ aggregates. It takes a lot of time to copy all the names.
- nishalitNew MemberCurrently adding a column adds a step labeled 'Added Custom'. This is very generic and not transparent. Rather using the column name that is added to automatically name the column would make it clear what the step does. Now this has to be maintained manually by the designer.
- nishalitNew Member
While performing a new step from UI (for ex Merge) there should be an option to Name that step right away as doing it after wards unnecessarily takes time in case of large number of records. Also after merging during column expansion there should be an option to set new names of columns without creating new step. We can do that by modifying "Expand" step itself by changing new column names but that can only be done after Expand step is executed which is time taking in case of large number of records.
- Regan_J_ReeseNew Member
Adding a comment here since this is an old thread - Especially if you want dataflows Gen2 to be utilized (You should it's cool!) make it less painful to visually audit the steps!
- fbcideas_migusrNew MemberStatus added:Needs Votes
Recent ideas
Support 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...WorkFull2237 minutes agoAdvocate INew2Views0likes0CommentsImprove 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-varunvv1 hour agoMicrosoft EmployeeNew11Views4likes0CommentsDynamic 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_db1 hour agoNew MemberNew223Views2likes1CommentTenant and/or App/Workspace Banner messages- alerts
As a tenant admin - would like to publish banner messages or alerts as needed for the organization in the event of a data load failure, or other messaging that needs to be show to the end user on l...sue_yerly1 hour agoNew MemberNew378Views18likes3Comments