> For the complete documentation index, see [llms.txt](https://docs.jigx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jigx.com/building-apps-with-jigx/ui/jigs-_screens_/forms.md).
# Forms
{% columns %}
{% column %}
{% endcolumn %}
{% column %}
In this guide, you will learn how to create forms with Jigx. Forms are mainly used to collect and update data for various data sources.
We will use Dynamic Data to store the data. If you want to learn more about Dynamic Data and its capabilities, check out this guide: [Dynamic Data](/building-apps-with-jigx/data/data-providers/dynamic-data.md)
{% hint style="success" %}
As we will use Dynamic Data for storing the data in this guide, please read the section below about *Defining a Dynamic Data table* before proceeding to the next part.
{% endhint %}
{% endcolumn %}
{% endcolumns %}
## Defining a Dynamic Data table
Before we can start creating records in Dynamic Data, our table has to be defined in the solution:
1. In your solution, go to the *default.jigx* file in the *databases* folder and add the following YAML:
{% code title="databases/default.jigx" %}
```yaml
tables:
form: null
```
{% endcode %}
The next time when you will publish your solution to Jigx, it will create a table in Dynamic Data for your solution. You can always log in to the [Jigx Management](https://manage.jigx.com/) and navigate to the *Data* area of your solution to check the tables and contents. We will use this table in this guide for storing the form data.
Now you can proceed to the next part, [Creating a Record](/building-apps-with-jigx/ui/jigs-_screens_/forms/creating-a-record.md) to get familiar with forms.
---
# 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://docs.jigx.com/building-apps-with-jigx/ui/jigs-_screens_/forms.md?ask=&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.
