# Creating details fields

{% hint style="info" %}
To review key information on defining details fields, see [Details fields](/complete-reference-guide/customization-options/custom-configurations/creating-custom-configurations/planning-configuration-and-data-structure/details-fields.md).
{% endhint %}

### In `fields` directory customize the `.json` files

Each `.json` file in the **fields** directory needs a `key`, `type`, `label`, and `placeholder.`

`type` can be one of `select_multiple`, `select_one`, or `text`.

For `select_one` and `select_multiple` fields, you will need to define an array of answer `options.`

#### Example fields file (`name.json`):

```
{
    "key": "name",
    "type": "text",
    "label": "Name",
    "placeholder": "Common name of this place"
}
```

#### Example fields file (`sample-type.json`):

```
{
    "key": "sample-type",
    "type": "select_one",
    "label": "Sample type",
    "placeholder": "Select the type of testing",
    "options": [
    	"Meteorological",
    	"Air",
    	"Soil",
    	"Water",
    	"Mineral",
        "Forestry/vegetation",
    	"Other"
	]
}
```


---

# 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.mapeo.app/complete-reference-guide/customization-options/custom-configurations/creating-custom-configurations/coding-configuration/creating-fields.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.