> For the complete documentation index, see [llms.txt](https://docs.flexikanban.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flexikanban.ai/components/forms/tricks-hints-and-best-practices/how-to-pre-populate-form-fields.md).
# How to pre-populate form fields
### Pre-populating Source object fields
To pre-populate Source object fields you should pass the fields values to the form parameters using fields API names.
On the example below you can see how could be configured the Parameters in case if you adding a form to the Lightning page. The form is configured on standard Event object.
Another example demonstrate how you can configure the form input Parameters in case if you are using the form [Navigate](/components/forms/tools/form-action.md#navigate-action-type) action.
### Pre-populating Virtual fields
To pre-populate form Virtual fields you should use "Default Value" field option.
The format of the pre-populating value could be different based on the Virtual field type. Please look at the article, linked with the your Virtual field type.
---
# 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://docs.flexikanban.ai/components/forms/tricks-hints-and-best-practices/how-to-pre-populate-form-fields.md?ask=&goal=
```
`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.