Widgets Show "No Data"
Symptoms
- Widget displays "No Data" or "N/A"
- Chart shows empty canvas
Troubleshooting
Verify Data Binding
- Click on the widget to open properties
- 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
| Issue | Solution |
|---|---|
| Too many widgets | Split into multiple dashboards; recommend max 20 widgets per dashboard |
| Large time ranges | Reduce chart time range (e.g., last 1 hour instead of last 7 days) |
| Complex queries | Simplify SQL queries; add appropriate indexes |
| High refresh rate | Increase refresh interval (e.g., 5 seconds instead of 1 second) |
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
- Check Auto-Refresh: Ensure dashboard auto-refresh is enabled (top-right toggle)
- Verify Binding: Edit widget and re-select the data source
- 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:
- Enter Edit Mode
- Drag widgets to non-overlapping positions
- Use the resize handles to adjust dimensions
- 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:
- Version Compatibility: Ensure both environments run the same Proxus version
- Data Source Mapping: If device IDs differ, update bindings after import
- XML Validity: Check for malformed XML (missing closing tags)
# Validate XML syntax
xmllint --noout dashboard.xmlDashboard exports include device references by ID. After importing to a new environment, you may need to re-bind widgets to local devices.
See Also
- Creating Dashboards - Dashboard designer guide
- Data Query Studio - SQL queries for widgets
- UNS Explorer Navigation - Browse live data
- Data Flow Problems - If data is not available for widgets