Could you please give me solution, I have two tables charges and payment my requirement is payment comes month on month based on charge bill month. Suppose jan2024 charge billed $100 so $40 payment comes in jan2024 , $20 payment comes in feb2024, $15 comes in March 2024 and so on so. Bill ID is unique column in both table. How to calculate and show in matrix as Row Charge. Jan24. Feb24 mar24 Jan2024. $40. $20. $15 Feb2024. $60. $25 Please give me solution in pawar bi.
Hi, awesome video! Question for you, given the same dataset what if the “Job Name” requirements is for multi-select? How would you approach it? Thanks in advance.
@@SQLBI I think you have answered the point in your response to Tommy Hao below. You explain that COUNTROWS returning 0 would be considered FALSE and any other number as TRUE, so it is actually returning a Boolean when used inside FILTER.
considering that the levels are integers, wouldn't it be sensible to use something like: GENERATESERIES ( 1, MAX ( EmployeeSkills[Level] ), 1 ) instead of FILTER & ALLNOBLANKROW? I have a feeling that ALLNONBLANKROW has a gap in a scenario when no employee one would have skill on level 2, just 1&3
What book would your recommend for power query that is the equivalent to the "Definitive guide to DAX". In other words.... to learn everything about DAX = Difinitive guide to dax AND to learn everything about Power query = ?????. Specifically interested in the "M language" and "Power Query Performance." Thanks for all the great content.
it makes me feel better when i see Alberto stop dead in his tracks mid formula to stare into the distance and go "fuck, how am i going to do this". thank you for sharing as always ❤
Why does the first summarize solution work? You are using Jobreqs table which is not filtering skills table (which would filter Employee skills) If you use Skills table it would make sense but the many to one relationship from Jobreqs to Skills should not work. There is also no expanded table concept or anything applied. Could you please elaborate on that? Thanks
I love learning from you! As discussed in the end, I'd be a bit worried about performance with larger datasets like 100000 employees, 3000 open positions, an average of 10 skills per employee and 5 levels that we distinguish. I'd address this with a calculated table that already has all matches of employees and jobs. What do you think?
Yes, having a test dataset would be nice. Anyway, if performance become important, then the model would need to be different, mainly avoiding the M2M to rely on regular 1:M relationships.
Thanks very much Alberto.The second parameter of FILTER is a Filter Expression that is a boolean (True/False) expression that is to be evaluated for each row of the table. In the video you used COUNTROWS as the second parameter for FILTER. Could you please advise how COUNTROWS works, because COUNTROWS cannot return a boolean value?
That was actually a mistake, that still worked by chance. COUNTROWS returns the number of rows: 0 or BLANK stand for FALSE, any other number stands for TRUE. Therefore, it works, even though adding a "> 0" would make it much better.
