If you have ever taken a peek into the Advanced Editor window of Power Query, you’d often see multiple lines of M Code. Some quick facts Typically the code starts with a let and ends with an in statement In between let and the in statements you will see intermediate steps taken to transform the data. In this post I want to share the idea of writing a nested let statement, the reason Each step in the let statement acts like a variable You can use these variables (in a nested let) to make your query compact.   See this quick video.. Consider these dates I have this data where Year, Month and Date have been concatenated and I want to create a proper date from this data.   Nested Let Statement in Power Query Although you can do a bunch of steps to set this straight but writing our own let and in statements gives you far greater power to customize the query. I have created a new custom column with the following M Code. let   Year = Number.From(Text.Start([Dates],4)),   Month = Number.From(Text.Middle([Dates],4,2)),   Date = Number.From(Text.End([Dates],2)),   FinalDate = #date(Year,Month,Date) in   FinalDate By creating this column I do get the correct date.   Did we really create a Nested let and in? Let’s peek into the advanced editor and see the code. The custom column created a Nested let & in Power Query. Although the code seems like it is running in multiple lines but there are actually just 2 steps in the applied steps window. Compact and Sweet!     A few More Power Query Tricks Refer to Previous Row in Power Query Expand All Columns Dynamically Create a Dynamic File Path in Power Query Change dates from MM-DD format to DD-MM format Split by Variable Columns in Power Query Replace Error Values in Multiple Columns   .        Automate repetitive data cleaning tasks using Power Query A comprehensive course to learn Power Query to automate all your mundane and repetitive data cleaning tasks in Excel or in Power BI   DOWNLOAD THE COURSE OUTLINE    |    ENROLL IN THE COURSE