A lookup field is a field that reaches into a linked record in another table and displays a value from it, like showing a customer's email next to their order without retyping it. It matters because it keeps one fact in one place: you store the email on the customer, and every order can display it without a second, drifting copy.
What is a Lookup Field?
How a lookup field works
A lookup field depends on a link between two tables. Once an order is linked to a customer, for example, a lookup field on the order can pull in and display a chosen field from that customer, like their email or phone number. The value is read-only, because it lives on the source record, not on the one showing it. Change the email on the customer and every order looking it up reflects the new value at once. This is what makes lookups safer than copying data: there is only ever one real version.
Lookup field example
Say you build an app where support tickets are linked to customers. You add a lookup field on the ticket that displays the customer's account tier from the customer table. Now an agent viewing a ticket sees "Premium" or "Free" right there, without opening the customer record. Update the tier once on the customer, and every linked ticket shows the change.
Frequently Asked Questions
Your Questions, Answered
This will automatically populate, don't change
Don't change this element unless you know what you are doing
Start Building
on Emergent today
on Emergent today
Start Building
