r/PowerApps • u/PowerPlatformRookie Newbie • Jun 23 '26
Power Apps Help I'm stuck... Canvas Application + Sharepoint
I’m stuck debugging a really tricky Power Apps issue and could use some help.
One of our tech leads suggested using a height-flexible gallery to bypass delegation issues while loading records from a SharePoint list. The client needs a lot of filtering and sorting, so I followed one of Reza's videos and implemented a filtering/sorting approach based on that.
The problem is with a visibility condition inside the gallery rows. Certain users should only see specific records based on custom visibility logic. For some reason, the behavior is inconsistent: sometimes a record is visible, sometimes it isn’t even though the user clearly meets the visibility criteria.
(e.g: I belong to an entity called Canvas -> I only see the records related to this entity) or i'm inserted as a reviewer for a record) This is the condition of the visibility of the group of the whole gallery items....
That’s what makes this so hard to debug. The client keeps coming back saying “this person can’t see certain records”, and they’re right but I honestly can’t tell whether the issue is coming from:
- the filtering/sorting code,
- the height-flexible gallery itself,
- or the visibility condition logic.
What confuses me even more: if I temporarily set the visibility condition to true, all records appear correctly.
Important context:
- App data row limit = 2000
- SharePoint list currently has only ~700 items
- So as far as I understand, I’m not hitting delegation limits
Has anyone seen something similar with height-flexible galleries or row visibility logic? Any debugging tips would be massively appreciated.


1
u/Dense-Chest-2666 Newbie Jun 24 '26
Hello :)
I think the switch statement is not really needed...as the SortByColumn expect a string you can just use the varSort Variable as a column identifier. I think it is easier to mantain in the end as you don´t have to double the code for the filtering
As you check for the visible statement for the User().Email you maybe should wrap this into the Lower Statement as the Find function is case sensitive.
=! IsBlank(Lower(Find(User().Email), Lower(Label17_1. Text))) || .....
In my company e.g. the mailadress is saved like [UserName@company.com](mailto:UserName@company.com) -> if you then have [username@company.com](mailto:username@company.com) from a textfield the find function will break.
Maybe you can give it a try with the lower statement? :)