Forum Discussion
GraphQL mutation from Power Query
The design goal of Power Query M is to take data from a source and transform it into a tabular format that can be consumed by Excel or Power BI, or a Parquet-style dataflow. Nowhere in the design specifications is there a place for "talking back to the data source" (the available options are more like unintended consequences of some of the design decisions). Unlike SSIS and Informatica Power Query is more of a one-way street.
The design goal of Power Query M is to take data from a source and transform it into a tabular format that can be consumed by Excel or Power BI, or a Parquet-style dataflow. Nowhere in the design specifications is there a place for "talking back to the data source" (the available options are more like unintended consequences of some of the design decisions). Unlike SSIS and Informatica Power Query is more of a one-way street.
Truthfully, I've already been working on a VBA solution for this component of the process (ie the outbound traffic). I am consistently surprised by the power of M, and was just hoping to hear some magic. Thanks for chiming in on it, much appreicated.
The more I learn about M the more I like it. It is indeed very powerful. In my opinion it would be easy to add the outbound part and make Power Query a true ETL tool. But I suspect that the designers have no intentions to actually do that, sadly.