Error in Dax Studio for a simple LOOKUPVALUE
up vote
0
down vote
favorite
I am new to PBI and DAX. I am using Dax Studio to explore some functions. I am trying to do a look up value on a simple table. The table is Users and it has 2 columns, Name and ClientID. This is my DAX formula that I have in the Studio editor
LOOKUPVALUE(Users[ClientID], [Name], "john smith")
When I run it I get this output
Thank you in advance
powerbi dax
add a comment |
up vote
0
down vote
favorite
I am new to PBI and DAX. I am using Dax Studio to explore some functions. I am trying to do a look up value on a simple table. The table is Users and it has 2 columns, Name and ClientID. This is my DAX formula that I have in the Studio editor
LOOKUPVALUE(Users[ClientID], [Name], "john smith")
When I run it I get this output
Thank you in advance
powerbi dax
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am new to PBI and DAX. I am using Dax Studio to explore some functions. I am trying to do a look up value on a simple table. The table is Users and it has 2 columns, Name and ClientID. This is my DAX formula that I have in the Studio editor
LOOKUPVALUE(Users[ClientID], [Name], "john smith")
When I run it I get this output
Thank you in advance
powerbi dax
I am new to PBI and DAX. I am using Dax Studio to explore some functions. I am trying to do a look up value on a simple table. The table is Users and it has 2 columns, Name and ClientID. This is my DAX formula that I have in the Studio editor
LOOKUPVALUE(Users[ClientID], [Name], "john smith")
When I run it I get this output
Thank you in advance
powerbi dax
powerbi dax
asked Nov 12 at 17:33
Jake
1018
1018
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
I'm guessing it wants a fully qualified column name.
Try this:
LOOKUPVALUE(Users[ClientID], Users[Name], "john smith")
Edit:
DAX Studio generally expects table output rather than measure output. You can get around this by turning your value into a table.
Try this:
EVALUATE {LOOKUPVALUE(Users[ClientID], Users[Name], "john smith")}
Thank you for the suggestion. I tried this and I am getting the same error. When I create a column in PBI desktop and input the formula there it all works fine. I am just trying to figure out how to use DAX Studio. I would prefer not to make a column when I test functions. I was hoping I could use DAX Studio as a playground to test around in
– Jake
Nov 12 at 18:29
Please see my edit.
– Alexis Olson
Nov 12 at 18:45
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
I'm guessing it wants a fully qualified column name.
Try this:
LOOKUPVALUE(Users[ClientID], Users[Name], "john smith")
Edit:
DAX Studio generally expects table output rather than measure output. You can get around this by turning your value into a table.
Try this:
EVALUATE {LOOKUPVALUE(Users[ClientID], Users[Name], "john smith")}
Thank you for the suggestion. I tried this and I am getting the same error. When I create a column in PBI desktop and input the formula there it all works fine. I am just trying to figure out how to use DAX Studio. I would prefer not to make a column when I test functions. I was hoping I could use DAX Studio as a playground to test around in
– Jake
Nov 12 at 18:29
Please see my edit.
– Alexis Olson
Nov 12 at 18:45
add a comment |
up vote
2
down vote
accepted
I'm guessing it wants a fully qualified column name.
Try this:
LOOKUPVALUE(Users[ClientID], Users[Name], "john smith")
Edit:
DAX Studio generally expects table output rather than measure output. You can get around this by turning your value into a table.
Try this:
EVALUATE {LOOKUPVALUE(Users[ClientID], Users[Name], "john smith")}
Thank you for the suggestion. I tried this and I am getting the same error. When I create a column in PBI desktop and input the formula there it all works fine. I am just trying to figure out how to use DAX Studio. I would prefer not to make a column when I test functions. I was hoping I could use DAX Studio as a playground to test around in
– Jake
Nov 12 at 18:29
Please see my edit.
– Alexis Olson
Nov 12 at 18:45
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
I'm guessing it wants a fully qualified column name.
Try this:
LOOKUPVALUE(Users[ClientID], Users[Name], "john smith")
Edit:
DAX Studio generally expects table output rather than measure output. You can get around this by turning your value into a table.
Try this:
EVALUATE {LOOKUPVALUE(Users[ClientID], Users[Name], "john smith")}
I'm guessing it wants a fully qualified column name.
Try this:
LOOKUPVALUE(Users[ClientID], Users[Name], "john smith")
Edit:
DAX Studio generally expects table output rather than measure output. You can get around this by turning your value into a table.
Try this:
EVALUATE {LOOKUPVALUE(Users[ClientID], Users[Name], "john smith")}
edited Nov 12 at 18:45
answered Nov 12 at 18:01
Alexis Olson
11.3k21633
11.3k21633
Thank you for the suggestion. I tried this and I am getting the same error. When I create a column in PBI desktop and input the formula there it all works fine. I am just trying to figure out how to use DAX Studio. I would prefer not to make a column when I test functions. I was hoping I could use DAX Studio as a playground to test around in
– Jake
Nov 12 at 18:29
Please see my edit.
– Alexis Olson
Nov 12 at 18:45
add a comment |
Thank you for the suggestion. I tried this and I am getting the same error. When I create a column in PBI desktop and input the formula there it all works fine. I am just trying to figure out how to use DAX Studio. I would prefer not to make a column when I test functions. I was hoping I could use DAX Studio as a playground to test around in
– Jake
Nov 12 at 18:29
Please see my edit.
– Alexis Olson
Nov 12 at 18:45
Thank you for the suggestion. I tried this and I am getting the same error. When I create a column in PBI desktop and input the formula there it all works fine. I am just trying to figure out how to use DAX Studio. I would prefer not to make a column when I test functions. I was hoping I could use DAX Studio as a playground to test around in
– Jake
Nov 12 at 18:29
Thank you for the suggestion. I tried this and I am getting the same error. When I create a column in PBI desktop and input the formula there it all works fine. I am just trying to figure out how to use DAX Studio. I would prefer not to make a column when I test functions. I was hoping I could use DAX Studio as a playground to test around in
– Jake
Nov 12 at 18:29
Please see my edit.
– Alexis Olson
Nov 12 at 18:45
Please see my edit.
– Alexis Olson
Nov 12 at 18:45
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53267290%2ferror-in-dax-studio-for-a-simple-lookupvalue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown