Power Apps: User Filter - SP & Dataverse

Key insights

• User() returns the logged-in user’s core details (Email, FullName, Image) and drives user-specific filters in Power Apps.
  Use User() values in your Filter formulas to show only records for the current user.
• SharePoint and Dataverse store creators differently, so filter slightly differently for each.
  For SharePoint, match the list’s Created By or Author email; for Dataverse, match the record owner or the user’s EntraObjectId (Azure AD object id) or systemuser lookup.
• StartsWith and simple text filters make responsive searches: use StartsWith or the "in" operator for single- or multi-column searches.
  Combine conditions with || to search across multiple fields and keep filters readable and fast.
• Group-based and people filters let apps show data for selected users or group members.
  Use directory connectors (like Office 365 Users) for multi-select people search and to check Entra/Microsoft Entra group membership before filtering results.
• Dataverse views offer server-side filtering and simplify app logic: load and apply table views in a Gallery instead of rebuilding complex formulas in the app.
  This reduces app changes and avoids republishing when filter rules change.
• Delegation and performance matter: prefer delegable queries and filter at the data source to avoid client-side limits.
  Test with different users, check delegable functions, and move heavy logic into Dataverse views or server-side filters for best speed and security.

Introduction

This article summarizes a YouTube video by Shane Young [MVP] that explains how to filter galleries in Power Apps so they show only the logged-in user's records. The video focuses on practical differences between filtering against SharePoint and Dataverse, and it demonstrates formulas and connectors for real-world apps. In addition, Shane highlights the role of the User() function in PowerFX and shows how to filter by both identity fields and plain text columns. Overall, the presentation aims to help makers choose the right approach for their data sources and scenarios.

What the Video Shows

First, Shane walks viewers through simple gallery filters that restrict results to the current user by using identity fields such as Created By. He then explains how to apply the User() function to obtain the logged-in user's details and plug them into filter formulas. Next, he contrasts the mechanics for SharePoint and Dataverse, calling out where field types and internal identifiers differ. Consequently, viewers get a step-by-step look at both formula syntax and practical testing techniques.

The video also covers text-based filtering as a complementary technique, useful when records store user names or email strings rather than complex identity objects. Shane demonstrates multi-select people controls and how to use selections to filter related data across lists or tables. He highlights that modern UI patterns can combine keyword search with person pickers to create flexible experiences. Thus, the session balances core formulas with user interface ideas that make filtering intuitive.

SharePoint Versus Dataverse: Key Differences

Shane emphasizes that filtering in SharePoint often uses the list's Created By person column, which stores user data as a complex record. By contrast, Dataverse frequently exposes an identity using an identifier like EntraObjectId, and that difference changes how you write filters. Therefore, a formula that works against Dataverse may require adjustment to run against a SharePoint list. As a result, makers must inspect the data model before copying formulas between systems.

Moreover, delegation limits and connector semantics vary between the two platforms, which affects app performance on large data sets. For example, some operators are not delegable to SharePoint, forcing client-side filtering that slows loading. Dataverse often supports richer server-side queries and view-based filtering that reduce client work. Consequently, the choice between tools has real implications for scalability and responsiveness.

Finally, identity resolution can be a hidden challenge when users have multiple accounts or when syncing occurs across tenants. Shane stresses verifying that the directory identifier you use matches the stored user field to avoid mismatches. He also notes that Office connectors may return different structures, so testing with real users is essential. Thus, careful validation prevents lost or hidden records in production apps.

Advanced Techniques and UI Considerations

The video introduces advanced options such as using multi-select people pickers to build dynamic filters that reflect multiple selected users. Shane shows how selecting several people can drive a gallery filter so that the app displays records for any selected person. He also explains how using view-based filtering from Dataverse can offload complex logic to the server and reduce app maintenance. Consequently, these techniques can improve both performance and manageability when used appropriately.

Additionally, modern UI patterns can merge keyword search with person-based filters to give users fast, familiar controls. Shane suggests combining text search, checkboxes, and person pickers to let users refine results quickly. However, he cautions that richer interfaces add development and testing work, especially across different devices. Therefore, teams should weigh UI complexity against the expected user benefit.

Tradeoffs and Practical Challenges

Balancing security, performance, and maintainability poses the main tradeoff when filtering by user. On one hand, server-side filtering and Dataverse views support scale and centralized logic, but they may require higher licensing or more admin work. On the other hand, client-side filters against SharePoint are straightforward to implement but can falter with large lists due to delegation limits. Consequently, teams must consider both immediate needs and long-term operational overhead.

Another challenge is mapping identity data consistently across connectors and tenants. Mismatched identifiers or differences in how person columns store data can lead to incorrect filters. Shane recommends rigorous testing with multiple user accounts and real-world samples to catch these issues early. Accordingly, planning and documentation help reduce surprises during deployment and handoff.

Practical Takeaways and Recommendations

In summary, Shane Young's video offers practical guidance for filtering galleries by user in Power Apps, and it emphasizes understanding your data model first. For quick solutions, filter by the Created By person column in SharePoint or use the identity field in Dataverse, but always validate the stored identifier. For scalable apps, prefer server-side views and delegable queries where possible, and test performance on realistic datasets.

Finally, combine clear UX patterns with thoughtful backend choices to balance usability and maintainability. By following these practices, makers can build apps that show the right data to the right users while minimizing surprises in production. The video serves as a practical how-to and a reminder that small differences in data models change how filters need to be written and tested.

Keywords

Power Apps filter by current user, Power Apps filter SharePoint, Power Apps filter Dataverse, Filter records by user Power Apps, Power Apps current user formula, SharePoint user-based filtering Power Apps, Dataverse user filtering Power Apps, Power Apps filter gallery by user