Skip to main content

Reading Zip files in PowerQuery / M

Being a fan of PowerBI, I recently looked for a way to read zip files directly into the Data Model, and found this blog which showed a usable technique. Inspired by the possibilities revealed in Ken's solution, but frustrated by slow performance, I set out to learn the M language and write a faster alternative.


The result of these efforts is an M function - UnzipContents - that you can paste into any PowerBI / PowerQuery report. It takes the contents of a ZIP file, and returns a list of files contained therein, along with their decompressed data:

If you're not sure how to make this function available in your document, simply:

  1. Open up PowerQuery (either in Excel or in PowerBI)
  2. Create a new Blank Query.
  3. Open up the Advanced Editor  (found on the View tab in PowerBI).
  4. Copy-Paste the above code into the editor, then close the editor.
  5. In the properties window, rename the the function to UnzipContents


Using the function is fairly straight forward:
  1. Choose "New Query -> Blank Query".
  2. Open the advanced editor.
  3. Paste the following:
        Source = File.Contents("[Full path to your zip file]"),
        Files = UnzipContents(Source)
  4. Close the advanced editor.
  5. In the Applied Steps, click the configure cog to the right of Source.
  6. Select your Zip file.

At this point you should see a table listing every file that is contained in the zip file you selected, along with a Binary blob of the file's contents. For many file types, like CSV and Excel, you can simply click in the Binary field and PowerQuery will intelligently build all of the steps needed to expose the contents of the file.

Good luck! 

Popular posts from this blog

Power Query: Transforming YYYYMM dates (the quick way)

Accountants. Their unit of work seems to be the month, as if individual days don't exists, or don't count somehow. Nowhere is this better seen than in the notion of the accounting period , which all too often follows the form YYYYMM.  Try converting this directly into a date and Power Query starts making excuses faster than a kid with his hand caught in the cookie jar. The quick solution to this is to understand what Power Query's Table.TransformColumns does, and then leverage this knowledge to transform your YYYYMM values into proper date type columns. Table.TransformColumns As it's name suggests, this handy function allows you to convert the contents of a column from one type to another. The basic syntax is: = Table.TransformColumns( #"Your Source Table", { A list of tuples, specifying the columns and what functions to apply to each value} ) Lists {denoted by curly braces} are something you need to get comfortable with if you

Easily Move SQL Tables between Filegroups

Recently during a Data Warehouse project, I had the need to move many tables to a new file group. I didn't like any of the solutions that I found on Google, so decided to create on of my own. The result? MoveTablesToFilegroup Click here for a nifty stored proc allows you to easily move tables, indexes, heaps and even LOB data to different filegroups without breaking a sweat. To get going, copy-paste the code below into Management Studio, and then run it to create the needed stored procedure. Hopefully the arguments are self explanatory, but here are some examples: 1. Move all tables, indexes and heaps, from all schemas into the filegroup named SECONDARY: EXEC dbo.sp_MoveTablesToFileGroup @SchemaFilter = '%', -- chooses schemas using the LIKE operator @TableFilter  = '%', -- chooses tables using the LIKE operator @DataFileGroup = 'SECONDARY', -- The name of the filegroup to move index and in-row data to. @ClusteredIndexes = 1, --