Calculated Member Not Excluding Other Calculated Member

Questions & Answers
1

I’m trying to create a calculated member for issues that excludes the members of another custom calculated member. The first calculated member (Recurring) that works fine is …

Aggregate(
  Filter(
    [Issue].Members,
    [Issue].CurrentMember.Get('Recurring') = 'Yes'
  )
)

Using this I’m trying to create the reverse calculated member as follows. I tried simply reversing the filter but this created too many results and threw an error. The problem is the second calc member doesn’t seem to be excluding the first set. Here’s the second member that’s not working.

Aggregate(
  Except(
    [Issue].Members,
    [Issue].[Recurring]
  )
)

I’ve tried a number of variances to no avail. Any assistance would be much appreciated.

1 Like
2

Hi, @Joshua_Hindman

Welcom back to the eazyBI community.

Calculated members in the Issue dimension aren’t good; they slow down the Issue dimension and might cause performance issues. The Issue dimension is the biggest in eazyBI. Hence, the member has to go through all the issues. Also, the member referencing the other member might be problematic.

Also, the Aggregate has a limit of 1000.

Please consider importing the “Recurring” as a dimension into eazyBI and use it instead.

Kindly,
Ilze