> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/example-gallery/example-projects-for-parts/add-data-records-example-project.md).

# Add Data Records Example Project

This provides an example of the *Add Data Records* part. In the example, the *Get Data Records* part in the first node returns all of the records in which the date is 'Fri' and later stores that data into a collection named *temperatures*. The Add Data Records part in the second node saves the *temperatures* collection into the data table named *temp*.

To run the example, open the project folder and click on the *add\_records* logicnet to show it on screen. Then click ***TEST*** to run it.

## Attachments

* [Add Records Example74.zip](https://github.com/logicnets/community-portal/tree/release-9/docs/.gitbook/assets/y7kqc6-Add-Records-Example74.zip)
* [Add Records from Collection Example81.zip](https://github.com/logicnets/community-portal/tree/release-9/docs/.gitbook/assets/63dfnn-Add-Records-from-Collection-Example81.zip)


---

# 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://community-test.logicnets.com/release-9/example-gallery/example-projects-for-parts/add-data-records-example-project.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.