in

Prologika Forums

Business Intelligence to the Masses
Latest post 04-17-2008 2:50 AM by Acius. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 04-16-2008 5:55 PM

    • Acius
    • Top 10 Contributor
    • Joined on 01-16-2006
    • Posts 53

    Listing 10.2 and testing non-existant values

    I'm trying to do something similar to the case statement in Listing 10.2.

    Problem I'm having is I'm testing against an attribute that's calculated as it's used in the data.

    To equate to your example it's possible

    [Month].&[1] doesn't exist

    and

    Month.&[2] does.

    The script saves but the calculations in the case statement after [Month].&[1] are invalid. Is there a way around this (testing currentmember against member that may or may not exist)?

     

  • 04-16-2008 9:01 PM In reply to

    Re: Listing 10.2 and testing non-existant values

    <member> is NULL will return True if the member doesn't exist.

  • 04-17-2008 2:50 AM In reply to

    • Acius
    • Top 10 Contributor
    • Joined on 01-16-2006
    • Posts 53

    Re: Listing 10.2 and testing non-existant values

    When I test if the member is null I still get the run time #VALUE! error (because the member doesn't exist.)

    I've found an alternative thanks

    instead of

    CASE

    WHEN  [INDICATOR].[Numerator YTD Calc].CurrentMember Is [INDICATOR].[Numerator YTD Calc].&[P]

    if I use 

    CASE

    WHEN [INDICATOR].[INDICATOR].CurrentMember.Properties("Numerator YTD Calc") = "P"

    it handles it OK

     

     

Page 1 of 1 (3 items)
Copyright © 2005 Prologika, LLC
Powered by Community Server (Commercial Edition), by Telligent Systems