I'm sorry for the duplicated chapter. Video recording/editing with COVID or whatever I'm still recovering from is harsh. I probably had to wait a few days or a week more, but I really wanted to publish this video sooner.
Andrzej this content is invaluable! 🤩 thanks for sharing your knowledge with the community, your dedication and passion for data analysis and visaulization is evident. It's amazing the result you reached, well done for this incredible development!!! I wish you a lot of success!!!
Great work Andrzej! It would be great if the chart could be resized automatically based on the matrix size. Then we could fit 8 of these amazing IBCS charts on the same page. Also in the measure if you could add a VAR to flip the chart to a horizontal bar instead - or perhaps we need to code another measure for that. I would have considered moving all total texts above the columns to make it less cluttered. For example for July it gets tricky to see the top of the bar etc
Thanks for you comment. Answers to the questions: 1) DAX measure can't know anything about the matrix size (individual image width and height), you'll need to change options on the Format pane and then to edit corresponding variables in the measure manually 2) Columns width is based on Font Size. So for smaller chart you'll also want to edit font size variable. 3) Flipping between horizontal and vertical definitely requires different measures (see another video for the vertical chart). I see no problem here, they have different use cases, one for time, one for structural analysis. 4) Data labels are for AC (and FC) column, not for PL columns. I believe we shouldn't place AC data label right above PL (outlined) column. But it's OK to just hide labels in certain cases to avoid overlapping.
@@power-of-bi Add your Variance one level back. It will look a bit better: VAR _SVG = _SVG_URLPrefix & _SVG_Open & _SVG_Variance & _SVG_PL & _SVG_ACFC & _SVG_PY & _SVG_DataLabel & _SVG_PeriodLabel & _SVG_TextStyle & SVG_HatchedPattern & _SVG_Close Also for extra clarity consider setting your FC triangle black VAR _triangleFill = IF ( _MainScenario = "FC", _ColorBlack, _ColorGrey)
@@apbreports Thanks. 1) I understand what it will change. Makes sense. Great tip. I'll try. 2) I'm sorry, I see your point (higher contrast), but this proposal contradicts IBCS recommendations (and visual perception principles). It will ruin the entire scenarios unification. Things that are the same should look the same. Triangles are grey for a purpose. Grey fill color = previous year data. IBCS, first of all, is not about 'looks better', but about 'works better'. Comparison with the triangles is secondary task anyway, they are not critically important.
Strange. I was 100% sure I've already answered here... I'll try again. Thanks for the comment. 1) I understand what you're talking about, makes sense, I'll give it a try 2) I see your desire to increase visual contrast. But that will contradict visual perception principles and IBCS recommendations, ruin scenario unification and make the chart unclear. Thing that are the same (previous year data, grey triangles) should look the same. And grey color is not random. It has a specific meaning here and shows older data (previous year) than black AC. Every color (and hatching) is meaningful.
Hi, Andrzej. Great job. One thing still is bothering me. The visualization you presented looks perfect until the displayed numbers are low or equal 999. What if the sales vary from 500k per month to 10000K? In that case the width of the labels might be wider than the width of the columns, which won’t look well. You might have thought of that already. What were your thoughts on that account? Will you make your table wider and put up with a horizontal scroll bar? Will you do the opposite?
Thanks. First of all, it's just a demo so far, not designed and not tested to handle all possible situations automatically. But, what you're asking about is already handled by IBCS. And it's very logical and straightforward solution - we don't really need to see more than 3 digits on data labels on a chart. 500 (k) and 10 000 (k) can be replaced with 0.5 (m) and 10.0 (m). And category with (period or month in this case) and column width (which is 2/3 of category width) is based on font size to get perfect composition of the columns and labels. a scroll bar in a chart? never!
Question: why there is no color legend (AC - solid black, FC - hatched, AC-PL > 0 - green etc.) in the 3rd title row. Answer: when IBCS standard is implemented in an organization, usage of solid black for actuals, hatched for forecasts, outlined for plans become a standard for all charts. Also green on all charts means good and red means bad. Note that reduced sales = bad, but reduced costs = good and therefore green. There is no need to use a legend in a standard business chart anymore. You can understand any chart almost immediately. This is one of the advantages of IBCS.
I would like your point of view on the pros and cons of creating svgs this way vs. deneb. From the start, peope would have to learn any of the 2 languages (yeah I am referring to creating the shapes here as a language, nevermind the technicality). Both methods allow for custom tooltips. This one can be done with native visuals, a plus for companies that restrict custom visuals. Probably a con if this method may be that it is a bit complicated DAX-wise to add a related chart, like an absolute variance column chart on top; you would need another row of the matrix for that... unless you can make a X axis that goes all the way without being chopped by the inner borders of the matrix visual?
Thanks for the detailed comment. Regarding the variance chart using another row of the matrix - not a problem to make the bars, See th-cam.com/video/RAiMq2MWDHM/w-d-xo.html. It's basically the same, just different orientation. What is currently a problem - creating uninterrupted horizontal lines through multiple cells (axis X, lines between bars in a waterfall, reference/scale lines). There are some inner borders that can't be removed, but I hope that's something Miguel Myers's team will be able to fix in future Power BI updates.
![[IBCS] New Column chart in Power BI - Feb 2024 Update](http://i.ytimg.com/vi/4Kn9jmgUlnY/mqdefault.jpg)
![ไข้ขึ้นเลย! เมื่อแฝดโดนจัดเต็มวัคซีนครบ2เดือน🤒 [cc] แดนแพทตี้ SS2 | EP.54 |](http://i.ytimg.com/vi/z2VHItnyyvY/mqdefault.jpg)
WOW! Just beautiful. The decomposition of the SVG was incredibly informative.
Thanks for doing this.
I'm sorry for the duplicated chapter. Video recording/editing with COVID or whatever I'm still recovering from is harsh. I probably had to wait a few days or a week more, but I really wanted to publish this video sooner.
Andrzej this content is invaluable! 🤩
thanks for sharing your knowledge with the community, your dedication and passion for data analysis and visaulization is evident. It's amazing the result you reached, well done for this incredible development!!!
I wish you a lot of success!!!
Congratulations. Your development is incredible.
Is the column chart not available on your GitHub anymore?
Sorry, I've moved it. See github.com/avatorl/PowerBI-IBCS/tree/main/matrix-visual-ibcs
Great work Andrzej!
It would be great if the chart could be resized automatically based on the matrix size. Then we could fit 8 of these amazing IBCS charts on the same page.
Also in the measure if you could add a VAR to flip the chart to a horizontal bar instead - or perhaps we need to code another measure for that.
I would have considered moving all total texts above the columns to make it less cluttered. For example for July it gets tricky to see the top of the bar etc
Thanks for you comment. Answers to the questions:
1) DAX measure can't know anything about the matrix size (individual image width and height), you'll need to change options on the Format pane and then to edit corresponding variables in the measure manually
2) Columns width is based on Font Size. So for smaller chart you'll also want to edit font size variable.
3) Flipping between horizontal and vertical definitely requires different measures (see another video for the vertical chart). I see no problem here, they have different use cases, one for time, one for structural analysis.
4) Data labels are for AC (and FC) column, not for PL columns. I believe we shouldn't place AC data label right above PL (outlined) column. But it's OK to just hide labels in certain cases to avoid overlapping.
@@power-of-bi Add your Variance one level back. It will look a bit better:
VAR _SVG = _SVG_URLPrefix & _SVG_Open & _SVG_Variance & _SVG_PL & _SVG_ACFC & _SVG_PY & _SVG_DataLabel & _SVG_PeriodLabel & _SVG_TextStyle & SVG_HatchedPattern & _SVG_Close
Also for extra clarity consider setting your FC triangle black
VAR _triangleFill = IF ( _MainScenario = "FC", _ColorBlack, _ColorGrey)
@@apbreports
Thanks.
1) I understand what it will change. Makes sense. Great tip. I'll try.
2) I'm sorry, I see your point (higher contrast), but this proposal contradicts IBCS recommendations (and visual perception principles). It will ruin the entire scenarios unification. Things that are the same should look the same. Triangles are grey for a purpose. Grey fill color = previous year data. IBCS, first of all, is not about 'looks better', but about 'works better'. Comparison with the triangles is secondary task anyway, they are not critically important.
Strange. I was 100% sure I've already answered here... I'll try again.
Thanks for the comment.
1) I understand what you're talking about, makes sense, I'll give it a try
2) I see your desire to increase visual contrast. But that will contradict visual perception principles and IBCS recommendations, ruin scenario unification and make the chart unclear. Thing that are the same (previous year data, grey triangles) should look the same. And grey color is not random. It has a specific meaning here and shows older data (previous year) than black AC. Every color (and hatching) is meaningful.
@@power-of-bi I understand about the triangle contrast. Best to keep to the standard of course:)
Hi, Andrzej. Great job. One thing still is bothering me. The visualization you presented looks perfect until the displayed numbers are low or equal 999. What if the sales vary from 500k per month to 10000K? In that case the width of the labels might be wider than the width of the columns, which won’t look well. You might have thought of that already. What were your thoughts on that account? Will you make your table wider and put up with a horizontal scroll bar? Will you do the opposite?
Thanks. First of all, it's just a demo so far, not designed and not tested to handle all possible situations automatically. But, what you're asking about is already handled by IBCS. And it's very logical and straightforward solution - we don't really need to see more than 3 digits on data labels on a chart. 500 (k) and 10 000 (k) can be replaced with 0.5 (m) and 10.0 (m).
And category with (period or month in this case) and column width (which is 2/3 of category width) is based on font size to get perfect composition of the columns and labels.
a scroll bar in a chart? never!
Question: why there is no color legend (AC - solid black, FC - hatched, AC-PL > 0 - green etc.) in the 3rd title row.
Answer: when IBCS standard is implemented in an organization, usage of solid black for actuals, hatched for forecasts, outlined for plans become a standard for all charts. Also green on all charts means good and red means bad. Note that reduced sales = bad, but reduced costs = good and therefore green. There is no need to use a legend in a standard business chart anymore. You can understand any chart almost immediately. This is one of the advantages of IBCS.
I would like your point of view on the pros and cons of creating svgs this way vs. deneb. From the start, peope would have to learn any of the 2 languages (yeah I am referring to creating the shapes here as a language, nevermind the technicality). Both methods allow for custom tooltips. This one can be done with native visuals, a plus for companies that restrict custom visuals. Probably a con if this method may be that it is a bit complicated DAX-wise to add a related chart, like an absolute variance column chart on top; you would need another row of the matrix for that... unless you can make a X axis that goes all the way without being chopped by the inner borders of the matrix visual?
Thanks for the detailed comment. Regarding the variance chart using another row of the matrix - not a problem to make the bars, See th-cam.com/video/RAiMq2MWDHM/w-d-xo.html. It's basically the same, just different orientation. What is currently a problem - creating uninterrupted horizontal lines through multiple cells (axis X, lines between bars in a waterfall, reference/scale lines). There are some inner borders that can't be removed, but I hope that's something Miguel Myers's team will be able to fix in future Power BI updates.
Gracias por compartir 😂
❤