DEV Community

Cover image for Power Apps Filter vs LookUp vs Collections (Quick Guide for Beginners)
Matt Hummel
Matt Hummel

Posted on • Originally published at matthummel.com

Power Apps Filter vs LookUp vs Collections (Quick Guide for Beginners)

If you're learning Power Apps, these three come up fast:

  • Filter
  • LookUp
  • Collections

They’re simple on their own — but easy to mix up.

Keep This Straight

  • Filter → multiple records (table)
  • LookUp → one record
  • Collections → stored data in memory

Most issues come from ignoring that.

Where Things Go Wrong

Common mistakes:

  • Using LookUp when multiple results exist
  • Using Filter when you only need one record
  • Storing everything in a collection “just in case”

The app might still work at first… then break later.

Quick Examples

  • Filter (for lists)
  • Filter(Requests, Status = "Approved")
  • LookUp (for one record)
  • LookUp(Users, Email = User().Email)
  • Common mistake
  • Filter(Users, Email = User().Email)

Now you’ve got a table, not a record — which complicates everything later.

Filter + LookUp
LookUp(
Filter(Orders, Status = "Pending"),
OrderID = varOrderID
)
Collections
ClearCollect(colOrders, Orders)

Use when reusing data — not for everything.

Real Example That Breaks

LookUp(Approvals, Status = "Pending")

Works… until multiple records match.

Better:

Filter(Approvals, Status = "Pending")

Simple Rule

  • Need a list → Filter
  • Need one record → LookUp
  • Need to store data → Collections

Final Thought

Most issues aren’t complicated — just small misunderstandings early on.

And your app will usually still work… until it doesn’t.

🔗 Full Post

[https://bit.ly/filter-lookup]

💬 Question

What’s something confusing you’ve run into with Filter or LookUp?

Top comments (0)