Forum Discussion
lookupValue in the same table
Hi All,
I am trying to populate a column (Manager ID) using the Lookupvalue but getting error mesage that says "A table of multiple values was supplied where a single value was expected."...following is the DAX I used -
Appreciate any help
Hi,
You can use this DAX:
Manager ID = LOOKUPVALUE('OrgChart_Raw'[Employee ID],'OrgChart_Raw'[Name],'OrgChart_Raw'[Manager Name])If this helps, I apreciate you give a kudo and mark as the solution. Thanks
5 Replies
- mauriciosoteroResolver III
Hi,
You can use this DAX:
Manager ID = LOOKUPVALUE('OrgChart_Raw'[Employee ID],'OrgChart_Raw'[Name],'OrgChart_Raw'[Manager Name])If this helps, I apreciate you give a kudo and mark as the solution. Thanks
- mraka9Helper III
Hi, I have a similar problem.
I have empty rows in the "Manager Name" search column and need to find values only for those rows for which there is a name. I can't solve the problem in any way, but I get a notification: A table with more values is given when an individual value was expected.
- ChrisMendozaResident Rockstar
Anonymous -
Is [Manager Name] ever going to be equal to [Employee Name]? I would take a look at https://www.daxpatterns.com/parent-child-hierarchies/ to handle something like this.
- AnonymousNot applicable
Hi ChrisMendoza , yes in the employee column I have all the employees in the organization including the manager, I just want to create a Manager ID column beside manager name column, and all the IDs are in the Employee ID column. I can do it in excel using the vlookup function but wanted to see if this can be done in Power BI.
Thanks
- ChrisMendozaResident Rockstar
Anonymous -
Anonymous wrote:... says "A table of multiple values was supplied where a single value was expected."...
From https://dax.guide/lookupvalue/: If multiple rows match the search values and in all cases Result_Column values are identical then that value is returned. However, if Result_Column returns different values an error is returned.
If you are able to create your table with that constraint LOOKUPVALUE works fine within the same table.