eazyBI MDX: Dynamic Current Member in Filter() Always Returns 0

Questions & Answers
, , , ,
1

Hi there,

I’m running into an issue in eazyBI with a Parent-Child setup in Jira:

  • Hardcoded works perfectly:
Count(
  Filter(
    [Issue].[Issue].Members,
    [Issue].CurrentHierarchyMember.Get('Parent link issue key') = 'KEY-150'
  )
)

Result: correctly returns 1 Child Issue.

Problem:
As soon as I try to make the Parent dynamic using a dashboard dropdown or the current Row-Context, Filter() always returns 0.

  • Cause: Filter() breaks the Row Context. Inside the filter, CurrentHierarchyMember refers to the iterated Child, not the selected Parent. Therefore, the comparison always fails.

Question to the community:
Is there a clean way to reference the selected Parent dynamically inside Filter() so that I can calculate Burn-Down counts for any Parent?
I want no hardcoding, and the solution must be robust for dashboards with dropdowns.

Thanks in advance for any working MDX patterns or guidance!

2

Hi @JAKO

Welcome to eazyBI Community!

It seems that you also reached out to us directly. I will post the answer here as well in case other eazyBI might be searching for a similar solution.

The limitation is that it is not possible to use the Issue dimension for report page filtering and then use the Issue dimension again to iterate and find the child issues. This part of the formula is not working, as the Issue.CurrentMember is ambiguous:

[Issue].CurrentHierarchyMember.Get('Parent link issue key')
MATCHES
[Issue].CurrentMember.Key

The solution is to use a different dimension for page filtering. If you have imported the Parent link , you should see dimensions that correspond to different Parent levels:

2098×696 73.2 KB

So, depending on which parent level you need to cover, the filter condition should look like this:

    [Issue].CurrentMember.GetString('Plans Feature') 
    = [Plans Feature].CurrentMember.GetString("KEY")

This formula expects the Plans Feature dimension to be used for page filters.

Best wishes,

Elita from support@eazybi.com

1 Like
3

This works exactly now for our use case.

Thank you very much for your solid Support