Trouble filtering a gallery based on current user

[water-guy-5]

Hello,

I have built an expense report application for my organization. On my end, everything is running smoothly, but others are experiencing a really frustrating issue. 

I have a few screens. The main screen filters to show the current logged in user's requests. So, the function looks something like:

SortByColumns(Filter('Expense Records', 'Created By'.DisplayName = User().FullName, Or(varFilter ="All", 'Overall Status' = varFilter)), "DateEntered", SortOrder.Descending)

The bold portion is what I am referring to, the rest related to variables and filtering buttons. When a user creates an entry, it triggers a flow that goes to the supervisor. On the backend, I have an Active Directory connection that finds the user, finds their supervisor based on our org. chart, and then it saves the supervisors email as one of my columns in my SP list.

I have a VERY similar screen for supervisors. Where it is set to show entries where the Supervisor Approver Email = the user logged in. So, if a supervisor is in the application, they can only see their employees' entries.

Here is the logic for this one:
SortByColumns(Filter('Expense Records', SupervisorApproverEmail = User().Email, Or(varFilter ="All", 'Supervisor Status' = varFilter)), "DateEntered", SortOrder.Descending)

Despite the logic being almost the exact same for the main page, this part is failing. When I manually switch the supervisor approver email to mine, it works (just to test), but for others, it is failing.

Anyone have any ideas as to what the issue could be? This is extremely frustrating.

Thanks!

Here is the page that is working correctly.

Here is the page that is failing.

[RJM07]

So when your email is set to the Supervisors email, it works and you can see what you need to see? But when your email isn't set as the supervisors email, you can't see any data...?

Doesn't that mean it's working correctly?

[water-guy-5]

@RJM07 I must have not explained correctly.

For example, lets say the Supervisor Approver Email column is set to John Doe's email and is jdoe@email.com
When looking on John's computer and he is logged into PowerApps, it should show on his end. It does not. So, as a test, I would go into the SP list and change it to my email and check on MY computer. It shows up when my email matches on my computer but does not show up for others when their email matches on their computer.

[RJM07]

Right I see... silly question, but these users do have access to the sharepoint list?

[water-guy-5]

@RJM07 Not a silly question, but yes, the list settings is set to contribute for all (or something along those lines). Our head IT director helped with managing the privileges so everyone has read/write access. Everyone has been able to add to the list so far, so I don't believe that is the issue, but it is worth exploring again.

[RJM07]

It's a strange issue becasue I use User().FullName in my app, and so far (touch wood) I have never had any issues... 

The only thing I can think of is that it's denying read access. Either that or User().Email is collecting the wrong data. Just for testing purposes, try User().FullName and see if that makes any difference. (You'll have to swap the email for the full name in the sharepoint list though, of course 🙂

[LaurensM · Accepted solution]

Hi @water-guy-5,

As @RJM07 correctly stated, it might be beneficial to double check the permissions for your list.

Other possible troubleshooting you could do is the following:

• Double check whether User().Email actually returns the exact email that is stored in SharePoint (not only for you, but also the user(s) experiencing the issue) - sometimes they differ and Office365Users.MyProfileV2().mail might be a good alternative
  
  
• Pay close attention to small differences in capitalization and trailing/leading spaces in your SP column compared to the output of the User().Email function.
  
  
• The following adjustment will take care of any capitalization or trailing space discrepancies Filter('Expense Records', StartsWith(SupervisorApproverEmail, User().Email), Or(...
  • To solve the issue regarding leading spaces, you could enclose the Supervisor field with a Trim() function, but this will make it non-delegable

I hope this helps!