Hi Reid - have you considered for your field parameters (good example) to expand the parameter table with more columns that contains extra columns where the the different order of fields might be named (country/class) and manufacturer/class and then use the grouping column from the parameter table in the visual and leave out the class column. Another option could be to change the slicer to multiselect and add class to the field parameter options - and then the order of which you select the fields will build the hierarchy in the visual
@HavensConsulting
6 ай бұрын
Great examples as well to accompany this! It is nice to use them to select the hierarchy order for a visual :)
@alexrosen8762
7 ай бұрын
Excellent example. Really useful to know in this type of situations 👌
@OneNI83
7 ай бұрын
Voice and video are not synced.
@workstuff5253
7 ай бұрын
I've noticed this on a couple of videos from Reid.
@HavensConsulting
7 ай бұрын
Separate mic/camera feeds which sometimes are off by about 100MS. Editor should catch that though.
@MrGazpage
6 ай бұрын
Great video. Is there somewhere I can read more about using calculation groups like this? I was only aware of using them in a table with each column being a measure. Seems there is a lot more to them!
@HavensConsulting
6 ай бұрын
I have a few videos that show some wacky use-cases. I'd recommend going to my channel page and searching "calculation groups" to find some of the streams and recorded videos I did :)
@martinbubenheimer6289
7 ай бұрын
Nice! I'm currently working on exactly the same design decisions. The original solution without field parameters or calculation groups used a SWITCH pattern in the DAX code to switch between the measures. But this is too slow and has too much code duplication, But field parameters also have their challenges: If you switch measures and you want to sort the visual by such a measure, sorting is lost each time you switch. You also cannot use a field parameter as a visual level measure filter. And you cannot use calculation items that actually do numeric calculations on measures that return text which becomes tricky is you use measures that return a color for conditional formatting. So you really need to make the best decision on a case-by-case basis. My favorite pattern is to use calculation items only for context changes, like different data range, different relationship, since they work with every measure. And use field parameter or a SWITCH logic for the calculations depending on the requirements.
@HavensConsulting
7 ай бұрын
Excactly, the "it depends" scenario. But this should help provide some people context of when to do what, and when :)
@gustavoesporte9072
7 күн бұрын
Hey Reid, awesome explanation, thanks a lot. Can you please share the demo pbix file?
@HavensConsulting
7 күн бұрын
Thank you! All files are on my Blog Files page on my website :) www.havensconsulting.net/blog-files
@businessinsights_AlexRobe
7 ай бұрын
Great video again, Reid! 🙏 To overcome the hierarchy issue in the right example, I always include ALL categories into the field parameter & slicer allowing the User to be in full control of the hierarchy he wants to build. As the sequence is defined by the selection sequence in the slicer - and sometimes he does not even want to have a hierarchy at all 🙂 Only downside IMO is a bit more real estate required for the slightly larger slicer
@HavensConsulting
6 ай бұрын
Well said!
@user-nz3yl7xf9j
6 ай бұрын
Calculation Groups having lots flexibility , you can write dynamic dax queries
@HavensConsulting
6 ай бұрын
Both do honestly! That same DAX logic can be used in the measure, and the dynamic format measure, then switched between using a field parameter. It just depends on how localized you'd want to apply that logic, measure, visual, page, report. :)
Пікірлер: 19