BLUF: The idea is to create the functionality in Power BI Desktop, Fabric, Power Platform and wherever else, to create parity between Power Shell and Power Query by creating a Power Query Gallery and allowing developers to (1) publish M extensions to the gallery, and (2) import M extensions to either Power BI, Fabric or Power Platform.
DISCUSSION:
- The Power Shell Community is able to use the Power Shell Gallery to publish and share Power Shell code
- Install a library is straightforward and my productivity with Power Shell is greatly increased by it
- Power Query (M) does not have similar support, but I venture to guess that the community would come together to support it if functionality was there to support it
- Power Query Extensions provide a way to add custom M code to pbix file currently, although I am not sure it is widely used
IDEA:
- Create functionality where M is used to import extension files to wherever it needs to go so that you can use custom extensions easily whenever M is used.
- Similar to the concept of an environment in Python, the code could be local to the project (.pbip), the workspace, or the solution (Power Platform dataflows).
- For Power BI desktop, create the functionality to easily search the Power Query gallery and import extensions to your project or add extensions that are global for your Fabric workspace
- For Fabric/Power BI Service workspaces, create the functionality to easily add packages that are global for that workspace and well as easily searching the Power Query gallery and importing extensions
- For Power Platform, create the functionality to add M extensions to your solution for the Power Query Gallery and any dataflows in that solution should be able to use functions in that extension
on:
List Slicer Bug
NaamaTsafrir
on:
Detect and control unused Fabric/Power items in th...