> 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:

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-6e45f6c6e0d32cf39e1b375cd3a7ba0a1ad81aca%2Fdda3d7_051833aa57db4e1994986721dc268a18~mv2.png?alt=media)

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":

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-2a1a8ef550ec5ed0b14af7a182536ba21c458a11%2Fdda3d7_7689aa47fdd94e78a63c8447a98e955b~mv2.png?alt=media)

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

* Image
* File
* Relationship

## Use on the web

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

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-bdf8b3fe123d407599df6b599125e1b44ee0555b%2Fdda3d7_cdd31226ce974ed4813c596ae79f4c92~mv2.png?alt=media)

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

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-01f2e3d27871e87787511f24658c6d8fb66b88f2%2Fdda3d7_40df64da60204e6eb2622d0f074973ef~mv2.png?alt=media)

You can click Edit, enter values then Save:

![](https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-8250f2a8806dd19c1fbde88f6afe6c264e433070%2Fdda3d7_5c6c0c888e084f5eb61139f113fc48d3~mv2.png?alt=media)

## Use on mobile

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

{% tabs %}
{% tab title="Android" icon="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="https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-ec00ff9d80af31294102ac9f8ece1df8e80ddb0b%2Fprefill-1-en-android.jpg?alt=media" alt="" width="375"> <img src="https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-465a2215cdbd403606065dfb77f2536ae74f267a%2Fprefill-2-en-android.jpg?alt=media" alt="" width="375"></div>

<div align="left"><img src="https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-9bb52acd40ba2385a9c2034886855b539b82f47f%2Fprefill-3-en-android.jpg?alt=media" alt="" width="375"></div>
{% endtab %}

{% tab title="iOS" icon="apple" %}
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="https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-ac25beac090aca598b4ac1d275a6dc680cba3ef6%2Fprefill-1-en-ios.png?alt=media" alt="" width="375"> <img src="https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-ab9186c2b82a57ce3d259d1d710d10fbe63e56fd%2Fprefill-2-en-ios.png?alt=media" alt="" width="375"></div>

<div align="left"><img src="https://2070467688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhifC5lkPdiB9lhTGThXK%2Fuploads%2Fgit-blob-60700cbde98062252c0dc6ece0800f5322ea2a92%2Fprefill-3-en-ios.png?alt=media" 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.center.daxium-air.com/user-documentation/build/building-forms/field-options/prefill.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
