# New Field Type: Lookup Field

**URL:** <https://community.noloco.io/t/new-field-type-lookup-field/197>\
**Category:** Feature Requests\
**Tags:** feature-request\
**Created:** [January 17, 2024, 6:16am UTC](https://community.noloco.io/t/new-field-type-lookup-field/197 "2024-01-17T06:16:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![akraut](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/akraut/32/63_2.png) [@akraut](https://community.noloco.io/u/akraut)\
**Post date:** [January 17, 2024, 6:16am UTC](https://community.noloco.io/t/new-field-type-lookup-field/197/1 "2024-01-17T06:16:14Z")

</div>

A lookup field would be very helpful.

Ex) When a user is filling out a Form or editing a record, I would like the ‘Entity Name’ field to be a type-to-search field that searches and displays a list of all existing entity name records associated with the Guarantor Name(s) previously entered in the loan application form / record. Selecting a list option would then autofill the existing field values associated with the Entity Name record.

The lookup field would be fetching records from a Noloco table ot Xano table.

Ideally, the same logic can be applied to street addresses (re: lookup existing property addresses previously associated with the Guarantor Name(s) previously entered in the loan application form / record).

Ex) I’m filling out a loan application and enter / select Primary Guarantor name. I then go to enter the property address that the borrower wold like to purchase / refinance. Ideally, beginning to type the address would display a dropdown of existing property addresses for which a record associated with one of the Guarantors already exists.

---

<div class="post-metadata">

**Author:** ![Tobias](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/tobias/32/252_2.png) [@Tobias](https://community.noloco.io/u/Tobias)\
**Post date:** [April 1, 2024, 7:03am UTC](https://community.noloco.io/t/new-field-type-lookup-field/197/2 "2024-04-01T07:03:58Z")

</div>

@darragh I vaguely remember hearing that this was on your road map… Any guess as to how far away this might be?

---

<div class="post-metadata">

**Author:** ![buildwithjoel](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/buildwithjoel/32/1537_2.png) [@buildwithjoel](https://community.noloco.io/u/buildwithjoel)\
**Post date:** [April 1, 2024, 11:11pm UTC](https://community.noloco.io/t/new-field-type-lookup-field/197/3 "2024-04-01T23:11:14Z")

</div>

Very glad I just found this post. 100% agree, this would be really really helpful.

---

<div class="post-metadata">

**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\
**Post date:** [June 6, 2024, 3:50pm UTC](https://community.noloco.io/t/new-field-type-lookup-field/197/4 "2024-06-06T15:50:09Z")

</div>

Hey @akraut - thanks for the suggestion, we actually recently released lookup fields

> [@Lookup fields, E-Signature Inputs, and Container Sections](https://community.noloco.io/t/lookup-fields-e-signature-inputs-and-container-sections/754):
>
> Hey there, this is Sam from Noloco with some new updates to make your apps better than ever. This update is jam-packed with new field types and ways to capture data in your Noloco app. Let’s dive in! Introducing Lookup Fields We’re adding a highly-requested feature to your Noloco tables: Lookup Fields. This new field type allows you to pull and display related data from different tables seamlessly, fostering dynamic and interconnected datasets.