Troubleshooting errors on the dashboards
This topic helps you troubleshoot some errors that might appear on the dashboards.
Issue symptoms | Issue scope | Resolution |
|---|---|---|
The following error is displayed: Failed to fetch | This issue occurs because of the browser session time out. | Refresh the browser. |
In BMC Helix Dashboards , you can see errors on the dashboards and you cannot perform any operations. Error: Data has no 'status field'. Check Query and Bar Data field configurations | This issue occurs when a BMC Helix Dashboards instance is open and you sign out of any other BMC Helix applications, such as BMC Helix Portal or BMC Helix Operations Management. The following image shows a sample error:
| Log in to BMC Helix Portal again, and cross launch to BMC Helix Dashboards. |
In BMC Helix Dashboards , you can see errors on the dashboards and you cannot perform any operations.Error 552: The SQL database Operation failed. Metric column must be of String data type | This issue occurs when the _metric_ clause is not added to a string data type field. The following image shows a sample error:
| In the SQL query, you must add _metric_ clause to a string data type field only. |
In BMC Helix Dashboards , you can see errors on the dashboards and you cannot perform any operations.Error 552: The SQL database Operation failed., No Column with name__time__found | This issue occurs when the Date column misses the _time_ clause. The following image shows a sample error:
| In the SQL query, you must add _time_ clause the Date column. For example, currentDate() AS _time_. |
Unexpected error/timeout error for non admin
|  | Please check if this error is appearing only for non-admin users. If yes, then we will have to look at optimizing the panel / variable query for which this error is appearing. |
Inner join issue arsqlquery API throws [ERROR (585): Failed to parse the SQL; Join type 'ALIAS' is not supported. | Related platform defect is resolved with above platform versions. Please check if your platform version is compatible. | |
| Chatbot dashboard/reports data is not visible to non admin users | This Event Report Access Role should be added as part of any functional role (as shown above) so that when that functional role is provided to the user, it will get this role assigned implicitly. | |
Error - 93 - Helix Dashboards - Reports are running out of time |
| If there is huge data expected as a result then please Set panel header -> Timeout = 600 so that data can be fetched completely without timeout issue. Alternatively, you can look for optimizing the query. Also additional filters can be introduced in the query so that result set will be limited and it will be loaded within time. |
