I have been using PQ for yrs and always rename steps to reflect their purpose. But, i had no idea about the insert of dummy steps via the fx button and the inserting of special chars via the Wi +. button. Great tip, thanks!
These are fantastic tips! However, by creating those dummy steps for documenting won't overload the query since more steps are created - particularly for big queries or queries with many merges?!
Another great tip from the expert.. love this technique and will surely use this.. keep it up Wyn.. looking forward to more out of the box tips and tricks
Thanks Wyn. Do you have any tips on how to document the overall business logic that is coded into these queries? I do something similar to your idea in documenting the steps, but many a times, I find it hard to figure out where a certain key logical step occurred - so, I have to click through multiple queries to figure that out. Any ideas on how to document all the queries and their connections?
1:15 If my findings are accurate, it divides the age in days by exactly 365,, not +/-365,25, difference that becomes considerable for higher year figures (leap years).
While helpful in documenting inside the Excel File/Power BI file, there is also the case of documenting outside the file. One of the disaster recovery techniques is still a 'paper' (real or digital) to retain and explain the complete process of any. I am a little more interested in suggestions in that form of documentation.
I think documenting the overall purpose externally is useful, documenting the detailed process generally is unnecessary and adds little value and quickly becomes outdated as these processes rapidly evolve
If I make a refrence quary for each related step (grouping them), will I slow the prosess down, or will it essentinaly just be "one" devided quary? Thx again! 👍👍👍
