---
title: "Access Submission Data Using the DevTools Console"
slug: "access-submission-data-using-the-devtools-console"
updated: 2025-09-25T19:21:18Z
published: 2025-09-25T19:21:18Z
canonical: "docs.unqork.io/access-submission-data-using-the-devtools-console"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unqork.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Access Submission Data Using the DevTools Console

Troubleshooting and testing are essential parts of the application creation process. Using the right tools, such as the **DevTools Console**, you can ensure your application works as expected. The DevTools Console is part of a suite of developer tools provided by Google Chrome. In the DevTools Console, you can enter commands, like the , to [troubleshoot](/v1/docs/troubleshooting) and test your application [submission data](/v1/docs/submission-data).

## Understanding Submission Data

When you preview a module in Express View, you can view any data stored in a [component](/v1/docs/module-builder-component-library) through automated or end-user input. You can view this component data through a JSON object called a submission.

Many of Unqork's input-type components include the **Store Data in Database** setting.

- When this toggle is set to ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/Screenshot 2025-09-11 131645.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A44Z&se=2026-11-07T18%3A57%3A44Z&sr=c&sp=r&sig=eoQ7fISEOx1FerarxnnLTLDFgqDZU0AI%2FpJYlZ%2BuxJw%3D)**(ON)**, data in that component is stored in your submission.
- When set to ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/image(39).png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A44Z&se=2026-11-07T18%3A57%3A44Z&sr=c&sp=r&sig=eoQ7fISEOx1FerarxnnLTLDFgqDZU0AI%2FpJYlZ%2BuxJw%3D)**(OFF)**, data won't persist when a create or update action is taken.

Most components have this toggle enabled by default. But some components, like the [Hidden](/v1/docs/hidden-component) component, disable it by default. As you configure your application, confirm this setting aligns with what data you want to store.

One of the most effective ways to test and troubleshoot your configuration is to view the submission object data in the browser console or DevTools Console. By viewing the submission object data, you can confirm your application logic performs as it's intended. You can also tell from the submission object data if the correct data persists after saving or submitting the module.

## Accessing Submission Data on the DevTools Console

### Opening the DevTools Console

To open the **DevTools Console** tab:

1. **Preview** your module in Express View.
2. Right-click anywhere on your Express View page.
3. Click **Inspect**. By default, the DevTools panel opens on the right side of your page.

> [!TIP]
> To open the Console in Google Chrome, you can use the **Ctrl + Shift + J** (Windows/Linux) or **Option + Command + J** (Mac OS) shortcut.
4. At the top of the DevTools panel, click the **Console** tab.

The Console tab lets you view your Unqork application's submission data. A blue arrow to the left of a blank row at the bottom of the Console's feed indicates the Console's command line. You'll use this field to enter commands to get more data details.

### Using the Angular Command

The most common command used in the DevTools Console is the . The Angular command, or data command, logs the submission data in the browser. You can reference this log to see how your application performs.

To run the in the DevTools Console tab:

1. At the prompt, enter the following Unqork Angular command:

```javascript
angular.element('.unqorkio-form').scope().submission
```
2. Press **Enter** **(Return)**. The submission object displays in the Console.
3. Click the solid drop-down arrow to the left of the response in your Console panel. The response starts with ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/grey_dropdown_arrow_closed.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A44Z&se=2026-11-07T18%3A57%3A44Z&sr=c&sp=r&sig=eoQ7fISEOx1FerarxnnLTLDFgqDZU0AI%2FpJYlZ%2BuxJw%3D) **{data: {...}**.
4. Expand the ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/grey_dropdown_arrow_closed.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A44Z&se=2026-11-07T18%3A57%3A44Z&sr=c&sp=r&sig=eoQ7fISEOx1FerarxnnLTLDFgqDZU0AI%2FpJYlZ%2BuxJw%3D) **data** section to display your submission data object.

> [!TIP]
> Next time you open the DevTools Console, you can press the up arrow key on your keyboard to repopulate the most recent command.

> [!NOTE]
> The Unqork Angular command only displays the submission data stored in a component through automated or end-user input before the command runs.

### Accessing Submission Data

The Console panel populates with data for the current submission. For example, if you enter information without submitting it, the data is temporarily stored in the Console. Use this data for troubleshooting and mapping—specifically when viewing hidden fields.

You can see an example of submission data inspected in the Console here: [http://trainingx.unqork.io/#/display/5eb01aa6811bf80215fd706b](http://trainingx.unqork.io/#/display/5eb01aa6811bf80215fd706b).

To see the submission data, follow the steps in [Opening the DevTools Console](/v1/docs/access-submission-data-using-the-devtools-console#accessing-submission-data-on-the-devtools-console), then run the .

In the Console, you can see that each row of the submission data comprises of a key/value pair. Keys display in purple, and values display in red. Some of the keys correspond to the module's component Property ID. Their values correspond to the value entered in Express View and saved to the submission data.

For example, if you enter the value Lavera in the **firstName** field, you can see it reflected in the Console.

To see the value in the DevTools Console:

1. Navigate to the [dashboard use case](http://trainingx.unqork.io/#/display/5eb01aa6811bf80215fd706b).
2. Open the [DevTools Console](/v1/docs/access-submission-data-using-the-devtools-console#accessing-submission-data-on-the-devtools-console).
3. In the **firstName** **T****ext Field**, enter `Lavera` (or any other value).
4. In the DevTools Console, enter the Angular command and press the **Enter (Return)** key.
5. Expand the submission data drop-down section.
6. Expand the ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/grey_dropdown_arrow_closed.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A44Z&se=2026-11-07T18%3A57%3A44Z&sr=c&sp=r&sig=eoQ7fISEOx1FerarxnnLTLDFgqDZU0AI%2FpJYlZ%2BuxJw%3D) **data:** drop-down section.
7. Under the ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/grey_dropdown_arrow_closed.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A44Z&se=2026-11-07T18%3A57%3A44Z&sr=c&sp=r&sig=eoQ7fISEOx1FerarxnnLTLDFgqDZU0AI%2FpJYlZ%2BuxJw%3D) **currentUser** drop-down section, locate the **firstName** key.

The **firstName** Property ID is associated with the Text Field component labeled First Name. Because you entered the value Lavera (or your alternative value) in the **First Name** field in Express View, you'll see that name appear as the value.

> [!NOTE]
> Some key/value pairs display in the submission data that the end-user didn't submit in Express View. These include logs of button-click events or values housed in Hidden components.

## Navigating Submission Data on the DevTools Console

Once you run the **Angular command** in the DevTools Console, you can access the module's submission data. After expanding the submission data, you can access the following expandable sections:

| Section | Description |
| --- | --- |
| ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/grey_dropdown_arrow_closed.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A44Z&se=2026-11-07T18%3A57%3A44Z&sr=c&sp=r&sig=eoQ7fISEOx1FerarxnnLTLDFgqDZU0AI%2FpJYlZ%2BuxJw%3D) data | Contains the module's submission data. |
| ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/grey_dropdown_arrow_closed.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A44Z&se=2026-11-07T18%3A57%3A44Z&sr=c&sp=r&sig=eoQ7fISEOx1FerarxnnLTLDFgqDZU0AI%2FpJYlZ%2BuxJw%3D) currentUser | The current user information. This includes the current user ID, name, and roles. |
| ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/grey_dropdown_arrow_closed.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A44Z&se=2026-11-07T18%3A57%3A44Z&sr=c&sp=r&sig=eoQ7fISEOx1FerarxnnLTLDFgqDZU0AI%2FpJYlZ%2BuxJw%3D) Submission Data | Located below the currentUser are the submission data fields, which take the form of key/value pairs. The Property ID/Name of the field acts as the key, while the submitted data is the value. |
| ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/grey_dropdown_arrow_closed.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A44Z&se=2026-11-07T18%3A57%3A44Z&sr=c&sp=r&sig=eoQ7fISEOx1FerarxnnLTLDFgqDZU0AI%2FpJYlZ%2BuxJw%3D) vars | By selecting the ellipsis (...), you can expand this section to view any global variables used in your environment. For more information, see our [Global Variables Administration](/v1/docs/global-variables-administration) article. |
| ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/grey_dropdown_arrow_closed.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A44Z&se=2026-11-07T18%3A57%3A44Z&sr=c&sp=r&sig=eoQ7fISEOx1FerarxnnLTLDFgqDZU0AI%2FpJYlZ%2BuxJw%3D) integratorErrors | Plug-In component errors. |
| ![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/grey_dropdown_arrow_closed.png?sv=2026-02-06&spr=https&st=2026-11-07T17%3A57%3A44Z&se=2026-11-07T18%3A57%3A44Z&sr=c&sp=r&sig=eoQ7fISEOx1FerarxnnLTLDFgqDZU0AI%2FpJYlZ%2BuxJw%3D) validationErrors | Validation errors that occurred in the module's components. > [!NOTE] > validationErrors only display errors server-side. Client-side validation errors don't display. |

End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product.

JSON (JavaScript Object Notation) is an open standard file and data interchange format. Unqork uses JSON for submission (record) data.

Express View is how your end-user views your application. Express View also lets you preview your applications to test your configuration and view the styling. This is also the view your end-users will see when interacting with your application. After configuring a module, click Preview in the Module Builder to interact with the module in Express View.

Also known as Record Data. Submission data consists of information saved by Unqork components. View submission data by using the angular command, or in Record Collections.

The DevTools Console helps you securely store, build, test, and deploy your software.

A Property ID is the unique field ID used by Unqork to track and link components in your module.