Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
Tho_Chr
New Member

Problem with lookup function

Hi all,

 

I have a problem with the below mentioned query. I only get values returned in approximately 25,000 rows out of 1,132,000 expected returns. The is a huge variety in YearMonth and currency returned. I believe that the problem could be that the column (Currency_from_slicer) is itself a lokup table and the it becomes a HEN AND THE EGG problem - but I'm not sure if that's the issue.

 

I use the same function with another table where I lookup in the Currency_Exchange_table (2) and here the outcome is as expected.

 

Any idea how to go around this?

 

amt_DKK_to_Euro_Exchange = LOOKUPVALUE('Currency_exchange_tabel (2)'[Calculated Exchange];'Currency_exchange_tabel (2)'[YearMonth];safe_tc40[YearMonth];'Currency_exchange_tabel (2)'[Currency_Numeric_Code A];safe_tc40[currency_from_slicer])

1 REPLY 1
lbendlin
Super User
Super User

would it be possible to connect the tables in a data model and avoid the LOOKUPVALUE altogether?

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors