Skip to main content

General

Dashboard Issues

Resolve widget display, binding, and performance problems.

Widgets Show "No Data"

Symptoms

  • Widget displays "No Data" or "N/A"
  • Chart shows empty canvas

Troubleshooting

Verify Data Binding

  1. Click on the widget to open properties
  2. Check the Data Source binding:
    • Direct Tag: Ensure device and tag are selected
    • Query: Verify the SQL query returns data
    • Expression: Check formula syntax

Confirm Data is Available

Navigate to UNS Explorer and verify the bound tag has recent values.

Check Time Range

For charts with time-based queries, ensure the selected time range contains data.


Dashboard is Slow

Symptoms

  • Widgets take long to load
  • Browser becomes unresponsive
  • High CPU usage

Performance Optimization

IssueSolution
Too many widgetsSplit into multiple dashboards; recommend max 20 widgets per dashboard
Large time rangesReduce chart time range (e.g., last 1 hour instead of last 7 days)
Complex queriesSimplify SQL queries; add appropriate indexes
High refresh rateIncrease refresh interval (e.g., 5 seconds instead of 1 second)
info
Caching

The dashboard engine caches data to reduce database load. If you need real-time updates, use the Live Stream binding mode instead of polling.


Widget Not Updating

Symptoms

  • Widget shows stale values
  • Other widgets update normally

Solutions

  1. Check Auto-Refresh: Ensure dashboard auto-refresh is enabled (top-right toggle)
  2. Verify Binding: Edit widget and re-select the data source
  3. Browser Cache: Hard refresh the page (Ctrl+Shift+R / Cmd+Shift+R)

Layout Issues

Widgets Overlapping

The dashboard uses a grid system. To fix overlapping:

  1. Enter Edit Mode
  2. Drag widgets to non-overlapping positions
  3. Use the resize handles to adjust dimensions
  4. Save the layout

Dashboard Not Saving

Ensure you have Edit permission for the dashboard. Check with your administrator if you cannot save changes.


Export/Import Problems

XML Import Fails

When importing a dashboard XML from another environment:

  1. Version Compatibility: Ensure both environments run the same Proxus version
  2. Data Source Mapping: If device IDs differ, update bindings after import
  3. XML Validity: Check for malformed XML (missing closing tags)
# Validate XML syntax
xmllint --noout dashboard.xml
warning
Environment Differences

Dashboard exports include device references by ID. After importing to a new environment, you may need to re-bind widgets to local devices.


See Also