I am trying to achieve at single member level for each GL account.. Agg_GLAccounts and Agg_StoresOnly have 1-n relationship.. So, for all sum of each GL per store/Agg_SqftGLAccount which is sqft per store is what I want.. Hope you understand.. If you would prefer to have a google meet that would reduce my stress

I am facing error: 'XQE-PLN-0071 The query is not supported. The referenced detail '' for the 'within detail' aggregate 'Data Item1' can not be found on the same edge as a sibling of the given aggregate.'

I am facing above error only when I switch either of them to 'within detail' instead of 'within set'. But I am damn sure that within detail will go at single member level. What do you say on this?? On the other hand when I use within set, I am getting the summirization at set level fine which I don't need.

Tuple is:

tuple([Agg_GLAccounts],[Value])/ tuple([Agg_SqftGLAccount],[Value])

Agg_GLAccounts - aggregate(currentMeasure within detail [NonStat_GLAccounts])

Agg_SqftGLAccount - aggregate(currentMeasure within detail [Stat_GLAccounts])

Agg_StoresOnly - total(currentMeasure within detail [StoresOnly])

Please help

Hari

A few issues are presented here.

1. "within detail" is specifically a relational operator. For dimensional reporting, you should use "within set".
2. Tuples are only valid when pointing to measures or members. They can work with calculated members, which you can construct like this:

member(aggregate(currentMeasure within set [NonStat_GLAccounts]),'AggGLAccounts' ,'AggGLAccounts',[Cube].[Dimension].[Hierarchy])

The structure here is: member( <VALUE EXPRESSION>[, code, caption, hierarchy])

An interesting note here, because the tuple is only referencing one object, you could get away with using:

aggregate([Value] within set [NonStat_GLAccounts]) / aggregate([Value] within set [Stat_GLAccounts])

to get the same results.