[]
        
(Showing Draft Content)

Configuring Table Data Source

Data Source Mode

The Table tab allows you to configure how a table retrieves and synchronizes its data.

A table can operate in either:

  • Remote mode – Data is loaded from HTTP endpoints.

  • Local mode – Data is embedded directly in the table configuration.

Only one mode is active at a time.

Remote Mode

Remote mode connects the table to one or more HTTP endpoints.

Configuring the Read Endpoint

The Read section defines how the table loads data.

You can configure:

  • HTTP Method (GET)

  • URL

  • Request Headers

  • Format

  • Data Path

  • Auto Sync

image

Request Headers

Request headers allow you to customize the HTTP request sent to the server.

The Headers section is collapsed by default. To configure request headers, click the Settings icon Local Data Setup.svg next to the URL field to expand the headers panel. Click the icon again to collapse it.

To configure headers:

  1. Use the Add (+) button to insert a new header row.

  2. Select or enter a header name in the Name field.

  3. Enter the header value in the Value field.

  4. Use the delete icon image to remove a header.

Common header names (such as Authorization or X-API-Key) are available in the dropdown list, but you can enter any custom header name as needed.

headers.gif

Only rows that contain both a name and a value are applied to the request. Empty or incomplete rows are ignored.

Auto Sync

When Auto Sync is enabled, the table automatically synchronizes data changes with the configured remote endpoints.

For details about synchronization behavior, refer to the Data Manager section in Features.

Local Mode

Local mode allows you to embed data directly into the table configuration instead of loading it from a remote endpoint.

To configure local data:

  1. Click the Local Data Setup button Local Data Setup.svg next to the URL field.

  2. In the Local Data Setup dialog:

    1. Select a Format (JSON, CSV, XML, or Column JSON).

    2. Upload a file, or paste data directly into the editor.

    3. Optionally use the Format Local Data button format local data.svg to improve readability.

  3. Click OK to apply the data.

LocalData.gif

When Local mode is enabled:

  • Remote endpoint settings are disabled.

  • Row Operations and Column Operations are unavailable.

  • The table stores the data within its configuration.

To switch back to Remote mode, click Reset local to remote mode in the dialog. This clears the embedded data and restores remote configuration.

reset.gif

Schema Configuration (Mode‑Independent)

Data Format

The Format option defines how the response data is interpreted.

The following formats are supported:

  • JSON

  • CSV

  • XML

  • Column JSON

Select the format that matches the structure of the server response.

Remote Mode

image

Local Mode

image

Data Path

The Data Path option specifies where the main data collection is located within the parsed response.

  • If a Data Path is provided, the Data Manager retrieves the data collection from the specified property of the parsed result.

  • If no Data Path is specified, the entire parsed response object is used as the data source.

Use this option when the server response wraps the data array inside another object.

datapath.gif

Window

The Window section allows you to define window-based configurations used by the table.

You can:

  • Add a window definition

  • Specify a name

  • Define a formula

Window definitions are applied as part of the table’s data behavior.

window.gif

For conceptual details about window definitions, refer to the Data Manager documentation in Features.

CustomerRecent3

=WINDOWDEF(PARTITIONBY([Product]), ORDERBY([Amount]), FRAMERANGE([@-200], [@+200]))

=WINDOWDEF(PARTITIONBY([customId]), ORDERBY([orderDate]), FRAMEROE([@-2], [@]))

Remote Submission Configuration (Remote‑Only)

When the table operates in Remote mode, you can configure endpoints for submitting data changes to the server.

Each operation is configured in a dedicated section with the same structure:

  • HTTP method

  • URL

  • Optional Request Headers

The headers panel behaves the same way as in the Read configuration.

Row Operations

The Row Operations section defines how row-level changes are sent to the server.

You can configure separate endpoints for:

  • Update

  • Create

  • Delete

  • Batch

Each operation is configured independently.

These endpoints are triggered when row data changes are submitted.

image

Column Operations

The Column Operations section defines how column-level changes are synchronized with the server.

You can configure endpoints for:

  • Get Columns

  • Update Column

  • Create Column

  • Delete Column

Each operation follows the same configuration pattern as Row Operations.

This section is available only in Remote mode.

image