The #1 Mistake You're Making in Your Queries

[@MissMicrosoft]

Thank you for watching! If you enjoyed this video then you should definitely check out this video next: Power Query Advanced Editor - What Is It and How to Use It? kzbin.info/www/bejne/naKzmZh3haqofpo

[@MarcelitaSuanchita]

You are brilliant!! I was pulling my hair out getting the "Expression.Error: The key didn't match any rows in the table." THANK YOU!

[@MissMicrosoft]

You are most welcome!

[@malchicken]

Thank you @MissMicrosoft for this great summary of the transform file error in example 3 😊. I wanted to suggest that at 3:54 maybe the function “Table.ToRows” could be used instead of a transpose and the Table.ToColumns?

[@kebincui]

That is a good suggestion 👍

[@jeromeastier462]

I will definitely use the dynamic column name and the Table.Combine tricks. Thank you Miss Microsoft!

[@MissMicrosoft]

You’re most welcome Jérome!

[@jeromeastier462]

I will definitely use the dynamic name column trick. Thank you Miss Microsoft!

[@MissMicrosoft]

Glad it was helpful! 😊

[@DuongEng]

Thank you so much. Solved my exact problem!

[@Sumanth1601]

Brilliant 😊 specially the last one Table.Combine was new for me.

[@MissMicrosoft]

Thank you Sumanth! Glad you enjoyed the video 😊

[@djl8710]

Thanks! Another excellent and useful video!

[@MissMicrosoft]

You’re welcome, glad you enjoyed the video!

[@mysterioususer2452]

In my case it was referring to the PowerBI workspace i have used to create the dataflow to which I have connected excel. People who will not have access to the particular workspace, will get this error as well. Error message is not very intuitive if you ask me :)

[@smartlearningoptions7609]

In Example 1 the source data changes every time the refresh is clicked by adding a column , (6:22 timestamp)

[@Gorman-84]

too cool. Thanks

[@kebincui]

Thanks for sharing, really good tips to make querries more dynmic and more accomodating 👍

[@MissMicrosoft]

You’re most welcome Kebin 😊

[@kebincui]

@@MissMicrosoft This is really an excellent video❤. I have a question on the video timeline of 6'21".When you just changed column name to the original table, when refreshed I saw that the table has one added column called "Column1". I am wondering why is that. Thank you

[@MissMicrosoft]

Hi Kebin, you are extremely observant 😊. It's similar to the recursion error that happens when using the Excel.CurrentWorkbook function. To prevent the "Column1" being added in the source data and in the query, load the query to a new sheet, it can be in the same workbook as the source table, just in a new sheet and you shouldn't get the "Column1" issue. Hope this helps!

[@kebincui]

@@MissMicrosoft Thank you for your reply 🌹🌹😊😊

[@MissMicrosoft]

You’re welcome Kebin :)

[@OdelLeal]

Thank you. Great Job. 😊

[@MissMicrosoft]

Glad you enjoyed the video!

[@mjb4365]

I think this is a super cool process, but I am getting an error and I could do with your assistance in identifying the work around. I followed the steps, but I am pulling in data via a SharePoint.Contents loolkup, then navigating to the relevant folder, and then pulling in the latest file that always has the same Tab Name. However, I get the following Error: Can you/anyone assist with this? Expression.Error: We cannot convert Type to Text type. Details: Value=[Type] Type=[Type]

[@saadspawn]

I think maybe the type names ('text' instead of 'Text' and so on) should all be lower case as everything is power query is extremely case sensitive.

[@josephwofford5090]

Good stuff!

[@MissMicrosoft]

Thanks!

[@SynapseC]

Flashing subtitles is not an accessible way to communicate.

[@txreal2]

Miss Microsoft is dynamite 🧨

[@MissMicrosoft]

Thank you 😊

[@thamilanban]

Thank you

[@MissMicrosoft]

You’re welcome Thamil 😊

[@youme7621]

😂😂😂 your highly funny

[@inthelensofthepublic]

Thank you so much. Solved my exact problem!