> For the complete documentation index, see [llms.txt](https://www.center.daxium-air.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.center.daxium-air.com/user-documentation/build/building-forms/field-options/prefill.md).

# Pre-fill

This option allows each user to manually define, from the web or mobile, a default value for the fields that have been authorized for pre-filling by the administrator in the form.

Thus, each file created will contain the default values defined by the user who can modify if necessary.

## Configuration

In the advanced field options, a checkbox is available to make it pre-fillable:

![](/files/r4gRcno95cG6Vu1pe5eN)

For a user to access the pre-fill configuration menu on mobile, a button must be added to the [customized application](/user-documentation/build/building-apps/app-configuration.md) whose action is "Autofill":

![](/files/4eB38YAw3oBCCXuoXeFC)

**List of fields not compatible with pre-filling:**

* Picture
* File
* Relationship

## Use on the web

From the form view, you will find the "Pre-fill" top right:

![](/files/wGNwT4B2wmx1MRghKhNc)

After clicking on the "Pre-fill" button, you will find a form with only the fields checked as pre-fillable in the form:

![](/files/GRKxZH5FMv4nzdHpFvdw)

You can click Edit, enter values then Save:

![](/files/1gSiV0E65JcnvHMFApUp)

## Use on mobile

On the custom application with the "Pre-fill" action button, click on it.

{% tabs %}
{% tab title="Android" %}
If you have several forms, select the one of your choice and fill in the desired values then click on the arrow at the top left when you are finished:

<div align="left"><img src="/files/jConBIllM3422SfSXL9G" alt="" width="375"> <img src="/files/r51GyQBTPI8gsyFtlOpk" alt="" width="375"></div>

<div align="left"><img src="/files/xqzLFE5xPRlbjNhXJwRP" alt="" width="375"></div>
{% endtab %}

{% tab title="iOS" %}
If you have several forms, select the one of your choice and fill in the desired values then click on the arrow at the top left when you are finished:

<div align="left"><img src="/files/WIFgpaLO79TwwWo6RGZp" alt="" width="375"> <img src="/files/XFzbtbjxow7gBqeOzS84" alt="" width="375"></div>

<div align="left"><img src="/files/2OjhFBTQY6R9nQRuvIFV" alt="" width="375"></div>
{% endtab %}
{% endtabs %}

**Attention: if you delete the logged-in account from the mobile/tablet, the pre-filled values will be lost.**

{% hint style="info" %}
Pre-fills are linked to the form's [version](/user-documentation/components-concepts-terminology.md#version). If the form's version changes, we recommend deleting existing pre-fills, synchronizing the device, and possibly creating new ones.
{% endhint %}


---

# 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://www.center.daxium-air.com/user-documentation/build/building-forms/field-options/prefill.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.
