Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
Hi Community,
am trying to find something similar to Vlookup to apply on 2 tables in power bi.
I have one table (meaccount) which has unique values for every client, and I have table (meaccounthistory) that has a column [Country] which I need to add it as table (meaccount)
It's worth mentioning that table (meaccounthistory) has multiple rows for same account, and I would like to distinguish the Country from the latest record
I tried using the lookupvalue, but am not succeeding to complete it.
Appreciate your help
Solved! Go to Solution.
@majdkaid22 @kcantor Merge queries is easiest way but probably will return multiple rows ( since we matching values from many to one ) so then remove duplicates on ID and good to go.
You can try with DAX also in case you have a column in meAccountHistory , like date or transaction ID that defines the latest record.
Create a calculated column :
BringCountry = LASTNONBLANK(meAccountHistory[IsoCountry];MAX(meAccountHistory[Date])) or LASTNONBLANK(meAccountHistory[IsoCountry];MAX(meAccountHistory[TransactionID]))
This way you avoid returning multiple values.
Be careful though that it will bring the latest IsoCountry so if an account change country it will show him as the latest country. Of cource if you use filter from meAccount table.
Hope that helps.
@majdkaid22 @kcantor Merge queries is easiest way but probably will return multiple rows ( since we matching values from many to one ) so then remove duplicates on ID and good to go.
You can try with DAX also in case you have a column in meAccountHistory , like date or transaction ID that defines the latest record.
Create a calculated column :
BringCountry = LASTNONBLANK(meAccountHistory[IsoCountry];MAX(meAccountHistory[Date])) or LASTNONBLANK(meAccountHistory[IsoCountry];MAX(meAccountHistory[TransactionID]))
This way you avoid returning multiple values.
Be careful though that it will bring the latest IsoCountry so if an account change country it will show him as the latest country. Of cource if you use filter from meAccount table.
Hope that helps.
@konstantinos it worked as a treat. many thanks mate!
as you, @kcantor and @Anonymous said, the more proper way is to have it done in query editor and merge both and have (meaccount) with a country column.
Better to save on some less Dax formulas in the front end.
Many thanks
Majd
Create new column:
ISOCountryName = lookup('meAccount'[CountryColumn] , 'meAccount'[AccountID] , 'meAccountHistory'[AccountID )
I can't seem to find the country in your meAccount table though. If you have it than the above should work
Edit: You should also take the summary off from AccountID in your table as you probably won't be doing any sums with ID's 🙂
Default summarization = Do Not Summarize
@Anonymous thanks mate
The country is in the (meaccounthistory) table, and I want to have it added to (meaccount)
How will that work?
ISOCountryName 2 = lookup('meAccountHistory'[ISOCountryName] , 'meAccountHistory'[AccountID] , 'meAccount'[AccountID )
My challenge here that hiaccounthistory has mutiple records for the same AccountID.
How can I trigger this?
Strange setup of data where the account table does not have a country but the history does.
History doesn't have a unique set of countries so you have to make them unique either with creating another query where you remove all duplicates.
You're actually right. I will ask the developers to add the country to the account list.
this makes no sense
Cheers,
Majd
@majdkaid22 You should pull them both in through Query Editor and merge the Queries to add the column you need. This method makes VLOOKUP unnecessary.
Proud to be a Super User!
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 |
|---|---|
| 48 | |
| 45 | |
| 41 | |
| 20 | |
| 17 |
| User | Count |
|---|---|
| 69 | |
| 64 | |
| 32 | |
| 31 | |
| 27 |