Share
Report
8Hi all,
I found a very strange behavior in a LookUp statement which I can't explain.
Maybe someone observed similar behavior or has an explanation for it.
Purpose of the app is to show a teams members and when they will be in or out of office.
This is based on a SharePoint list with a person field (User), two date fields (Start and End) and a select field (Type).
For the display, I use two nested galleries, the outer gallery with a distinct call to the list to get one entry per user and the inner gallery with a lookup call to find the state for the specific date.
The outer gallery has a hidden label (LabelEmail) to hold the User.Email received from the distinct call.
In the LookUp, I use this label to find the corresponding dataset, so I compare with User.Email = LabelEmail.Text.
Now this worked very well in my tests, but for one user it did not work.
Even though I confirmed, that both values are spelled exactly the same, LookUp does not return a dataset.
Changing the comparison to Lower(User.Email) = Lower(LabelEmail.Text) does return a result, but causes a delegation warning and thus slows down performance.
I have no idea why the first comparison does not work, but the second does, especially since both values are from the same source and must be identic.
Also there are no capitals in the strings.
Any ideas on why this happens or how to get around delegation warning are appreciated.
All responses (
Answers (
