dynamic member property selection with EPMDimensionoverride

[former_member233959]

Hi Folks,

I have a specific question concerning the EPMDimensionoverride. I would like to use one Hierarchy for my Report. Let me say the ACCOUNT Hierarchy is PARENTH1.

The member in this hierarchy has the property A1.

I know how it works by using the Report-Editor but how can I write the EPMDimensionoverride to filter the hierarchy Members two values within A1. So A1 OR A2 - would be my desired solution but see below my examples:

If I write it like

1. EPMDimensionOverride("000","ACCOUNT","LDEP(3,PARENTH1);A1=1;A1=2") --> there is clearly no result as I used ; and this means AND. A1 can't be 1 and 2 at the same time
2. EPMDimensionOverride("000","ACCOUNT","LDEP(3,PARENTH1);A1=1,A1=2") --> this means I will see all members of PARENTH1 having an A1=1. And below this I will see all members having a property value of 2 BUT of all ACCOUNTs and not only of PARENTH1.
   
   So how do I get my desired selection of PARENTH1 with all ACCOUNT members having A1=1 OR A1=2 ?????
3. EPMDimensionOverride("000","ACCOUNT","LDEP(3,PARENTH1);(A1=1,A1=2)") --> doesn't work. IN the Report Editor it is pretty simple I just select TWO properties by using ONE filter.
   
   So how to do with EPMDimensionOverride?

I am grateful for any help - thanks in advance!

Max

[former_member186338]

May be:

EPMDimensionOverride("000","ACCOUNT","LDEP(3,PARENTH1);A1=1,LDEP(3,PARENTH1);A1=2")

[former_member233959]

Hello Vadim,

yeah nice try. I considered this as well. But due to the fact that in my specific case A1 has the value A (for account) and A1=N for node.

It is actually there to make it possible to Show the required accounts with their belonging nodes.

Vadim Kalinin wrote:

May be:

EPMDimensionOverride("000","ACCOUNT","LDEP(3,PARENTH1);A1=1,LDEP(3,PARENTH1);A1=2")

Your proposed soultion brings all the Accounts and Nodes but in a wrong structure eventually. Because it would Show the accounts and nodes in two separated Groups. But not like in a hierarchy structure.

Any other hints?!

[Former Member]

This worked for a similar scenario for me,  but it had similar issues with the order.  I don't think you can retain the hierarchical order when doing this type of property filtering.

=EPMDimensionOverride("000","ACCOUNT",LDEP(3,PARENTH1) AND A1 = 1,LDEP(3,PARENTH1) AND A1 = 2)

Message was edited by: Ryan Forsberg

[former_member186338]

If you use filters by property etc... you will be unable to retain the hierarchical order. No way! Look on the resulting order in member selector.

Vadim

[jrg_finster3]

Sorry Vadim but this is not true.

If you use Property Filters combined with for example "ALL(XYZ)" the hierarchical order is still given.

You can even Switch between Parents Before or After.

Maximilian:

Unfortunatly we are also struggeling at that Point without an idea, what the Syntax could be.

As a Workaround we use new properties with "comined values", but there should be a way to have the same result in Report Editor and via AxisOverride.

Goal is to Archive something like that via AxisOverride:

Regards

Jörg

[former_member233959]

Hi Jörg,

you were quicker . I was just about to prepare screenshots. Because I know it is working from the Report Editor Options.

But not with EPMdimensionoverride.... 😞

Yeah combined values could be a solution as well. For our case I thought about giving the required Nodes and Accounts an extra property A2 and the value A just for the nodes and also accounts. But it is not a very cool solution...

[former_member186338]

Unfortunately looks like EPMdimensionoverride is unable to parse logical expression with brackets!

Like: condition1 AND (codition2 OR condition3)...

Vadim

[former_member233959]

Hi Vadim,

exactly - this goes nowhere unfortunately...

I think we have to go on with some kind of workaround...

Max

[former_member186338]

Another not elegant workaround: create SORTORDER property, fill it for all members and use it in Member sorting by property...

[Former Member]

Maximilian,

     Is the list of properties finite for A1?  because you could just exclude the rest if so.

EPMDimensionOverride("000","ACCOUNT",LDEP(3,PARENTH1);A1 <> 3;A1 <> 4;...)

~Ryan

Sorry for the double post:

[former_member233959]

Hi Ryan,

that is exactly how I did it here for the customer because they have only N and A or E (empty).

EPMDimensionOverride("000","ACCOUNT","LDEP(3,PARENTH1);A1<>E") solves the issue for me.

You could also think about using different values for this property such as an process prefix and work with LIKE. So it could be A1=E, PA, PK. then you could do something like A1 LIKE P*

Thanks for all your Support!
Max