(Case Study) Field Parameters or Calculation Groups???
HTML-код
- Опубликовано: 11 июл 2024
- Dive into a client scenario with me as I compare and contrast the use-cases, benefits, and limitations between Field Parameters and Calculation Groups. Tune in to learn more!
RELATED CONTENT 🔗
Field Parameters -- learn.microsoft.com/en-us/pow...
BECOME A CHANNEL MEMBER 🎉
-- / @havensconsulting
CHECK OUT OUR MERCH STORE 👕
-- havens-consulting.creator-spr...
LET'S CONNECT! 🧑🏽🤝🧑🏽 🌟
-- / havensbi
-- / reidhavens
-- / havensconsulting
-- / havensconsulting
HAVENS CONSULTING PAGES 📄
Home Page - www.havensconsulting.net
Blog -- www.havensconsulting.net/blog-...
Blog Files -- www.havensconsulting.net/blog-...
Files & Templates -- www.havensconsulting.net/files...
Consulting Services -- www.havensconsulting.net/consu...
Online Courses -- www.havensconsulting.net/onli...
Contact & Support - www.havensconsulting.net/conta...
EMAIL US AT 📧
info@havensconsulting.net
#PowerBI #powerplatform #microsoft #businessintelligence #datascience #data #dataanalytics #excel #powerapps #datavisualization #dashboard #bi #analytics #powerquery #dax #microsoftfabric #semanticmodel #fieldparameters #calculationgroups 
Наука
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
Great examples as well to accompany this! It is nice to use them to select the hierarchy order for a visual :)
Excellent example. Really useful to know in this type of situations 👌
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!
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 :)
Amazing video Reid!!!
Thanks!!
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.
Excactly, the "it depends" scenario. But this should help provide some people context of when to do what, and when :)
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
Well said!
Nice case study...
Voice and video are not synced.
I've noticed this on a couple of videos from Reid.
Separate mic/camera feeds which sometimes are off by about 100MS. Editor should catch that though.
Calculation Groups having lots flexibility , you can write dynamic dax queries
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. :)