Skip to main content
SimilarExport ZIP
100%

[Power Query] return the table at the end of the path eg. xmlPath(XML,{"auditfile","customersSuppliers","customerSupplier"})

✓ Published0🌍 Public
HHugoberry
Last edited Nov 7, 2017
Created on Nov 6, 2017

This example demonstrates a Power Query function that extracts a table from nested XML by following a specified path, such as pulling customerSupplier records from an auditfile. The code shows how to traverse XML nodes using list manipulation and table operations, leveraging Power Query’s M language functions like `Table.SelectRows`, `List.Accumulate`, and `Table.FromRecords`. It handles empty tables by converting them to null values and consolidates child records into a flat table structure. The visualization highlights the query logic rather than graphical output, focusing on data-shaping mechanics within Power Query’s native environment.

AI-generated description

Similar vizzes

Loading thumbnail…

Power Query Table to XML

This example demonstrates a Power Query M function that converts a table into a nested XML structure, using a recursive custom function named `tab2xmlREC` to handle tables, records, and scalar values. The initial sample table, created with `#table(null,{{1,2},{3,4}})` and typed via `Value.ReplaceType`, is transformed into a string of XML elements. The implementation relies on `Table.ToRecords`, `List.Accumulate`, and `Record.FieldNames` to iterate over rows and fields, while `Text.Format` builds the XML tags. The output shows a flat representation for simple values, and the recursive call handles nested tables or records, producing a hierarchical XML string.

HHugoberry
74% match
Loading thumbnail…

Searializing a table into and XML string in Power Query

This example demonstrates how to flatten a tabular dataset into a single XML string using Power Query’s M language. It shows the transformation of a table’s records into nested `<row>` elements wrapped in a top-level `<table>` tag. The code relies on `Table.ToRecords`, `List.Accumulate`, and `Record.FieldNames` to iterate over rows and columns, dynamically generating tags with `Text.Format`. Field names and values are inserted into `<#0>` and `</#0>` placeholders, producing a structured XML output. The approach is purely functional, avoiding loops, and directly serializes the table’s content into a text-based hierarchical format.

HHugoberry
70% match
Loading thumbnail…

PowerQuery an alternative to opening XML files

This example demonstrates how PowerQuery can serve as an alternative to manually opening and parsing XML files. It shows a direct query that uses the `OleDb.Query` function with the `MSDAOSP` provider and the `MSXML2.DSOControl` data source to access an XML catalog. The code specifies a file path, `c:\code\catalog.xml`, and executes the query to load its contents. This approach highlights a practical way to integrate XML data into data-analysis workflows without a separate parser. The visualization makes the data-access method visible, emphasizing the tool's role in bridging XML files and PowerQuery’s querying capabilities.

HHugoberry
67% match
Loading thumbnail…

Gist ba39cf5b6349b2131c577e2e046e8654

This example demonstrates a data-driven approach to XML serialization within the Power Query language, showing how database queries can be wrapped in a custom function. The code defines a let expression that calls the `Value.NativeQuery` function, targeting a SQL Server database named "QueryPower" and executing a stored procedure called `usp_InsertDemoXML` with a binary parameter. The procedure receives an XML payload stored in a variable named `dummy2XML`, which is passed as the `xmlBin` argument. This illustrates a pattern for embedding XML data into SQL Server stored procedures through Power Query, highlighting how native database queries can be integrated into data transformation workflows. The example focuses on the parameter-passing mechanism rather than visual rendering.

HHugoberry
63% match
Loading thumbnail…

Gist 47d998760fa7271ac3157ce7d9555612

This example demonstrates how to query and load data from external sources using Power Query's OleDb.Query function, specifically connecting to a local CSV file and an XML catalog. The code shows two approaches: one using Microsoft's ACE OLEDB provider to read a delimited text file, and another using the MSDAOSP provider with MSXML2.DSOControl to access XML data. The visualization highlights the raw query definitions rather than rendering graphical output, focusing on the data-acquisition layer. Both queries reference file paths on the local system, with the CSV query specifying the file directory and the XML query pointing to a catalog file.

HHugoberry
63% match
Loading thumbnail…

Dummy table serialized as XML binary

This example shows a Power Query routine that serializes a two-column table into a single binary XML document. The code transforms each row into a `<row>` element containing `<key>` and `<value>` tags, then wraps all rows in a root `<table>` element. It relies on the `Table.TransformRows` function to iterate over the input table, while `Binary.Combine` and `Text.ToBinary` concatenate the textual XML fragments into a single binary output. The data source is an in-memory table named `dummy`, and the result is a well-formed XML representation of that table.

HHugoberry
61% match
Loading thumbnail…

Sequence of adding a table (Query4/2/1) to Power BI desktop tabular model

This example visualizes the step-by-step process of adding a new table to a Power BI Desktop tabular model, using a sequence of XMLA commands captured via a gist. It documents the workflow from initial discovery through to relationship creation and verification, with each step represented as a distinct stage in the sequence. The visualization highlights the XMLA command types (create, refresh, discover) and the DAX queries used to validate the model, showing the interplay between table creation, annotation, data refresh, and relationship management in the tabular model lifecycle.

HHugoberry
59% match
Loading thumbnail…

Extracting Power Query queries

This example shows how to extract Power Query query definitions from an embedded Power BI tabular model by reading the model’s in-memory connection string. The PowerShell script first locates the dynamic port number for the local Analysis Services instance by scanning workspace files for `msmdsrv.port.txt`. It then uses the `Invoke-ASCmd` cmdlet to query the `$SYSTEM.TMSCHEMA_DATA_SOURCES` schema, revealing the connection string. The script decodes the base64-encoded `Mashup` portion of that string, writes it to a binary ZIP archive, and uses `System.IO.Compression.ZipFile` to extract `Section1.m`, which contains the readable Power Query formulas. This approach exposes the model’s underlying data-transformation logic without any direct UI interaction.

HHugoberry
59% match