What Are PowerApps Lookup And Its Use Cases

PowerApps Lookup Functions and Use Cases

PowerApps LookUp, Filter, and Search are the three core data retrieval functions in Power Fx. LookUp returns the first matching record. Filter returns all matching records. Search returns records matching a partial text string. This guide covers each function's syntax, performance best practices, delegation limits, and enterprise use cases.

Key facts

• LookUp returns the first record matching a formula condition. Filter returns all matching records.
• Power Fx is the formula language for Power Apps — similar to Excel formulas.
• Delegation limit: by default, Power Apps retrieves a maximum of 500 records from data sources without delegation. Configure up to 2,000.
• Cross-source lookups (Dataverse to SharePoint, for example) must be handled in app logic — no server-side join between different data sources.
• EPC Group builds enterprise Power Apps for regulated industries. Engagements start at $25,000.
• EPC Group holds core Microsoft Solutions Partner designations including Modern Work and Digital & App Innovation.

The LookUp Function

LookUp finds the first record in a table that satisfies a formula. It returns either the entire record or a specific field value from that record.

LookUp Syntax

• LookUp(DataSource, Condition) — returns the first matching record.
• LookUp(DataSource, Condition, FieldName) — returns a specific field from the first matching record.
• Example: LookUp(Employees, EmployeeID = SelectedID, FullName) — returns the full name of the employee whose ID matches the selection.

When to Use LookUp

• Retrieving a single related record — the manager's email for the selected employee.
• Populating a form field based on another field's selection.
• Validating that a record exists before submitting a form.
• Getting a calculated value (price, rate, category) from a lookup table based on user input.

The Filter Function

Filter returns all records from a table that satisfy a condition. It is the correct function when you need multiple results, not just the first match.

• Filter(DataSource, Condition) — returns all matching records.
• Example: Filter(Orders, CustomerID = SelectedCustomer && Status = "Open") — returns all open orders for the selected customer.
• Use Filter as the Items source for galleries, tables, and dropdowns.
• Filter supports multiple conditions using && (AND) and || (OR) operators.

The Search Function

Search returns records where a specified text column contains a search string. It is used for user-driven search experiences in galleries.

• Search(DataSource, SearchString, ColumnName) — returns records where the column contains the string.
• Example: Search(Products, SearchInput.Text, "ProductName") — filters a gallery as the user types.
• Search is case-insensitive by default.
• Combine with Filter for searches that also apply status or category conditions.

Delegation — The Most Important Performance Concept

Delegation determines whether a query runs on the server or on the Power Apps client. Server-side delegation is faster and required for large datasets.

• Delegable — The query runs on the data source server. All matching records return. Best for large datasets.
• Non-delegable — Power Apps downloads up to 2,000 records and filters locally. Records beyond 2,000 are invisible to the query.
• Dataverse supports delegation for most Filter and LookUp conditions. Ideal for enterprise Power Apps.
• SharePoint lists support delegation for simple equality checks. Complex formulas (StartsWith on non-indexed columns) are non-delegable.
• A yellow warning triangle in Power Apps Studio indicates a non-delegable operation.

Cross-Source Lookups

Power Apps cannot perform server-side joins between different data sources. Cross-source lookups must be handled in app logic.

• Example: looking up a Dataverse record based on a value from a SharePoint list — no automatic join.
• Workaround: use two separate queries. First, get the SharePoint value. Then, use that value as input to a Dataverse LookUp.
• For high-volume cross-source scenarios, store the joined data in Dataverse and query from one source.

Enterprise Power Apps Use Cases

LookUp, Filter, and Search are the core functions in these common enterprise Power Apps patterns.

• Employee directory app — Search and LookUp on Dataverse Employee table. Department Filter for org chart navigation.
• Work order management — Filter open work orders by technician and status. LookUp asset details from equipment table.
• Expense approval — Filter expense submissions by approver. LookUp policy limits from a rates table.
• Inventory management — Filter items by warehouse and category. LookUp reorder points from a SKU configuration table.
• Safety incident reporting — Filter incidents by date range, location, and type. LookUp regulatory reporting thresholds.

Frequently asked questions

What does the LookUp function do in Power Apps?

LookUp searches a table and returns the first record (or a specific field from that record) that satisfies a condition. It is the Power Apps equivalent of VLOOKUP in Excel, but for data sources like Dataverse and SharePoint lists.

What is the difference between LookUp and Filter in Power Apps?

LookUp returns the first matching record. Filter returns all matching records. Use LookUp when you need one result (a user's profile, a product's price). Use Filter when you need multiple results (all open orders, all active employees).

What is delegation in Power Apps?

Delegation means the query executes on the server (Dataverse, SharePoint) rather than downloading all data to the client. Delegable queries handle any dataset size. Non-delegable queries are limited to 2,000 records. Use Dataverse for the best delegation support.

How do I handle cross-source lookups in Power Apps?

Power Apps does not support cross-source server-side joins. Use sequential queries: get the value from Source A, then use it in a LookUp against Source B. For high-volume needs, consolidate data into Dataverse using Power Automate flows.

Does EPC Group build enterprise Power Apps?

Yes. EPC Group designs and builds Power Apps for work order management, employee portals, safety incident reporting, expense management, and custom Dynamics 365 extensions. Regulated-industry deployments include HIPAA and SOC 2 data controls. Engagements start at $25,000.

Schedule a Power Apps consultation

Talk to an EPC Group Power Platform architect about your Power Apps design, Dataverse modeling, or regulated-industry app requirements. Call (888) 381-9725 or request a 30-minute discovery call.