> 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/data-and-data-tables/logicnet-data-viewer.md).

# Logicnet Data Viewer

As you build and test your application you can view the data contained in your session. This logicnet Data Viewer allows you to see the data that has built up as you test your logicnet or application, and this can help you verify and troubleshoot.

As of v7.4, LogicNets has enhanced this Data Viewer with a filter for system data objects, which are those data objects generated by the platform application frameworks. By default, the system filters out system data objects so you can focus on the data objects generated by your application. You can also click the checkbox next to the *Show system data* option to see the system data as well.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-2bc0b8e1141f4b82b833b1ba4b0db67576ecd7eb%2F28c93d96-c9f6-4253-8406-b2fe1d58f1c9.png?alt=media)

Additionally, LogicNets improved the layout of the Data Viewer to include type icons for the data objects.

| Icon | Meaning                            |
| ---- | ---------------------------------- |
| T    | This is a text object.             |
| \</> | This is HTML text.                 |
| {}   | This is a container data object.   |
| \[]  | This is a collection.              |
| 123  | Data with this symbol is a number. |
| B    | This is a Boolean object.          |

## Using the Filter

The filter lists the "active" variables from your model in alphabetical, non-case-sensitive order; for example, 'A' comes after 'a' and before 'b'. If the user has not input a value into a form node or the variable in a process step has not been calculated yet the system will not display it in the list.

* Enter any text string to retrieve the data objects that contain the specified text. For example, if you enter the text string "day" the system displays the full path of any variables containing "day" you specified in the model, including such items as birthday, day\_of\_week, time\_of\_day, daydreamer, student.days\_late, or current\_year.current\_week.friday\_date.
* The filter is case sensitive, so if you entered "Day" the system would not return the data object names listed above, but it would return First\_Day\_Of\_Month.
* The format icons (T, 123, \[]) and the record numbers in collections (#1, #2…) are not searchable.

To reset the filter, clear the contents of the filter and click the *Return* button.

## Searching for Inputs

Sometimes, you can't remember the name of the variable but you DO know you answered the question with the word "red". You can find the variable by using the browser text filter (Ctrl + F). Type the case-insensitive text in the input box and the browser displays how many occurrences are present on screen. Use the Up/Down arrows to find the next/previous matching entry.

Note: The browser search results count includes any occurrences in the Data Viewer as well as text that is found on the application UI, which is greyed out behind the popup.

* You can search for any text using the browser search function, including T, 123, and other format icons as well as specific records in a collection (#1).
* To find a variable whose path begins with "product" (and exclude all variables like product\_name, product\_cost) search for "\[product". Including '\[' limits the search to containers only.


---

# 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/data-and-data-tables/logicnet-data-viewer.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.