Working With Records

Working with Records

Overview

This guide explains how to work with data rows in OpenEdge HCK after you have selected a database and opened one of the available monitoring or statistics screens.

Where Interface Overview explains what each part of the screen is for, this guide focuses on what you can do with the table data shown in the selected screen.

Read the full Interface Overview documentation

The available actions are intended to stay consistent between the VS Code extension and the native application unless noted otherwise.

Before You Start

Before you begin, make sure:

• HCK is open
• the correct context is selected
• the correct database is selected
• the screen you want to work with is open

Unlike DataDigger, HCK does not provide general record maintenance for table rows. The data shown in these screens is intended for monitoring, inspection, filtering, sorting, and navigation.

The Records Area

After you open a monitoring or statistics screen, the main table area becomes the place where you work with the returned rows.

Here you can:

• review the returned rows for the selected screen
• sort data by column
• filter data by column on screens that support column filtering
• move through large result sets with paging controls
• show and hide columns
• use screen-specific navigation actions where available
• compare values during incremental refresh on supported screens

Loading and Refreshing Data

HCK loads data for the currently selected screen and database from its backend endpoints.

Depending on the screen, HCK can:

• load the current data set for the selected database
• reload the data after you switch screens or databases
• show an incremental refresh state on supported screens
• show a message when no changes were detected during an incremental refresh

This is useful when you want to monitor how activity or statistics change over time rather than maintain application records.

Viewing Table Data

HCK presents returned data in configurable tables. These tables are designed for inspection and comparison.

From the table, you can:

• review the current rows returned by the active screen
• sort rows by clicking a column header
• move between pages using the paging controls
• change the number of rows shown per page
• review incremental values on supported screens

For example:

• User I/O Data includes a row action that can open the related User Table/Index Statistics view for that user
• User Table Statistics can be linked to the Index Statistics table so that selecting a table filters the related index rows

Filtering and Sorting Data

HCK supports column sorting across its configurable tables, and some screens also support column filters.

Depending on the screen, you can:

• click a column header to sort ascending or descending
• open a column filter for supported columns
• clear a column filter by removing its value
• review how many rows remain after filtering

At the moment, column filtering is not enabled on every HCK screen. For example, the User I/O Data table supports column filters, while other screens may provide sorting without per-column filters.

Configuring Visible Columns

HCK allows you to configure which columns are visible in each table.

When you open the column configuration:

• you can enable or disable individual columns for that screen
• you can save the updated column layout
• you can reset the column layout to the defaults for that screen

This is useful when a screen contains many fields and you only want to focus on the values that matter for your current investigation.

Working with Incremental Data

Some HCK screens support incremental refresh. In that mode, HCK compares the latest values with the previously loaded values and shows the differences for supported numeric fields.

This is especially useful for screens such as:

• User I/O Data
• User Table Statistics
• User Index Statistics

When incremental mode is active:

• HCK marks the screen as incremental
• changed numeric values are shown as deltas
• identity and metadata fields continue to show their normal values
• HCK can show a message when no data changes were detected since the last reload

This helps you focus on what changed between refreshes instead of re-reading the entire result set.

Screen-Specific Row Actions

Some HCK screens provide limited row-based actions that help you navigate related monitoring data.

Examples include:

• opening User Table/Index Statistics from a row in User I/O Data
• linking a selected table to the related index information in User Table/Index Statistics

These actions are navigation and analysis helpers. They are not record-editing actions.

Troubleshooting Tips

No rows are shown

• Confirm that the correct database is selected.
• Confirm that the screen you opened returns data for the current database.
• Refresh the screen if needed.

The data is difficult to read

• Hide columns you do not need.
• Sort the data by the column that is most relevant.

Incremental mode does not show changes

• Refresh the screen again after activity has changed.
• If HCK reports that no data changes were detected, the source values may not have changed since the previous reload.