Drill through issues problem when using [Issue].[Project].Children approach

Questions & Answers
,
1

Hi Team,

I ran into a performance issue with Filter(Descendants approach, I then found this post Performance issue when calculating Max with filter and descendants - #2 by janis.plume for using [Issue].[Project].Children approach.

Count(
  Filter(
    DescendantsSet([Issue].[ABC],[Issue].[Issue]),
    [Measures].[Status Was Ongoing]>0
  )
)

This approach is doing a really good job on returning numbers. But however, I found out that drill through issues feature no longer work on the number result. It will give me some irrelevant tickets.

Is there anyway we can still do drill through issues with this approach.

Thank you in advance.

2

Hi @QiZhang ,

The current expression overwrites the Issue dimension context.
The drill-through is executed on each issue separately, but that context is overridden within the expression.

The workaround is to split the expression into two branches - one expression for the drill through and the other for the general issue category.

The expression might look as follows.

CASE WHEN
-- individual issue from default hierarchy or drill through issue
 [Issue].CurrentMember.Level.Name = "Issue"
THEN
 CASE WHEN
-- original condition
  [Measures].[Status Was Ongoing]>0
  AND
-- extra condition to check relevance to project
  [Issue].CurrentMember.Get('Project key') = "ABC"
 THEN
-- value to be returned
  1
 END
ELSE
-- the expression for issue category - the original one
 Count(
  Filter(
    DescendantsSet([Issue].[ABC],[Issue].[Issue]),
    [Measures].[Status Was Ongoing]>0
  )
 )
END

Regards,
Oskars / support@eazyBI.com

3

Thank you very much. This is really helpful