Skip to main content

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 want to harness the under-the-hood power of the M language. The example below lists two tuples - for ReportedDate and LossDate respectively. On both columns, the function Date.From is invoked, which attempts to convert in input value to a date type.
= Table.TransformColumns( #"Your Source Table",{
{"ReportedDate", Date.From}, {"LossDate", Date.From} })
This works fine for normal dates, but for YYYYMM dates we need to cook up our own function:
= Table.TransformColumns(#"Replaced Value",{
{ "Date",
each Date.From(Text.From(_) & "01") }})
The secret here is in understanding what each does.
It is shorthand for creating a nameless (or anonymous) function, where the underscore character represents the single parameter/argument being passed in by the caller.

The example above effectively says:  "For each value in the Date column, convert the value to text (Text.From) then concatenate the string 01  (to create a text value of the form YYYYMM01) , then convert that text to a date type (Date.From) and put the result back into the Date column."

Give it a try!


Comments

Bryan said…
Hello Mike.
Trying your custom function but in vain
File: filename.csv.bz2 (bz2 format)
Content: filename.csv (# separator)
Please help. I'm really new to the M language
Anonymous said…
Hello!
I'm brazilian. I can't read, speak, or write in English, but I'm always learning from your tips. To write this text I used the translator.
I don't use Power BI either. I use Excel Power Query.
I need to import several .XML files, which are inside .FRE files, which are inside zipped folders. I could not import the .xml files without unzipping. An example of the file is available at https://github.com/msperlin/GetDFPData/raw/master/inst/extdata/FRE_6629_HERC_2010-12-31.zip

Thank you very much

Popular posts from this blog

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. UnzipContents 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: Open up PowerQuery (either in Excel or in PowerBI) Create a new Blank Query. Open up the Advanced Editor  (found on the View tab in PowerBI). Copy-Paste the above code into the editor, then close the editor. In the properties window, rename the the function to  UnzipContents Usage Using the function is fairly straight for...

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, --...