# Searchable Properties

Searchable properties allow you to define any `String` based properties in a model. It can be searched via Umbraco UI Builder's list view and entity picker search controls.

Both direct `String` properties and `String` properties within nested objects can be made searchable, provided the parent object is not `null`.

![Search](/files/R4wWRzbdcuZPwwKc7XSy)

## Defining Searchable Properties

### Using `AddSearchableProperty()` Method

Use `AddSearchableProperty` to specify which properties should be included in search functionality.

#### Method Syntax

```cs
AddSearchableProperty(Lambda searchablePropertyExpression) : CollectionConfigBuilder<TEntityType>
```

#### Example

```cs
collectionConfig.AddSearchableProperty(p => p.FirstName);
collectionConfig.AddSearchableProperty(p => p.Address.Street);
```

## Search Expression Pattern

The search behavior differs based on the version:

* Up to version 15.0.1: Search uses the `StartsWith` method, meaning results include entries that begin with the search term.
* Version 15.0.1 and later: Search can be configured to use `Contains`, allowing results that include the search term anywhere within the property value.

### Example

```csharp
collectionConfig.AddSearchableProperty(p => p.FirstName); // will search for keywords that start with.
collectionConfig.AddSearchableProperty(p => p.FirstName, SearchExpressionPattern.Contains); // will search for keywords that are contained.
```


---

# Agent Instructions: 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:

```
GET https://docs.umbraco.com/umbraco-ui-builder/searching/searchable-properties.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.