Hi,
I'm working with two SharePoint lists in a simple app.
In one list, I have the e-mail addresses in the title column and the name of the organisation the person belongs to in a separate column.
I want to show the organisation depending on the user who is logged in.
I managed to it with this "LookUp(Schulzugehörigkeit; Title = User().Email; Organisation)"
However, the LookUp is case-sensitive. I know all the e-mail adresses, but I don't know if the names are capitalised (some are).
Is there a way to make this lookup case-insensitive to make it more robust?
Solved! Go to Solution.
You use the Lower or Upper function to convert the Title and email addresses so the result in same case before the comparison:
LookUp(Schulzugehörigkeit; Lower(Title) = Lower(User().Email); Organisation)
------------
If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.
You use the Lower or Upper function to convert the Title and email addresses so the result in same case before the comparison:
LookUp(Schulzugehörigkeit; Lower(Title) = Lower(User().Email); Organisation)
------------
If you like this post, give a Thumbs up. Where it solved your request, Mark it as a Solution to enable other users find it.
Perfect!
Thank you so much!
This is actually unnecessary.
Lookup in Sharepoint is already case insensitive.
Furthermore, adding Lower(...) makes it non-delegable - so not only is it unnecessary, but it could be detrimental too.
I'll check that out...
I think we had the problem in the past that filters in powerapps against user mails stored in SP lists did not work if the case did not match the user profile.
I'll look into it.
Lookup is case sensitive and that is the problem. That's why we try to find solution.
But you're right in other conclusion: this makes the Lookup non-delegable and this creates even worse problem.