Hi,
I have a usual requirement in an OPEX cube when a user selects a Cost Center from the title dimension, only the relevant Expense lines should appear on the rows. We have done this many times in Web an Perspectives, worked fine. There is a small parameter cube with Cost Centers and Expenses, put a 1 to the relevant combinations, then use a subset like this in the planning cube, while having CCs on title, Expenses on rows:
{FILTER(TM1FILTERBYLEVEL(TM1SUBSETALL([Accounts_OPEX_PLAN]) , 0) , [PLAN_Param_CCToGL].([CostCenters_OPEX].CURRENTMEMBER,[StrNum].[nValue]) = 1)}
It seems CAFE ignores the "[CostCenters_OPEX].CURRENTMEMBER" part of the subset, and returns those Expenses of which Sum is 1 in the parameter cube => so those expenses that are assigned to one and only one Cost center, independently from the Cost center selection on the title.
Any idea of a quick workaround? Same results but different mdx code?
Thank you!
Matyas
CurrentMember in CAFE
- paulsimon
- MVP
- Posts: 808
- Joined: Sat Sep 03, 2011 11:10 pm
- OLAP Product: TM1
- Version: PA 2.0.5
- Excel Version: 2016
- Contact:
Re: CurrentMember in CAFE
HI
I would suggest creating a dimension from your cube with consolidations for each Cost Centre and base level elements of the relevant Expense codes. Then you don't even need MDX. You can use a simple list with ELCOMP.
Regards
Paul Simon
I would suggest creating a dimension from your cube with consolidations for each Cost Centre and base level elements of the relevant Expense codes. Then you don't even need MDX. You can use a simple list with ELCOMP.
Regards
Paul Simon
-
- Community Contributor
- Posts: 341
- Joined: Wed Nov 03, 2010 9:16 pm
- OLAP Product: tm1
- Version: 10 2 2 - 2.0.5
- Excel Version: From 2007 to 2013
- Location: Earth
Re: CurrentMember in CAFE
Thanks Paul!
Actually, that is one of my main points to consider if I want to use one merged, or two dimensions, found some pros/cons for both. If I understand correctly your suggestion means the one dimension approach.
Actually, that is one of my main points to consider if I want to use one merged, or two dimensions, found some pros/cons for both. If I understand correctly your suggestion means the one dimension approach.
- paulsimon
- MVP
- Posts: 808
- Joined: Sat Sep 03, 2011 11:10 pm
- OLAP Product: TM1
- Version: PA 2.0.5
- Excel Version: 2016
- Contact:
Re: CurrentMember in CAFE
Hi
No I am not suggesting that you need to convert your cube to a single combined dimension. I was suggesting that you create a dimension that is not used in any cubes and that you just use this to drive the dependency between the two dimensions for your second drop down box.
Regards
Paul Simon
No I am not suggesting that you need to convert your cube to a single combined dimension. I was suggesting that you create a dimension that is not used in any cubes and that you just use this to drive the dependency between the two dimensions for your second drop down box.
Regards
Paul Simon
- PavoGa
- MVP
- Posts: 622
- Joined: Thu Apr 18, 2013 6:59 pm
- OLAP Product: TM1
- Version: 10.2.2 FP7, PA2.0.9.1
- Excel Version: 2013 PAW
- Location: Charleston, Tennessee
Re: CurrentMember in CAFE
Code: Select all
{FILTER(TM1FILTERBYLEVEL(TM1SUBSETALL([Accounts_OPEX_PLAN]) , 0) , [PLAN_Param_CCToGL].([CostCenters_OPEX].CURRENTMEMBER,[StrNum].[nValue]) = 1)}
Ty
Cleveland, TN
Cleveland, TN
-
- Community Contributor
- Posts: 341
- Joined: Wed Nov 03, 2010 9:16 pm
- OLAP Product: tm1
- Version: 10 2 2 - 2.0.5
- Excel Version: From 2007 to 2013
- Location: Earth
Re: CurrentMember in CAFE
Hi
Not in CAFE unfortunatelyIt will automatically filter it for the context of the title dimension, the cost center selected.
-
- Community Contributor
- Posts: 341
- Joined: Wed Nov 03, 2010 9:16 pm
- OLAP Product: tm1
- Version: 10 2 2 - 2.0.5
- Excel Version: From 2007 to 2013
- Location: Earth
Re: CurrentMember in CAFE
Hi
Seems to be a bug, if I open the subset editor in CAFE, click on the MDX icon, and amend the subset by just adding a simple space, it starts working.
So I think it won't be related to CurrentMember, much more how CAFE renders the dynamic subset, although not sure yet what kind of mdx expressions/formulas are impacted, if it is not only CurrentMember
Ticket opened, I will post the APAR nr here.
Seems to be a bug, if I open the subset editor in CAFE, click on the MDX icon, and amend the subset by just adding a simple space, it starts working.
So I think it won't be related to CurrentMember, much more how CAFE renders the dynamic subset, although not sure yet what kind of mdx expressions/formulas are impacted, if it is not only CurrentMember
Ticket opened, I will post the APAR nr here.