Skip to Content
author's profile photo Former Member
Former Member

Using a dimension member property in transformation


I have been searching if it is possible to do some IF ELSEIF calculations in data manager transformations. If the statements is done on a dimension member, the transfotmation works fine.

What I was not able to achieve is to use a dimension member property in the if statement. (e.g. if local currency of entity is something do something).

Can anyone help me in this? I am not sure if this is even possible in BPC 7.0 NW at all 😔



Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • Best Answer
    Posted on Oct 01, 2009 at 12:44 PM


    I'm not sure I'm following exactly what you want to do here. The way I usually think about it (though I don't do transformation file work every day) is that the operands evaluated in an "IF" statement in a transformation file are not dimensions or members, but rather columns in the source file. As such, they don't really have properties. They are just text strings. (Examples here: [])

    If you're loading from an InfoProvider rather than a flat file, it is possible to restrict on navigational attributes in the SELECTION in the OPTIONS section. It does not appear possible to execute conditional logic based on navigational attributes, or to map navigational attribute values to members in the BPC application.

    One option to possibly achieve what you are looking for is to load data into your BPC application and then perform your conditional logic within the application itself, where you do have access to the member properties you need.

    Probably not what you wanted to hear, but hopefully it's helpful.


    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member


      the second option you described is exactly our scenario. We need to load data from other BW cubes and need to evaluate BPC dimensions according to nav. attributes in BW.

      It really seems that this functinality is not yet implemented 😔



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.