Often when understanding the Power Query code built by others Power Query's default step names provide little context. You must hunt-and-click your way through steps to find that exact column... crack open the code in advanced editor, copy the code to a text editor and search (especially if the number of steps is a lot).
The time spent understanding what Power Query steps are doing can provide a significant time investment. That time investment leads to slower delivery to customers and poor maintenance. This is the antithesis to DataOps which emphasizes that “We should strive to minimize the time and effort to turn a customer need into an analytic idea, create it in development, release it as a repeatable production process, and finally refactor and reuse that product.”
With the advancement of Co-Pilot, this product should provide the ability to (1) suggest comments to add to an applied step, (2) rename the applied step to something with better context and (3) add comments to custom functions.
In addition, the advanced editor should have a search feature.
on:
Importing data (or drag and drop) from Fabric Lake...
anshulsharma
on:
Integrate Fabric Eventhouse with Azure AI Agent se...
on:
change button slicer selected item color