Limitations to generating data visualizations
While data visualization generation is designed to handle a wide range of queries and scenarios, certain cases are not supported or only partially supported.
| Query contents | Example | Limitation |
|---|---|---|
| Visualization type | "Show me a heatmap of open incidents by creation date" | Only the following visualization types are supported:
|
| Data source | "Show me open asset contracts" |
Only table data sources listed in the Semantic Table Configuration table are supported. See Add a table to the semantic data layer. |
| Multiple Group By conditions | "Show me open incidents by group and state." | Data visualization generation will produce results, but only the first 'group by' clause (group) will be considered. The second 'group by' clause (state) will be ignored in the current output. |
| Multiple time periods | "Show me open incidents last week, month, and year." | Data visualization generation is currently unable to process queries that request data for multiple time periods simultaneously. Only one time period can be handled at a time. |
| Conflicting or complementary conditions | "Show me resolved and unresolved cases last week." | Data visualization generation detects only the first condition (resolved) under the state column. The second condition (unresolved) is misinterpreted and may be incorrectly mapped to another column or ignored. |
| Multiple data tables | “Show me high priority incidents, problems and changes” | Data visualization generation identifies only the first table and ignores the other ones. |
| Non-English queries | -- | Only English is supported |
| Technical dashboards | -- | Data visualizations can be added only to dashboards that are created in the inline editor. Technical dashboards are not supported. |
Possible ways to circumvent limitations
- Simplify your queries by focusing on one 'group by' clause at a time.
- Specify a single time period per query.
- Avoid multiple conditions in a single query.