> For the complete documentation index, see [llms.txt](https://docs.eximee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eximee.com/documentation/documentation-en/budowanie-aplikacji/model-danych/przechowywanie-danych-w-modelu.md).

# Storing data in the model

## Model initialization

The data model for the application is created when the application instance starts (see [Running Applications](/documentation/documentation-en/budowanie-aplikacji/aplikacja-biznesowa/uruchamianie-aplikacji.md)) . Once the model is created, it can provide values for fields, according to the definition of data sources. And accept values for locally stored fields.

## Data storage location

Data stored in the model can be divided into two types — based on where they are stored and who manages them.

### Data retrieved from services

If the application uses data stored and managed by organizational or external systems, it is retrieved via services. The low-code application does not own this data, cannot modify it, and does not control changes to its values.

Values are retrieved from the service and are always up to date, subject to cache (see [Editing the data model](/documentation/documentation-en/budowanie-aplikacji/model-danych/edycja-modelu-danych.md#zrodlo-danych)).

Examples

* current customer address
  * the customer submits an insurance purchase application
  * after submitting the application, but before generating the sales contract, the customer changes the address data stored in the bank (usually through a dedicated process)
  * the insurance sales contract has the updated address - it will be retrieved in the process according to the data definition in the model
* account balance
  * when accepting the instruction, the application verifies whether sufficient funds are available on the account indicated by the customer to cover the servicing costs
  * before actually debiting the funds, the application may verify the funds again to correctly handle the account debit

### Data stored in the model

When data is created and managed by the application, it is stored in the data model. The low-code application owns it, can modify it, and controls changes to its values.

Examples

* requested credit card limit
  * when applying for a credit card, the customer provides the desired limit amount
  * the application can change this value during process handling (e.g. reduce it)
  * the generated contract (and presumably in communication to the customer) contains the current limit value
* customer correspondence address for process handling
  * when applying for a loan, the customer provides a correspondence address
  * by default, the application displays the address stored in the bank's systems (retrieved from a service)
  * however, the customer can change this address and request that correspondence regarding this process be sent to a different address
  * the application preserves the values entered by the customer

## Data outside the model

A low-code application does not have to store all data in the model. Some data is temporary in nature and serves only to determine the target value or make a decision, e.g.:

* customer account list
  * generates the account selection domain from the Value Selection from List component
  * allows the customer to easily select a specific account
  * in the data model we want to keep only the account selected by the customer; we do not need the entire list
* customer age
  * allows a decision to be made about whether the product can be purchased (e.g. *Card <26*)
  * is calculated from the PESEL number

Temporary, operational data can be stored in session variables on forms, process variables, or script variables.


---

# 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.eximee.com/documentation/documentation-en/budowanie-aplikacji/model-danych/przechowywanie-danych-w-modelu.md?ask=<question>&goal=<endgoal>
```

`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.