15:34 If it makes you feel any better, I made the same very stupid decision! 😂 38:17 Every time I see you snip like this, I think ‘I should do that!’ - and then I forget to… 39:30 Go To -> Special -> Formula is your friend here!
I agree I really liked the storytelling of the case here. On the first part I had the same worry about the size of the table but did a few checks and looks like it was always 30 so I could reference the columns like normal. Funny we did the set up for the first half of the case exactly the same. Always a small error or lapse of thinking can cost you the case like for you the odd or even. Every case I feel there's something too so you're not alone there! Your pathfinder method for 5 is interesting, but seems time consuming compared to the way I did although my way was a bit manual. 6 was a very nice clean approach. Our approaches are actually very very similar in terms of how we think about solving the problems. I have my vid up if you're interested.
Yeah, it was totally unnecessary, a simple indirect of endpoint - indirect of startpoint would have worked! I will definitely have a look at your solution, thanks for the heads up!
11:58 For Level 3 I solve it into a single function like @DimEarly but lost lot of time. My function form Example3: =LET(tab;SORT(SORT(SORT(FILTER(tRez;tRez[Battle]=H120);3;1);5;1);6;-1);poz; XMATCH(G120;CHOOSECOLS(tab;3)); INDEX(CHOOSECOLS(tab;3);poz+1))
![Felix "Unfair" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/Oswujxm2Ag0/mqdefault.jpg)
15:34 If it makes you feel any better, I made the same very stupid decision! 😂
38:17 Every time I see you snip like this, I think ‘I should do that!’ - and then I forget to…
39:30 Go To -> Special -> Formula is your friend here!
It's incredible what the pressure can cause!
And I definitely need to become proficient in tables and managing other excel tricks like the "go to"!
I agree I really liked the storytelling of the case here. On the first part I had the same worry about the size of the table but did a few checks and looks like it was always 30 so I could reference the columns like normal. Funny we did the set up for the first half of the case exactly the same. Always a small error or lapse of thinking can cost you the case like for you the odd or even. Every case I feel there's something too so you're not alone there! Your pathfinder method for 5 is interesting, but seems time consuming compared to the way I did although my way was a bit manual. 6 was a very nice clean approach. Our approaches are actually very very similar in terms of how we think about solving the problems. I have my vid up if you're interested.
Yeah, it was totally unnecessary, a simple indirect of endpoint - indirect of startpoint would have worked!
I will definitely have a look at your solution, thanks for the heads up!
11:58 For Level 3 I solve it into a single function like @DimEarly but lost lot of time. My function form Example3: =LET(tab;SORT(SORT(SORT(FILTER(tRez;tRez[Battle]=H120);3;1);5;1);6;-1);poz; XMATCH(G120;CHOOSECOLS(tab;3)); INDEX(CHOOSECOLS(tab;3);poz+1))
Very nice formula! I still feel 10x more confident in building expanded models rather than diving into big LET/LAMBDA anyway :)
@@LorenzoFoti yes is more time consuming to put all staff into a single cell. Good luck for next rounds!