> For the complete documentation index, see [llms.txt](https://docs.servoy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.servoy.com/guides/develop/application-design/data-modeling.md). # Data Modeling Data modeling in Servoy involves the logical structuring of data through the creation of tables, views, relationships, and procedures. It defines how data is organized and connected within both traditional databases and in-memory sources. Servoy supports a variety of datasources, including database connections, in-memory tables, and view foundsets, allowing for flexible access and manipulation of data based on the underlying data models. Relations allow developers to associate tables through key data providers, enabling dynamic access and filtering of related data at runtime, while value lists provide predefined or dynamically generated lists of values that can be bound to UI components, simplifying data entry and interaction. --- # 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.servoy.com/guides/develop/application-design/data-modeling.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.