Hi @Matt_Shudy,
Yes, when filtering data by multi-selection field and selecting multiple values in a report, then results are summed up for each matching value.
In the given example, Dedupe based on customer field is used an issue property “Issue Story Point” and a measure “Issues created” representing current values. In your case, you are analyzing historical data and their changes (Est To Close ($) change) and might want to use historical measures for the calculation.
The logic for calculation to exclude the duplicates is to get a set of issues that matches report context including selected values for a multi-selection field, and then sum up those values ignoring the selection of the multi-selection field. The updated formula right look like this:
Sum(
--get set of issues that has changes in Est To Close ($) according to report context
Filter(
Descendants([Issue].CurrentMember,[Issue].[Issue]),
[Measures].[Est To Close ($) change] > 0
), --sum up changes in Est To Close ($) ignoring multi selection custom field
([Measures].[Est To Close ($) change],
[Multi-selection custom field].CurrentHierarchy.DefaultMember)
)
There are more details on calculated measures and used function DefaultMember:
- https://docs.eazybi.com/eazybijira/analyze-and-visualize/calculated-measures-and-members/calculated-measures
- https://docs.eazybi.com/eazybi/analyze-and-visualize/calculated-measures-and-members/mdx-function-reference/defaultmember
Best,
Zane /support@eazybi.com