> For the complete documentation index, see [llms.txt](https://dyns.ntd.asia/power-dynamics/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dyns.ntd.asia/power-dynamics/power-platform/model-driven-app/auto-search-on-the-lookup-field.md).

# Auto search on the Lookup field

Hi all, \
How are you? :heart\_eyes:

This week, my client asked me about the data searching on a **Lookup field.** \
The system's current behavior is so confusing when they press on the area lookup fields which show almost recent records first, then they click on the icon <img src="/files/FmrtoVnLJ5HOTGb687Uk" alt="" data-size="line"> and can get an available record list.

<figure><img src="/files/XSWI2XhUFBrG2XpYlnKY" alt=""><figcaption><p>Example: Contact field whit recent records</p></figcaption></figure>

## Turn off recent record

So, I already disabled showing recent records on this lookup field as below.

<figure><img src="/files/Zj54BtbonH6qGRLIt6ew" alt=""><figcaption><p>Disable recent record on "Contact" lookup field</p></figcaption></figure>

And return to my app and check...&#x20;

<figure><img src="/files/JoaX0lsk1h7LZspPasW0" alt=""><figcaption><p>Recent record have been disabled</p></figcaption></figure>

The recent records have been disabled. However, my client is still facing another confusing behavior with nothing to be shown when pressing on on lookup field (as about the image).\
Even, though they did type a character into this field but nothing to be shown either.

<figure><img src="/files/hjjTPRhvdaOsAhXnTW2v" alt=""><figcaption><p>Nothing with a charater</p></figcaption></figure>

Very very confused... :disappointed\_relieved:

## Configure Lookup field behavior

... And I found one configuration in the **Power Platform Admin Center: &#x20;*****Environment > Setting > Behavior.***

<figure><img src="/files/ab7esdUI9ATWRXdYXySL" alt=""><figcaption><p>Lookup Behavior Configuration</p></figcaption></figure>

You should input 2 values and I did input minimum value also:

* *Minimum number of characters to trigger typeahead search: **1***
* *Delay between character inputs that will trigger a search: **250***

## Checking after configuring

On my Lead form, at the **Contact** lookup field, I type the **"T"** character and check...

<figure><img src="/files/M2aMXzN4XF9O4sxy5yIS" alt=""><figcaption><p>Typing "T" character and auto searching</p></figcaption></figure>

<figure><img src="/files/mK5WoewJzv02saCLKWWL" alt=""><figcaption><p>Typing "H" character and auto searching</p></figcaption></figure>

Happy and happy... :tada::clap:

**\[NTD]yns.asia**\ <mark style="color:red;">...</mark>[<mark style="color:red;">invite me a cup.</mark>](https://ko-fi.com/ntdyns/?ref=qr\&amp;v=2) :coffee: Thank you. :heart:


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dyns.ntd.asia/power-dynamics/power-platform/model-driven-app/auto-search-on-the-lookup-field.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.