Forum Discussion

charleshale's avatar
charleshale
Continued Contributor
2 years ago
Solved

Bug in Lookupvalue() ?

I am experiencing a result wherein a simple lookupvalue() for the exact same value sometimes returns blank and sometimes doesnt.   I have never seen this before.   Here's the detail:  I am adding a...
Need Help
  • Greg_Deckler's avatar
    Greg_Deckler
    2 years ago

    charleshale So LOOKUPVALUE will return BLANK if more than one row is returned. I've encountered some issues with it honestly which is why I always use MAXX( FILTER( ... ), ... ) instead.

Greg_Deckler's avatar
Greg_Deckler
Community Champion
2 years ago

charleshale So LOOKUPVALUE will return BLANK if more than one row is returned. I've encountered some issues with it honestly which is why I always use MAXX( FILTER( ... ), ... ) instead.

  • charleshale's avatar
    charleshale
    Continued Contributor
    2 years ago

    The greatest Greg_Deckler.  You have solved my problem with your insight and reflected glory!  So - fantastic point as usual: yes that maxx is better.      Here's what I did, below.

     

     

     

     

     

    Try7 = 
CALCULATE(
    maxx(Json, json[WBS2.1]),
    FILTER(
        Json,
        Json[Id] = 'Stripe Raw'[Originating Patch]
    )
)

     

     

     

     However, the problem remained the same.

     

    This got me thinking of a totally different solution: adding an all() after calculate.

     

     

     

    _OrigPatchNameLkup = 
CALCULATE(
    maxx(json, Json[WBS2.1]),
    FILTER(
        Json,
        Json[Id] = 'Stripe Raw'[Originating Patch]
    ), all('Stripe Raw')
)

     

     

     


    This worked.   Somehow there must be a filter context somewhere in my table that was causing the blanks.  I still don't see exactly where, but the column and measure now work.  How interesting!   Thank you for this varsity-level point.

     

    Charlie