> 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/system-administration/system-settings/system-settings-configuration-show-system-data.md).

# System Settings Configuration - Show System Data

## Introduction

In LogicNets Version 8, it is possible to include specific system or custom data in the initial DATA popup to support more advanced troubleshooting.

## Description

When you view session context data using the DATA button, LogicNets routinely filters out system data - for example, data used by the LogicNets frameworks - so that the you only see the data associated with your modeled content variables and status.

In more complex applications you may use or build on existing system data, and it can be helpful to see the status of those variables in the initial context view. So you do not have to continually click on the *Show system data* checkbox, there is a System Configuration setting that lists any system variables to be automatically included in the initial view.

## Configuration Settings for System Data

You must make the configuration change at the company level from the System Configuration package *Designer* tab.

With these settings you can control specific system containers (like \_configuration).

1. Explicitly promote them to the main data view.
2. Hide them from view completely, even if you click *Show system data*.

The (middle) default option is standard behavior for the prior release (system data available when you check *Show system data*.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-999b33f3a87827052e4c0ffbe6fc7780d6878231%2Ff6cb8c67-9582-4840-bcc7-f63e231022e4.jpg?alt=media)

Changes to these settings impact the **company-level** **settings.cfg** file as shown below.

```
_session = {
    DESIGNER = {
        settings_dataview_filter = {
            _configuration = "show",
            _framework = "show",
            _part_defaults = "hide"
        }
    },
...
```

### Configuration Settings for Custom Data

If there is specific custom data container within your modeled application that you want to hide from the DATA view, you can add your values to the **installation settings.cfg** file in the same way. Once you have added a data object here, it will appear in the System Configuration *Designer* tab as above, and you can set the information to be hidden in the same way.

```
_session = {
    DESIGNER = {
        dataview_filter_items = {
             "yourvalue"
                                }
                 },
...
```


---

# 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/system-administration/system-settings/system-settings-configuration-show-system-data.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.