Skip to content


Reports offers a range of user interactive Dashboards. Dashboards are a visualization tool that enables non-technical and power users to query, transform, and present live data to the KX Insights Platform. Visualizations can be built using drag-and-drop and point-and-click operations in an easy to use editor.

Get Started

  1. Create a new report or select a report from the entity tree or Overview page. Reports are accessible from the Document bar.



  2. Click Design to edit a report; click-and-drag components into the central workspace and assign data sources from pipeline data. Save changes and Preview to interact with the updated view.

  3. Reports can be saved to your profile.


    Saved Reports

    Saved reports persist across sessions, but any required update will reset all changes.

Report Properties

Components within a report can be replaced and new data sets assigned. The report can be styled in a light or dark theme, and the arrangement of components changed.





Dashboard Theme
Theme Switchable
Sets Light or Dark theme for dashboard and define if theme can be switched. This should be disabled (theme-locked) if the dashboard uses custom styling which would not update on global theme switch.
Widgets Spacing
Widget Shadow
Define distance in pixels between components and add optional shadow.
Background Color
Transparent Background
Define background color of components.
Border Size
Border Color
Border Rounding
Border Spacing
Define border criteria of components. Spacing is defined in pixels.
Show Loading Indicators
When checked, indicates when a report is loading data. If your report uses streaming, managed or polling data, leave this unchecked.

For more on Style






New views can be created by adding a screen to an existing report. If adding screens, remember to define which screen is the default one by selecting the star icon. New screens start with a blank workspace into which components can be added and data sources assigned.

button action
Delete screen Delete screen
Duplicate screen Duplicate screen
Set as default Set screen as default on dashboard load
Edit screen Edit screen
Screen snapshot Take snapshot image of screen: used by Navigation Component tooltip


Click-and-drag a component from the left-hand menu into the workspace. When dragging a component into a workspace, be careful not to drop it on top of another as this will replace the underlying component; any such change (or others) can be undone by clicking the undo action in the report menu bar next to the save icon.

Data Sources

Each report comes with its own set of data sources. Data sources are managed in the Data Dialog.

Set up

  1. Open the data dialog by selecting Data Source in a component's Basics Properties; for Charts, the Data Source is available under Layers - Basics.


  2. Select a data source from the list of available options in the data dialog, or create a new query:

    • SQL for a SQL text query.
    • kdb+/q for a kdb+/q text query.
    • Builder to use a visual query builder.
    • Virtual for a javascript query.
    • Streaming for a real-time data source.
    • Analytic for a pre-defined function.
  3. Click Execute to preview, success will populate the Results table or return an error message.

  4. Click Apply and Select to assign the data to the component.



Default setting. Single request for data


A client-side poll of the database; this is a direct client request to the database. Server paging can be enabled to limit the amount of data returned to the report.

option effect
Interval Time between client poll request
Key Select which data source column to define Subscription handling; e.g. to have continual or static update
Force Reset By default, for updating data sources Dashboards merges updates from the server with its existing dataset, unless a parameter is changed in which case the existing dataset is cleared. Enabling Force Reset will clear the existing dataset each time it receives an update, regardless of whether a parameter has changed or not.


Streaming subscriptions push data to the report in place of a client or server-side poll. Key defines which data source column to define subscription handling; e.g. to have continual or static update


True by default. When auto-execute is true, the data source will automatically execute whenever an input parameter is changed or on load if mapping is used.

When auto-execute is false, subsequent parameter changes won't execute the query. However, it will still execute normally if associated to a component, e.g., a data grid on load, or as an action tied to a button.

Max Rows

Default is 2,000 rows of data is returned for any subscription type



Pivot Query

Pivot Query

Update Query

Update Query


Mapping maps results from a data source to View States. Results should include a column that contains keys and a column that contains values.

Mapping configuation is accessible from the Mapping tab in the Results panel.

Key and value columns should be defined in the Key and Value dropdowns.

Mappings can be added using the + button. Within each mapping you can define the Key and the View State that the Value should be mapped to.

Keys in the current results can be added using the dropdowns. Other keys can be added by typing them into the dropdown input field and pressing enter.

The Reset button will populate the list of mappings with all available keys.

View States

View States store values accessible to all components of the report. Use them to pass values like user selections or preferences between components and into queries.

View States can be edited from the View State dialog.

Select View State dialog showing a selected View State and its properties

This dialog can be summoned by clicking inside any input box showing the eye icon Screenshot.

Hidden eyes

Some inputs offer View States, but the icon is hidden. If a View State is available, a rollover of the input will display the eye icon.


Viewstates in a Query

kdb+/q Query Editor

Viewstate parameters can be referenced from with in kdb+/q editor.

1. Function parameters

For a kdb+/q function, viewstates can be defined at the start of the function.

Add the required viewstate parameter enclosed in square brackets. Multiple viewstates can be defined by seperating parameters with semi colons.


The maximum number of parameters permitted is 8; specifying more than eight parameter will cause an error. You can circumvent this restriction by encapsulating multiple parameters in a list or dictionary.

    select from table where (column1 = x)

This causes the supplied viewstate to be substituted for all occurrences of the parameter x, the expression to be evaluated and the result returned as the output value.

2. In-query parameters

Alternative approach to add a viewstate parameter is to define an in-query parameter in a kdb+/q query, viewstates can be added to the query using the following syntax <%param%>.

    select from table where column1 = <%x%>
This causes the supplied viewstate to be substituted for all occurrences of the parameter x, the expression to be evaluated and the result returned as the output value.

SQL Query Editor

Viewstate parameters can be referenced from with in SQL editor.

1. In query parameters

In your SQL query editor a viewstate parameter can be added to the query using a set of double curly brackets e.g. {{trader}}.

    SELECT * FROM table WHERE column1 = {{x}}

This causes the supplied viewstate to be substituted for all occurrences of the parameter x, the expression to be evaluated and the result returned as the output value.

Map Viewstates in Query Editor

As new data sources are defined in the kdb+/q Query Editor, it is often convenient to map them immediately to View States.

This can be done with a single click on the eye-and-gear button.

Mapping a query’s trade argument to an eponymous View State

This will update Value to reflect the mapped View State. For example, <%Query/value%> as mapped in the image below:


To edit the View State, click on the eye button to summon the Select View State dialog.


Parameter types

Parameter types must match. A parameter’s type is defined in the Select View State dialog. Check to ensure the same type is assigned in the Query Editor for which the View State is assigned.

In Query Editor, if there is an assigned value prior to creating a View State, the created View State will adopt the assigned value as the default value; ensuring the query will run when executed.

Selected Values

Selected Values

View State Routing

View State Routing

Component linking

Component linking


Action is a common property set used to configure a view state, run a query or open an URL.


Highlight Rules

Highlight rules are a common property utilizing color and/or icon markers to notify users of value changes. Highlight rules are best used with real-time streaming, or polling data.

Highlight Rules

Additional Information

For more on Dashboards.