Thanks for providibg the screenshot. Before discussing the fix:
Recap… (read carefully)
User Rer is of type USER
input email is of type TEXT
when doing a search, you must search for a data type. You’re searching for users, which is great.
The next thing you tried is to add a constraint. You want to get the user who is the user ref. You’re using an input email to match the email to the user ref. The problem is, that when comparing a data type to an input you need to make sure that both things You’re comparing are the same type. Right now, you’re comparing input email (which is of type TEXT) to a field called User Ref (type USER). because USER and TEXT are not the same type, bubble will throw an error. This is normal.
What you’re really trying to do is compare user Ref’s email (which is type TEXT) to the input email (type TEXT). This will work.
In conclusion …
You must always compare two things of the same type.
TEXT and USER are incompatible, i.e, not the same
To fix, compare to User Ref’s email (TEXT) to input email (TEXT).
If you’re still not able to get it to work, please read this article and watch the linked video:
The content format of the input isn’t really relevant. Have a look at your user object (the screenshot you sent me)
What you’ll see is that email is of type (either email or text, but they are essentially the same thing).
The problem you are facing is exactly as I said: you must compare two of the same types. Right now you’re constraint says User Ref = input email’s value. This is incorrect.
The type on the left of the = is user. The type on the right of the = is email. You can’t say find me the user that is equal to this email. That doesn’t make sense. You need to say “Find me the user who’s EMAIL is this EMAIL (the input)”
I strongly suggest reading the article I linked as if you read that and watch the video then this question will be solved.