Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now! Learn more
Hello Microsoft Community,
I have a scenario, that I haven't been able to find answers for as of yet. I am new to Power Query so this might be quite simple and I just don't understand the full potential of Power Query yet.
For my scenario, I grab data from an API. The data comes through as a giant array with many data fields in each section, the simplest ones are date, text, or number values, but some come as arrays or objects, which in this scenarios would be arrays of groups of arrays. The data comes as a JSON file and I use Power Query to organize the data. I am currently working on a small subset which would be the test data.
After I've sorted the data as best I can I come (expanded columns, converted tables, removed columns, etc.) to the issue of these arrays which in query would be lists of lists or lists of records. I can't figure out how to properly extract the information from the list. Specifically, I want to add x additional columns to my dataset. Where each column name is made up of a string field in each record in the list, and the value assigned to that column would be another string field in same record in the list. I was not sure how to do this so instead I duplicated my query and went into each list separately. See picture below.
From each duplicated query, I can now sort out this column and value issue via filtering columns, transposing table, and promoting headers and such. For example, the Code Values duplicate tab, which was a list from the original query looks like this now
Where the column titles (BT-Phase and BT-Project Number) were previously the same labelled values of each record in the list, and the outputs (FEED, TEST) were also another labelled values of each record in the list.
My questions are:
Any help would be appreciated, even if the answer is I'm going down the wrong path for this scenario.
2. Avoid merges in Power Query whenever you can. Instead, let the Power BI data model do the work for you.
The Power BI Data Visualization World Championships is back! Get ahead of the game and start preparing now!