> For the complete documentation index, see [llms.txt](https://docs.nedyx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nedyx.com/nedyx/clearlines-functions/widget-functions/storewidgetcontent.md).

# STOREWIDGETCONTENT

#### Syntax

**STOREWIDGETCONTENT**(*widget*)

* *widget* - the widget for which the current content should be saved in the nedyx database - ***Value type**: widget*

#### Remarks

* This function enables using the nedyx database to store data of an app, instead of using an external database.
* If widget has a Content formula assigned, the function does nothing\
  **Note**: The content of widgets with a Content formula is never stored in the nedyx database, because it is always calculated by the Content formula.
* It is recommended to call the UPDATE function of the widget before calling STOREWIDGETCONTENT, to get the latest stored content of the widget and ensure that changes, which have been stored by other users in the meantime, don't get lost.

#### Examples

**Example 1**

<figure><img src="/files/KeXb7i0EPBJEaTZmCx77" alt=""><figcaption></figcaption></figure>

**Example 2**

Please note that this example is more complicated than usual examples, and requires some enhanced experience with nedyx app creation.

The "lockState" cell is used here to further ensure, that all desired changes can be merged into the latest stored content of a widget, with a reduced risk that another user does the same in parallel.

<figure><img src="/files/YCIaKZdnsWieUlfU1cUN" alt=""><figcaption></figcaption></figure>


---

# 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.nedyx.com/nedyx/clearlines-functions/widget-functions/storewidgetcontent.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.