Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
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])
would it be possible to connect the tables in a data model and avoid the LOOKUPVALUE altogether?
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 3 | |
| 2 | |
| 2 |
| User | Count |
|---|---|
| 8 | |
| 7 | |
| 6 | |
| 6 | |
| 5 |