The debug preview feature for DataV screens records interaction logs and error messages in real time, including widget operation logs and exception details.
Background information
DataV provides two preview modes for screens: Normal preview and Debug preview.
-
Normal Preview: Click Normal Preview under the
icon in the upper-right corner of the canvas or blueprint editor. In this mode, DataV does not record interaction logs or error messages. -
Debug Preview: Click Debug Preview under the
icon in the upper-right corner of the canvas or blueprint editor. In this mode, DataV records interaction logs and error messages.
The Debug Preview feature is available for PC dashboards only. Mobile dashboards do not support Debug Preview.
Prerequisites
-
You have created a DataV screen. You can create a screen from a template, create a screen from a blank canvas, or generate a screen using AI.
-
You have added widgets and configured blueprint interaction events or actions.
Enter the debug preview page
Access the DataV console.
-
On the All Applications page, hover over the target DataV screen and click Edit to open the canvas editor.
-
In the canvas editor, click the
icon in the top menu bar to open the blueprint editor. -
Right-click the connection line of the node that you want to debug and select Record Log to enable log recording.
NoteWhen log recording is enabled, the connection line turns red, which indicates that you can trace operations. If you no longer need to debug the node, right-click the connection line and select Cancel Log Recording.
-
Click Debug Preview under the
icon in the upper-right corner to open the Debug Preview page.NoteDuring debugging, you can use the minimum granularity of the log recording mechanism to trace issues from end to end. If a target widget does not produce the expected interaction, you can start troubleshooting by working backward from its trigger action and verifying the input data for each node.
Page overview
On the Debug preview page, perform an interaction to start debugging. The following table describes the page layout.
|
Number |
Description |
|
1 |
User interaction module. Click to view the configured interaction effects. |
|
2 |
Blueprint log logic module. Displays the connection logic of each node on the blueprint log page, where you can inspect the logic details. |
|
3 |
Blueprint log details module. Click Record/Stop to enable or disable the listener, or click Clear to clear the current blueprint logs. This module shows the source node, destination node, source event, and destination action for each log entry. You can also perform operations related to interaction logs. Note
To prevent log refreshes from affecting the performance of the DataV screen, disable automatic data updates or increase the automatic data update interval during debug preview. |
|
4 |
Widget log module. If a widget has issues such as data source errors, filter errors, or initialization failures, the widget logs are displayed here. |
|
5 |
Widget log details module. Click an error log on the left to view the details of the widget log error. |
Log information
When you interact with a debug preview page and trigger a connection with log recording enabled, the system automatically captures the upstream-downstream node relationship and a data snapshot at the time of the interaction. Logs are divided into two types: interaction logs and widget logs. Interaction logs record runtime parameters and context for widget actions. Widget logs track runtime exceptions and errors for widgets.
Interaction logs
-
View log details: After each new interaction, a new record is added to the top of the log list. Click the
icon to the left of a log record to view the runtime parameters of the action. -
Copy a node ID: Double-click a node in the blueprint log logic module to copy its ID.
-
Repeat the previous operation: Double-click the event-action connection line in the blueprint log logic module to execute the previous action again.
icon to the left of a log record to view the runtime parameters of the action.
Widget logs
-
When a widget request fails, a new error record is added to the top of the panel. Click a log record to view the error details.
Common error types
Error type
Description
Data retrieval failed
Occurs when a widget fails to retrieve data from a data source. This can happen during initial widget loading, automatic updates, global variable triggers, or blueprint-triggered data source requests. The error shows the Time, Widget Name, Data Source, and Error Message.
Filter execution error
Occurs when data retrieved from a data source encounters an error while passing through a filter. The error shows the Time, Widget Name, Data Source, Filter, Input Data, and Error Message.
Internal widget error
Occurs during widget rendering or widget method execution. The error shows the widget ID and the widget method.
Internal node error
Caused by a code problem within a blueprint node, such as an initialization error.
NoteA warning message is generated if the parameters used to call a widget method do not match the method's declaration.
-
Copy a widget ID: Double-click the widget name in an error record to copy its ID to the clipboard.
-
Search for a widget ID: Paste the copied widget ID into the search box of the editor to locate the corresponding widget. Then, you can modify its configuration based on the error message.
-
Filter widget error logs: Enter a widget name, widget ID, filter, or error message in the search box to filter related error logs.
