> 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/platform-documentation/process-node-parts/generate-data-log.md).

# Generate Data-Log

## Description

In LogicNets, *context* is session memory that contains all data objects that can be managed by the logicnet in an application. The *data log* is the meta-data structure inside the session that contains meta data about the data-objects in the context. This part allows you to retrieve data log items and place them in the context. The system removes all items that are already in the context but not in the data log. Since the data log stores more information than the value, you can use this part to generate data structures to export data objects.

Note: in the LogicNets Designer this process step will be displayed with the label *convert\_ctx\_to\_data\_log*\_.\_

**Data Log Example**

```
log = {
    ['mypath'] = {
        path = 'mypath'
        value = 1,
        data_type = 'number'
    },
    ['mypath2'] = {
        path = 'mypath2'
        value = { “a”, “b” },
        data_type = 'number'
    }
}
```

**Node Type:** This part is located in the *Misc* dropdown menu in the Process node.

**Used With:** You can use this part with all framework and non-framework projects.

## Editor Fields

Configure the part using the following editor fields:

| Field Name               | Description/Use                                                                                                                                                               | Type/Option | Optional/Mandatory |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | ------------------ |
| Output path              | This is the location in the context where the system stores the data objects.                                                                                                 | Text        | Mandatory          |
| Input path               | This is the location from which the system retrieves the data objects. If you leave this field empty the system retrieves all items in the data log.                          | Text        | Optional           |
| Set max level            | When you check this checkbox you can define the level to which the system processes tables.                                                                                   | Checkbox    | Optional           |
| Max level                | With *Set max level* checked, this field allows you to set the level to which the system processes tables.                                                                    | Number      | Optional           |
| Set exclude filter       | With this checked you can define a filter of items the system should not place in the context.                                                                                | Checkbox    | Optional           |
| Exclude filters          | With *Exclude filters* checked you use this field to define a list of objects the system should filter.                                                                       | Collection  | Optional           |
| Export specific keys     | Check this to define a list of specific keys.                                                                                                                                 | Checkbox    | Optional           |
| Datalog keys             | With *Export specific keys* checked you use this field to define a list of keys for the system to export. The system will place these keys of the data object in the context. | Collection  | Optional           |
| Export as data log items | Check this option to have the system define a list of data log paths.                                                                                                         | Checkbox    | Optional           |
| Export as data log paths | With *Export as data log items* checked you use this field to define a list of data log paths for export.                                                                     | Collection  | Optional           |
| Keep non-data log items  | Checking this item allows you to define a list of data objects the system should keep when they are not in the data log.                                                      | Checkbox    | Optional           |
| Keep items               | With *Keep non-data log items* checked you use this field to define a list of the names of data objects the system should keep even if they are not in the data log.          | Collection  | Optional           |


---

# 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/platform-documentation/process-node-parts/generate-data-log.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.