Forum Discussion
Grouped summaries with conditional filtering
- 1 year ago
Anonymous - If the answers you have given me are true and all your data lives in the CBAM_Goods_InScope table then the DAX for a Dynamic measure I gave you earlier works. I have copied it below again:
VAR Threshold = [SelectedThreshold] VAR HighValueEntries = CALCULATETABLE ( VALUES ( 'CBAM_Goods_InScope'[EntryIdentifier] ), FILTER ( ADDCOLUMNS ( VALUES ( 'CBAM_Goods_InScope'[EntryIdentifier] ), "@CustomsValue", CALCULATE ( SUM ( 'CBAM_Goods_InScope'[CustomsValue] ) ) ), [@CustomsValue] > Threshold ) ) RETURN CALCULATE ( SUM ( 'CBAM_Goods_InScope'[SupplementaryUnitQty] ), KEEPFILTERS ( 'CBAM_Goods_InScope'[EntryIdentifier] IN HighValueEntries ) )I will repeat, you cannot do this dynamically within a physical DAX calculated table, because they do not re-calculate every time a parameter changes, a.k.a they are static.
If you want this to be dynamic, then you will have to use a measure. Use the DAX I have given you above. It creates a virtual table, based on the selectedThreshold, and the SupplementaryUnitQty is then calculated over this table. It is the most optimal and performance efficient version of this calculation you will get.
I am attaching my file so you can investigate it working, and below are some screenshots to show it dynamically calculating based on the value in the slicer.
If I answered your question please mark my post as the solution, it helps others with the same challenge find the answer!
grazitti_sapna Thanks and I tried this... Summarize will not work based on the dynamic parameter as I mentioned in my post earlier... It is always considering 150 which is default value not the value which is getting passed...
Hi Anonymous ,
You're correct when we use SUMMARIZE in a calculated table, it doesn’t pick up the dynamic slicer value like [SelectedThreshold]. It only takes the default value at the time of refresh. To make it work based on what the user selects in the slicer, it’s better to use a measure-based virtual table. That method will react properly to the slicer and can be used in further calculations also.
If this answer was helpful, please consider marking it as Accepted Solution and giving a Kudos, it helps the community.
Best Regards,
Harshitha.
- Anonymous1 year agoNot applicable
Anonymous Thanks for your response. Can you please let me know how to create the measure based virtual table to filter the data based on my requirement.
- mark_endicott1 year ago
Super User
Anonymous Anonymous - I have already done this and attached the file for you to use. See below for the post it is further up the chain.
Anonymous - if the file I have already supplied you has not resolved your issue, please can you explain why?
- Anonymous1 year agoNot applicable
Hi Anonymous,
mark_endicott ,thank you and really appreciate the detailed support and working file you have provided.Yes, completely agree with your approach here. As you rightly mentioned, calculated tables won’t respond to slicer/parameter changes at runtime. The dynamic measure with virtual filtering using TREATAS and filtered EntryIdentifiers is the right and optimal solution in this case.
Anonymous Please do revisit Mark’s earlier post and test the attached PBIX. If you are still seeing differences between your SQL output and Power BI results, could you kindly share what exactly is not matching? That’ll help us assist more precisely.
Best regards,
Harshitha .