UserStory: in 99% cases we use previous name as input for current step - very annoying and difficult to read, not comfortable to type and edit (it's always a double work). Proposal: reserve some sp...
Very necessary for the scenarios where we need to move steps around, and risk breaking references that are hard to debug in an already very-hard-to-debug language. Since order of operations is intrinsic to power query, relativising references would make it far easier to work with code rather than the restrictive GUI.
Would be good to be able to traverse multiple steps backwards in cases where the step before is not the table you intend to operate on, but retrieves some value you need, e.g.:
let
Step1 = loadData(...),
Step2 = ([params...]) => [function definition],
Step3 = Table.AddColumn(# - 1, "NewColumn1", each Step2([params...]))
in
Step3
