Currently we can use Power Query menu options to do lots of things in PBI Desktop without having to know M Code. This has been a huge help in advancing the popularity of PBI Desktop. My suggestion is to expand this ability to nested tables. After performing a Nested Join or Group By, many times you end up with a Table Column that you need to add a field to like an index, or filter it to a max value, or several other things BEFORE expanding the column. The M Code to do these operations is not as straight forward and finding books on the subject are not readily available. My thought is you click in the first cell to show the full table in the window below the parent table, and then the menu option's "focus" switches to the child table allowing you to add columns, filter columns, do all the same stuff. When you close the child table view, the menu options then operate back on the parent table as they do today.
1 Comment
- fbcideas_migusrNew MemberStatus added:Needs Votes
Recent ideas
Data Pipelines - Run only selected activities
For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities. For example, I'm working on editing ...frithjof_v6 hours agoCommunity ChampionNew612Views11likes2CommentsSemantic model connection bindings should be in source control (Git)
Semantic model data source connection bindings should be source controlled. A semantic model can contain multiple data source references, each of which can be mapped to a separate Fabric data connec...frithjof_v14 hours agoCommunity ChampionNew17Views1like0CommentsBulk changing column names in Visualizations Pane
We often use raw/api column names or measures with a set nomenclature to be consistent and to keep track of them but we do not want to display these names in the visuals. Currently we have to change ...vishal14019717 hours agoFrequent VisitorNew6Views0likes0Comments