The if-else version is a lot easier, but I really love how you explain the other version, that's really help to make us understand m language more deeply. Awesome content.
@Hortster3 ай бұрын
I would approach this differently and have the conditions and commissions as a separate table which could be joined to your main table. That way you can keep it all dynamic rather than hard coding values into the advanced editor.
@clubedavid6 ай бұрын
Amazing video. I Start seeing M as a standard programming language instead of thinking of Chinese characters, thanks to you!
@victor_wang_16 ай бұрын
It's cool and clever, but I'd recommend sticking with the normal nested ifs as its more universally familiar. This technique, like much of custom M code, also breaks query folding which creates a different "scalability" problem if you have many records. As a final point (and this is only based on my experience), even ignoring query folding, it wouldn't surprise me if the nested ifs was more performant as I've found that iterating list access can have a noticeable impact. If you have many conditionals, creating an additional table and left joining could provide the most scalability (for non-query folding).
@txreal25 ай бұрын
Yes, tried this "creating an additional table and left joining could provide the most scalability" Thanks.
@EricHartwigExcelConsulting6 ай бұрын
Excellent video! I watched this last night and forgot to comment. But I had so many ideas from watching this video!!
@punit64906 ай бұрын
Error alert: added 6 results for 5 conditions. Anyways great stuff.
@GoodlyChandeep6 ай бұрын
Download the file ⬇ - goodly.co.in/switch-function-power-query The Magic of Working with Lists in Power Query - kzbin.info/www/bejne/b2HEpYuXis11m8Usi=x49Gh1lgJ-Kse79o Tackle even the most challenging data-cleaning problems. Check out the M Language course and push beyond the user interface ↗ - goodly.co.in/learn-m-powerquery/
@spen24316 ай бұрын
💥💥 Nice one, and thanks for sharing. Not convinced it is "easier" than a conditional column though...
@paulwyatt85236 ай бұрын
Thank you Chandeep. What a fantastic technique. Until I discovered your content, I was concerned at how we might provide 'Certified' datasets because they still require the user to understand DAX in order to create their own 'self-service' measures and columns. You PQ SWITCH function is perfect for devs to create really rich 'certified' datasets that users can easily build with. I have a colleague who, after seeing the power of power Query through your techniques, has decided to work in PQ and not in SQL. You really change perceptions. You are also underpinning all of my own best practice solutions at the PQ level so, again, thank you.
@txreal26 ай бұрын
Except with large datasets 😊
@randomguy-jo1vq6 ай бұрын
@@txreal2that is true but with pq you need to be very cautious where to apply which resource intensive transformation step
@sandeepkhawas33676 ай бұрын
You are such an inspiration to thousands who are learning power bi..god bless you sir..!
@barttitulaerexcelbart94005 ай бұрын
Thanks. But if you don't need that so much, you can forget. My alternative: use "Column by Examples. It first starts with = but if you add more numbers at some point the "algortithm" displayst >=. You can then change some numbers in the formula. I don't know if it works all the time, but I just tried out. Looking forward to see your next video.
@mienzillaz6 ай бұрын
Really nice example and I need to thank you not for this particular video, but for everything you did around PQ. Because of you (and BI Gorilla) I started to see PQ almost the way Neo saw the matrix 😅 You won't see bunch of views from me on this account, as I mostly watch you from company account 😂, but I'm there and I'm always recommending you as PQ guru. Keep it coming.
@cemisovs6 ай бұрын
Very good explanation and nice tricks. Thank you for the video! ❤
@rzvnpscl6 ай бұрын
Thanks for your videos, Chandeep. Is there any performance improvement with this approach?
@kaidobor16 ай бұрын
Largest complexity in either approach right now is the redundancy of writing each threshold level twice. With nested if and switch you can avoid this, since after first match the result is selected and that's it. Switch statement does not require, that only one condition is true. With list approach you must provide complete condition, so only one result would match.
@gauravguliani3586 ай бұрын
Not a problem in the first place I see that in a lot of your videos
@joaorataoo6 ай бұрын
Your solution is brilliant and the way you make the explanation simple is amazing. When you were starting to present the solution, I thought you were going to suggest another solution which would be to create a function and call it within the query.
@megabuilds30076 ай бұрын
I was unable to see the importance or efficiency of this approach over nested ifs. Explain please?
@frachiar44446 ай бұрын
me too. I tried to import a table of conditions and results, in order to make this more dinamic, but I failed :-( so, I do prefer nested if
@dssmatus49626 ай бұрын
This is amazing Chandeep, thanks for this. Is this somehow replicable in a way, that instead of hardcoding list, we can use some mapping file instead? Lets say, if another department is keeping excel with those commissions, and I am connecting this to my datamodel, I would like to automate this without me doing any maintenance of hardcoding
@ziggle3146 ай бұрын
Great work! M lists are so powerful. Thank you.
@shoaibrehman99886 ай бұрын
I would say, its a gr8 solution, i hv been in situations and used many nested if, now thankful 🙏 for you. 🎉
@kuuuyajim3 ай бұрын
Thank you for the wonderful explanation. I already have few use cases in mind while watching. 😀
@stefankirst32346 ай бұрын
Watched this video almost immediately after it was posted and today I needed this exact thing. Once again: Thanks Chandeep! Awesome content :)
@GoodlyChandeep6 ай бұрын
Awesome! 😄
@jamesclark20206 ай бұрын
This is neat! Thank you. Power Query M is awesome 😎
@laurentmarc19286 ай бұрын
Already splendid. Something really convenient in DAX Switch function is that the answer comes with the first TRUE answer. Would there be a tweak in this M code to give the position of the first TRUE in the list to even mimic better the DAX Switch? Maybe with a List.First ?
@carlossv29456 ай бұрын
its Amazing the potental of powerquery, regards from Colombia
@alejandraseverino92405 ай бұрын
Your video was very helpful, how can I apply this function if I'm using dates and in between and after specific date?
@olivergarveigh86626 ай бұрын
Your videos are really helpful. I've been able to really improve my powerbi skills so thank you :D Just a quick question if that's okay. I have watched your videos on creating fiscal years but I can't figure out how to get it to show the fiscal period in a line graph. Can you help pls?
@DinoDelight6 ай бұрын
What a great video, great explanation and example, thank you
@kelemi46 ай бұрын
Great video! Curious if you could make this into a user defined function with three inputs: a list of values, list of conditions and list of results that then could be reusable, would be interesting to modify for a default value if no conditions are met.
@miksosnowy10386 ай бұрын
you showed here also how to use something like index + match in excel in an easy way. I think this functionality is for me much more useful than swich. anyway great video, and as always very well explained :)
@ronaldtugume5726 ай бұрын
Brilliant! How do you make it dynamic if the conditions change just as the discounts would equally change?
@kot236 ай бұрын
Nice take on this scenario, I like that it uses lists & table logic instead of nested ifs, feels a lot more like Power Query that way. But is it more readable or user-friendly?
@raimundojs95476 ай бұрын
Perfect! Awesome solution!
@leemorgan80076 ай бұрын
great video and clear instructions to use. Will check out your lists video too as I don't use them currently but think they will be incredibly valuable.
@ThepExcel6 ай бұрын
creative one. thx
@HussainAliNasser6 ай бұрын
Nice video. Wouldn't you run into an error if more than 1 condition is true? If so, is there a workaround for that? SWITCH only evaluates the first true (or false) condition and returns the result.
@Nalaka-Wanniarachchi6 ай бұрын
Nice one 👍 One list lookup another list based on true condition.
@zahir5856 ай бұрын
Brillante ❤ Keep up the hard work my friend✌
@PranayPawar19915 ай бұрын
I still find "nested if" better in this case as it's adding too much of query folding. It is worth comparing how much time it takes in report refresh with a large dataset
@markrobinson74926 ай бұрын
is it just me, or anyone else think the NestedIF will just do fine here
@yaynative6 ай бұрын
Probably depends on the scenario
@roncruise43 ай бұрын
It's you. He's using a simple example to prove it works. For larger complex multi layered nested ifs, it makes sense to use this. My question: is it any faster or slower with millions of rows using this new way? Will it slow down any?
@pawewrona97496 ай бұрын
I am not sure this approach makes things easier here. On top, I see another performance issue on top of the query folding point mentioned below. In your example you have 4 conditions to check, and even if the first condition is already satisfied, your approach still calculates remaining ones. This is unnecessary and doesn't happen when standard if is used. Still, your video shows how great Power Query is :)
@ПавелЛинев-ч7м6 ай бұрын
Отличный кейс. Спасибо. 👍👍
@chrism90376 ай бұрын
Amazing! Thanks Chandeep!!!
@SSi-nq3rt6 ай бұрын
Great 2nd solution, thank you. However, I am a bit unsure why i do not get the first solution of cond. column…. Why wouldn’t it work to add a simple conditional column but using the rule upside down? Like (If greater then 14500 then 0.25 else if greater then 14000 then 0.20 else if greater then 12000 then 0.15…) and so on? Rather then using a condition with „greater then A but smaller than B“? I am sure there is a reason but I can’t see it…
@iankr6 ай бұрын
Very nice - many thanks!
@prabhuji33376 ай бұрын
Does this have any impact over processing speed? Amazing video once again!
@deda1186 ай бұрын
As a beginner, can’t see the benefit of this convoluted solution. But a a learning anyway, thank you.
@RonDavidowicz6 ай бұрын
Great video…any technique that gets rid of nested ifs is a good one! Question: how would you incorporate an Excel table of the different commission levels to make this more end user friendly?
@jonathanheath89036 ай бұрын
Excellent video as usual, for a standard data set (int, text, etc) it’s great. I have to wonder if I can use the idea to test binary\table condition like Excel.Workbook(binarytotable) iserr true,false result being switch to ‘bad file’ or the normal [table]
@RavinderSingh-i6k6 ай бұрын
Nice as always :)
@pthapa556 ай бұрын
You are amazing, thank you for sharing.
@boissierepascal57556 ай бұрын
Awsome and brillant use of lists.
@jimgleason40406 ай бұрын
Awesome video as usual!
@MyAvn4 ай бұрын
Thanks
@jerrydellasala76436 ай бұрын
Would love to see that as a function!
@indradutta41366 ай бұрын
Can you please show me to create a custom WE column using power query. I want start date of week should be Saturday.
@pamphlex6 ай бұрын
Great video, Does it process data faster than a nested if statement?
@Acheiropoietos6 ай бұрын
I find nested if statements very easy to use in m code
@Fannie2uN20106 ай бұрын
Brilliant
@McIlravyInc4 ай бұрын
How can I do this in DAX looking between tables?
@pavelandreev60236 ай бұрын
Really nice! Tnx
@GainerOP6 ай бұрын
Is there a way to have wildcards in your conditions? So a=1200 and b>4000, a=1200 and b=%
@manojkahar57186 ай бұрын
I like this trick, Lot I use nested if. I will replace this trick
@zdzislawkes6 ай бұрын
Hi, thank You very much for great content. I wonder what you said "something simillar to switch function" ;-) Maybe You thought about some functions with Your solution: fx_SWITCH( condition1, result1, condition2, result2, ... , else) ?
@brij265796 ай бұрын
Awesome Use case 🤟 Goodly Rocks 👏
@cdmkk22116 ай бұрын
Can we get by multiplying the two list conditions and Result and sum them?????
@dilipinamdarpatil63016 ай бұрын
Nice 🙏
@RogerStocker6 ай бұрын
2:23 Not sure but I guess the cases below 10000 would result in 25% commission, wouldn't it? I guess this was not the intension.
@bimanroy88656 ай бұрын
The catch all (*) condition is missing
@KuldeepSingh-nq1vi6 ай бұрын
Very Nice and Incredible Video Bro..
@DeviChidambaram-w4m6 ай бұрын
let Conditions = { [Amount] >= 1000 and [Amount] 10000 and [Amount] 14000 and [Amount] 20000 and [Amount] 30000 and [Amount] 50000 } , Boolean = List.Transform (Conditions , each if _ then 1 else 0), Results = {0.1,0.2,0.3,0.35,0.4,0.5} , ZipList = List.Zip ({Boolean,Results}) in List.Sum ( List.Transform ( ZipList,List.Product))
@ramakrishnaravula43506 ай бұрын
Full video on new updates on Dax, power query and pivot
@JJ_TheGreat6 ай бұрын
Awesome!
@nitheshn70196 ай бұрын
Thank you
@ershelin6 ай бұрын
Hello Dear, is it possible to add conditional column in PQ based on parameters from multiple columns. I am asking since it is not working with me. Thanks
@GoodlyChandeep6 ай бұрын
see this - stackoverflow.com/questions/31548135/power-query-transform-a-column-based-on-another-column
@ershelin6 ай бұрын
@@GoodlyChandeep thanks for the feedback. problem resolved.
@giorgitsomaia28126 ай бұрын
Super !!!
@umesh24036 ай бұрын
Amazing...❤
@eslamfahmy876 ай бұрын
🎉 creative 💡
@joaquimcosta9526 ай бұрын
Amazing.
@Rice09876 ай бұрын
First formula is more simplier.😄
@GoodlyChandeep6 ай бұрын
True at the first instance. One could argue that.
@Rice09876 ай бұрын
@@GoodlyChandeep but your example is very good for custom functions explanation.🤗
@ajaykumarthakur32072 күн бұрын
❤
@vijayvizzu16 ай бұрын
Does the length of the both lists, need to be same? Means 1st contains 5 rows, and 2nd list 3 rows
@GoodlyChandeep6 ай бұрын
Yes
@pabeader19414 ай бұрын
Did you add the extra value to the second list just to see if anybody would comment on it? The last .35 has no real purpose...
@salahaldeen79246 ай бұрын
how cool was that
@arpankumar44876 ай бұрын
Hi can you give me a solution why i'm not able to load xlsb file in powerquery window but same data i can load in xlsx format why it is happening.... in binary format file size reduce that's why we save file in binary format....
@aahanavikram076 ай бұрын
Power query uses only xlsx file.
@ershelin6 ай бұрын
this is an awesome video. my below code worked well. however false conditions generates Error. let Conditions= { Text.Contains([Description],"STATIONERY"), Text.Contains([Description],"STATIONARY"), Text.Contains([Description],"FURNITURE"), Text.Contains([Description],"CHAIR"), Text.Contains([Description],"A4"), Text.Contains([Description],"HSE"), Text.Contains([Description],"GIFT") }, Results = {"CORPORATE","CORPORATE","CORPORATE","CORPORATE","CORPORATE","CORPORATE","CORPORATE"} in Results{List.PositionOf(Conditions,true)}
@GoodlyChandeep6 ай бұрын
The conditions need to be mutually exclusive
@ershelin6 ай бұрын
@@GoodlyChandeep noted. however, I changed my approach. in my case "if/or/then/else if and else" works better and easy. well, your videos are very informative and saves my time
@darwisyb2 ай бұрын
I will delete all my queries and follow some from your videos lol
@williamarthur48016 ай бұрын
I thought you were going to zip them, I have a bit of an obsession with list zip.
@GoodlyChandeep6 ай бұрын
That would have produced a nested list. Hard to preview 😕
@sunilkumar84196 ай бұрын
Create video on febric pls
@farooqtahir5383 ай бұрын
Really this is an easy version than nested if???😂😂
@pk51346 ай бұрын
Great content as always! Is there a way you can use list.anytrue or list.alltrue for this?