Loved it! But how can i deal with Blank Values? Whenever there are blank values my status will show very bad, its showing the data quality is bad hahah is there an "IFNA" or "ISNULL" option?
This is exactly what I've been looking for! Only thing that prevents me using this is when you said at 1:58, that you have already created the measure? Do I need to create that too? If so, how?
Hi Bas, as a newbie in PBI, your videos help me a lot. Thank you so much. As an exam secretary at a middle school, I built the enclosed gauge in Excel (the pointer consists of two lines of different length around a pivot point by means of a sin and cos table). It is a challenge, but is this also possible in PBI? I do find them online, but not nearly as nice ;-). I think the context is clear. Oeps... I can't upload the picture 😞
Great idea! I see your default pointer value is at 3 or 4. Do you have a filter on? How is the 'Status bar' table related to the table in which the 'DifferencetoForecast' measure exists? Thanks!
Question: If I wanted to select one value of the status bar (let's say "Very Bas") and have the rest of the report update and show me everything that is considered "Very Bad" (ie the sales of April 2021) how would you do it? Should you update the sales data with a Status ID and then link it? Kudos in advance to anyone who can answer this or propose different ways
Some strange problem is appearing. I cannot drag and drop the columns created by Enter Data (Status Id and Status Description) to values (no problem with measures - pointer and status). Is there was some PBI Update that prevents this
Hi Bas, Can you please help with below scenario I have 10,000 customer records in my report on day 1 Monday Monday - 1,000 failed records 1,000 / 10,000 = 10% fail rate Tuesday - 500 NEW failed records 1,500 / 10,000 (or total customers) = 1,500 failed records = 15% fail rate - Its important that the cumulative figure is only re-calculated on the NEW failed records Wednesday - Zero NEW failed records = 15% failed records Thursday - Zero NEW failed records, but 500 new customers come onto the report - 10,500 customers. Still have 1,500 records failed which now equals 1,500 / 10,500 = 14.3% failure rate
Hi Azhar, this is a running total calculation. See example below -> Failed Records running total in Date = VAR FailedRecordsRT = CALCULATE( SUM('data'[Failed Records]), FILTER( ALLSELECTED('data'[Date]), ISONORAFTER('data'[Date], MAX('data'[Date]), DESC) ) ) VAR TotalCustomers = SUM(data[Total Customers]) VAR Result = DIVIDE( FailedRecordsRT, TotalCustomers ) RETURN Result
@@azharshaik21 there is a quick measure that you can use (running total) as a starting point, maybe that helps. Then one you have the running total for failed records you can edit so that you divide it by the sum of customers
Hi Sahan, thx! This approach is not really suitable for a continuous value scale. Let me think of an alternative that would work with a continuous scale
Very informative and great video (don’t know how someone can “Unlike” it )
Loved it! But how can i deal with Blank Values? Whenever there are blank values my status will show very bad, its showing the data quality is bad hahah is there an "IFNA" or "ISNULL" option?
I love it !! really good idea, I think I will try to put this status bar everywhere :D
sure your colleagues will love it 😅 😁
Hey very informative, I want to have the status bar inside my table cell., Is it possible ?
Hi Baz, Great Video. Unfortunately the download link isnt working.
please have a look again the link seems to be working and download starts automatically
b for baz
b for best power bi youtuber
p for power bi
p for perfect baz
😂 I'm on the ground. You made my day!
Amazing! Thank you for sharing.
thank you!!!! 😀
I tried this method, everything else works fine, except the pointer row shows "1" in each cell, and I couldn't figure out why
hey, great work again.
I get an error when i follow your learning path, could you please fix it? =)
Edit: Same with your Download Link.
Greetings
thank you for spotting it! all fixed :)
@@HowtoPowerBI What an insane support here! ;)
Thank you man.
Now it works!
Awesome thanks for sharing
You are a star ✨✨
Please share design tips
thank you for watching!! 😃
This is exactly what I've been looking for! Only thing that prevents me using this is when you said at 1:58, that you have already created the measure? Do I need to create that too? If so, how?
Hi Bas, as a newbie in PBI, your videos help me a lot. Thank you so much. As an exam secretary at a middle school, I built the enclosed gauge in Excel (the pointer consists of two lines of different length around a pivot point by means of a sin and cos table). It is a challenge, but is this also possible in PBI? I do find them online, but not nearly as nice ;-). I think the context is clear.
Oeps... I can't upload the picture 😞
Great out-of-the-box thinking, thanks for the video.
Thx Todd!
Great idea! I see your default pointer value is at 3 or 4. Do you have a filter on? How is the 'Status bar' table related to the table in which the 'DifferencetoForecast' measure exists? Thanks!
there is no default - the measure of interest could be anything (here sales vs forecast). You just need to determine the status based on that measure
@@HowtoPowerBI Thanks for replying, when I put the pointer measure in values, I don't see the value '1' as shown in 5:23
Prefect as usual, out of box thinking :)
Thanks again! 😀
Very usefull video! Thanks
thx Nicolas!!!!😀
Question: If I wanted to select one value of the status bar (let's say "Very Bas") and have the rest of the report update and show me everything that is considered "Very Bad" (ie the sales of April 2021) how would you do it? Should you update the sales data with a Status ID and then link it? Kudos in advance to anyone who can answer this or propose different ways
Can't wait to try this one out. Another great one. Thank you!
Thanks Chris! Let me know how it goes!
Some strange problem is appearing. I cannot drag and drop the columns created by Enter Data (Status Id and Status Description) to values (no problem with measures - pointer and status). Is there was some PBI Update that prevents this
I'm having the same issue ☹️
Power BI is saying the File is corrupted, can't open!!
oh no! not sure how that happened. Should work now 🙂
Hey, how do you input emoji in there? Switch to japanese keyboard??
Hi, you can watch this video about how to work with emojis ua-cam.com/video/WWKTrdlJjNM/v-deo.html
Hi fantastic however I can’t resize the finished product any ideas?
Hi Debbie, you would need to play around with the width and height of the columns and rows
Hi Bas, Can you please help with below scenario
I have 10,000 customer records in my report on day 1 Monday
Monday - 1,000 failed records 1,000 / 10,000 = 10% fail rate
Tuesday - 500 NEW failed records 1,500 / 10,000 (or total customers) = 1,500 failed records = 15% fail rate - Its important that the cumulative figure is only re-calculated on the NEW failed records
Wednesday - Zero NEW failed records = 15% failed records
Thursday - Zero NEW failed records, but 500 new customers come onto the report - 10,500 customers. Still have 1,500 records failed which now equals 1,500 / 10,500 = 14.3% failure rate
Hi Azhar, this is a running total calculation. See example below ->
Failed Records running total in Date =
VAR FailedRecordsRT =
CALCULATE(
SUM('data'[Failed Records]),
FILTER(
ALLSELECTED('data'[Date]),
ISONORAFTER('data'[Date], MAX('data'[Date]), DESC)
)
)
VAR TotalCustomers =
SUM(data[Total Customers])
VAR Result =
DIVIDE(
FailedRecordsRT,
TotalCustomers
)
RETURN
Result
@@HowtoPowerBI Thanks Bas for the quick response. ISONORAFTER function is not allowing me to take date in the first value
@@azharshaik21 there is a quick measure that you can use (running total) as a starting point, maybe that helps. Then one you have the running total for failed records you can edit so that you divide it by the sum of customers
Excuse me while I like and save for later all of your videos :)
hahaha thank you so much for watching! 😄
YOU
JUST
ROCK
MY
DUDE
Good video, can you advise how to do this for continuous values, not discrete
Hi Sahan, thx! This approach is not really suitable for a continuous value scale. Let me think of an alternative that would work with a continuous scale
Great stuff!
thank you Niko!!!
Genious.
Grate !!
Thanks once again Bas!!!
thanks for watching Frank!😀
very cool
Thx Mark!
Awesome
thanks Prachi 👊😃
Totally incredible!!!!
Thank you Roberto! 😀