Measure stopped working when shared

Questions & Answers
1

Hi all,

I have a measure that works fine when it is report-specific but fails when it’s shared.

The code in each one is this:

--annotations.group=Predicted
Order(
  Filter(
    ChildrenSet([Fix Version].[AggregatePageMembers]),
    Format([Fix Version].CurrentMember.GetDate('Start date'),'Medium Date') <> ''
  ),
  [Fix Version].CurrentMember.Get('Start date'),
  BASC
)
.Item(0).GetDate('Start date')

In a table, it shows up like this:
image

I’m 99.99999% sure it’s not a cut/paste error as the behaviour is consistent if I simply change the measure between Shared/Report-Specific.

Any ideas what could cause this?

2

Additional information…

I narrowed it down to the ChildrenSet line.

ChildrenSet([Fix Version].CurrentHierarchyMember) returns the expected list in both shared/report-specific measures.

ChildrenSet([Fix Version].[AggregatePageMembers]) returns {[Fix Version].[#null]} in the shared measure but works fine in the report-specific measure.

even though:

[Fix Version].CurrentHierarchyMember.Name is AggregatePageMembers in both.

3

Hi,

Thank you for your effort with the debugging!
I tried to reproduce the behavior, no luck so far.

Could you also share the formula and a screenshot of how the “AggregatePageMembers” are defined?

Kindly,
Janis, eazyBI support

4

Hi Janis,

There isn’t really a formula for the AggregatePageMembers. This is the member that is returned when I use the multi-select option for ‘Project’ in the Pages area of my report and >1 item is selected.

Chris P.

5

Hi Chris,

Thank you for the update.

I added this behavior to our backlog as a possible bug report. The workaround you mentioned is the recommended way to go since the use of AggregatedPageMembers is an undocumented feature and should not be relied on.

ChildrenSet([Fix Version].CurrentHierarchyMember)

Kindly,
Janis, eazyBI support