on 09-25-2020 7:37 PM
In our entity dimension, we have a property "ACQ_YEAR - Acquisition Year" this might contain multiple years or a single year:
In a report I need to show all members that have either 2018 or 2019 in the property.
If I use EPMDimensionOverride to filter for ACQ_YEAR like *2018" or ACQ_YEAR like *2019* members that have both 2018 and 2019 in their list are returned twice.
Using the filter by properties from the member selector it is possible to use merged filters to control this using "Not Like"
I would like to replicate this in using EPMDimensionOverride formula so that I can make the years dynamic dependent upon the selected time period.
I have run into two problems with this:
1. "Not Like" does not seem to be possible in EPMDimensionOverride
2. There does not seem to be a way to "merge" criteria
Can someone suggest how I would be able to replicate the
I developed a work around for this problem, which was to build a list of the possible combinations of the property for each year, then link this to the EPMDimensionOverride function via a vlookup.
The downside of this approach is that I will have to maintain the list as master data changes, but it does at least mean that I can provide workable input templates...
vadim.kalinin, would you suggest I raise this as a message with SAP in order to bring this to SAP's attention, or use the suggestions route?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In general, EPMDimensionOverride have to support the same logic that can be implemented using filter in Member Selector.
Unfortunately, currently we have no support for NOT LIKE condition. Have to be corrected.
I have checked all possible syntax variants - nothing works:
ACCTYPE NOT LIKE '*E*'
ACCTYPE NOT(LIKE '*E*')
NOT ACCTYPE LIKE '*E*'
NOT(ACCTYPE LIKE '*E*')
ACCTYPE LIKE NOT '*E*'
ACCTYPE LIKE NOT('*E*')
ACCTYPE NOTLIKE '*E*'
And for sure LIKE itself is working fine:
ACCTYPE LIKE '*E*'
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Marc,
Like appears to work without any problem, Not Like does not.
I was able to use "ACQ_YEAR LIKE *2018* or ACQ_YEAR LIKE *2019*"
Regards,
Mark
We have also been using LIKE syntax for several years already.
It's indeed not in EPM-addin help documentation files. But maybe it's about time this gets recognized and officially supported.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.