> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/tips-and-tricks/database-tips.md).

# Database tips

On this page you can find tips for working with the Any2Info databases

## Form content

All the data from filled forms is stored in the Any2Info database. The data is stored in the FRMMessage\_\<FormDefinitionId> tables. These tables are dynamically generated when a FormDefinition is saved in the platform. When a field is added to a FormDefinition, the backend service adds a column to the corresponding table. When a field is deleted, the column is not removed from the table to prevent accidental data loss. The FormMessage table contains column which use the internal fieldId as name, to make live a bit easier we also generate a view for each FormMessage table using the naming convertion vw\_FRMMessage\_\<FormDefinitionId>. In these views the column use the names of the fields.

## Usefull database functions

### **GetValueBetweenQuotes**

This function can be used to extract selected list, tree and state values from the columns

example usage&#x20;

```
SELECT sysId, dbo.GetValueBetweenQuotes(lsList1) AS ListId FROM vw_FRMMessage_1
```


---

# 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://academy.any2info.com/any2info-academy/tips-and-tricks/database-tips.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.