Is LookUp faster than Filter in Power Apps?

Not meaningfully on server data sources, because the query is executed remotely either way. On local collections, LookUp is marginally faster because it stops at the first match rather than scanning every row. Choose LookUp for readability and the correct return type, not for speed.

Why does my Search function show a delegation warning on SharePoint?

Because Search is not delegable to SharePoint. There is no workaround at the function level. Either use StartsWith inside Filter, pre-filter the set below your row limit, or move the data to Dataverse or SQL Server.

Can I use Filter and Search together in one formula?

Yes, and you usually should. Nest the delegable Filter on the inside and Search on the outside: Search(Filter(Employees, IsActive = true), txtSearch.Text, "FullName"). The Filter runs server-side and Search operates on the reduced set.

How do I get a single record without using LookUp?

First(Filter(Table, Condition)) returns the same record. It is valid but more verbose, and it makes your intent less obvious to whoever maintains the app next. Use LookUp.

Why does LookUp return blank instead of throwing an error when nothing matches?

By design. Power Fx treats "no match" as a blank value so your app keeps running rather than showing an error screen. Guard it explicitly with Coalesce(LookUp(...), "Default value") when a blank would confuse the user.

Does Search do partial word matching in the middle of a string?

Yes. Search performs a substring "contains" match, so typing nal matches both "Analyst" and "Financial". That is exactly what StartsWith cannot do, which is the trade-off you accept when you switch to a delegable formula.

Can Search look at more than two columns?

Yes, pass as many quoted column names as you need: Search(Employees, txtSearch.Text, "FullName", "JobTitle", "Email"). Every additional column adds work, so on non-delegable sources keep the list tight.

Filter vs Search vs LookUp in Power Apps (Complete Guide)

Three functions, one job that sounds identical: find records. That is exactly why new Power Apps makers pick the wrong one, and then spend an afternoon wondering why the gallery is empty or why the delegation warning refuses to go away.

I have lost count of how many Power Apps apps I have opened where someone used Filter to grab a single record, then wrapped the whole thing in First() to make it behave. It works, but it is the long way round.

In this tutorial, I will show you exactly what each of these three functions returns, when to reach for each one, how they behave with delegation, and the mistakes that cause the most support tickets.

Table of Contents:

What Filter, Search, and LookUp Actually Do in Power Apps

All three functions belong to the same family in Power Fx. They all reduce a table down to the rows you care about.

The difference is what comes back out.

Filter returns a table. It can be zero rows, one row, or ten thousand rows.
Search returns a table too, but you do not write a condition. You hand it a search string and a list of text columns.
LookUp returns a single record, or a single value if you give it a third argument.

That one distinction, table versus record, causes most of the confusion, because Power Fx will not let you use a table where a record is expected.

Use them when:

Filter – you need many matching rows, or you need precise logic (>, <, And, Or, date ranges).
Search – you are building a search box and want a “contains” match across a few text columns.
LookUp – you need one record, usually to read a property off it, like an email address, a price, or an ID.

Don’t use them when:

Don’t use Filter to get one record and then wrap it in First(). Use LookUp.
Don’t use Search for numeric, choice, or boolean comparisons. It only works on text columns.
Don’t use LookUp when more than one row can match and you actually care about all of them. It silently returns only the first.

The Short Answer

If you only read one section, read this one.

Do you need more than one row back? → Filter
Is the user typing into a text box and expecting “contains” behavior? → Search
Do you n