Limitations and requirements for Data snapshots
Summarize
Summarized using AI
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.
Summary of Limitations and Requirements for Data Snapshots
This document outlines the limitations and requirements for using Data Snapshots within ServiceNow, particularly focusing on database compatibility, supported features, and restrictions on indicators and breakdowns. Understanding these limitations is crucial for effective implementation and use of Data Snapshots in your organization.
Show less
Key Features
- Database Requirements: Only RaptorDB Professional (PostgreSQL) databases are supported; Oracle and MariaDB/MySQL are not.
- Domain Separation: Domain-separated instances are not compatible with Data Snapshots.
- System Tables: System tables (sys) are not supported.
- Supported Breakdown Types: Only breakdowns on Choice fields that are strings or integers are allowed; purely string and numeric fields are not.
- Query Operators: Certain operators are unsupported across various fields, such as boolean, currency, and string types.
Key Outcomes
By adhering to these limitations and requirements, customers can ensure that Data Snapshots function correctly within their environment. Key outcomes include:
- Effective data management and reporting through automated indicators and breakdowns.
- Clarity on what configurations and types are permissible, minimizing errors during setup.
- Streamlined data collection processes with daily collections and time zone specifications for accurate reporting.
Understanding these aspects will aid ServiceNow customers in making informed decisions regarding the implementation of Data Snapshots, ensuring that all necessary conditions are met for optimal performance.
Several features of indicators and breakdowns are not supported with Data snapshots and multiple breakdowns.
Instance-level limitations
| Limitation or unsupported feature | Notes |
|---|---|
| Database requirements | Only instances with the RaptorDB Professional (PostgreSQL) database are supported, not Oracle or MariaDB/MySQL. (Checked when plugin is activated.) |
| Domain separation | Domain-separated instances are not supported. |
Table-level limitations
| Limitation or unsupported feature | Notes |
|---|---|
| System tables | System tables (named sys_*) are not supported. |
| Benchmarking indicators | Not supported |
Indicator- and breakdown-level limitations
| Limitation or unsupported feature | Notes |
|---|---|
|
Benchmarking indicators |
Not supported |
| Indicators with no conditions | Not supported |
| Scripted breakdown mappings/aggregations | Not supported |
| Breakdowns/aggregations on string and numeric type fields are not supported | The same limitations apply as with classic Performance Analytics breakdowns and indicators: Breakdowns on Choice fields that are strings or integers are supported. Only purely string and numeric fields are not supported. For example, a breakdown on Incident.Category would be supported because Category is a Choice field. A breakdown on Short Description would not be supported, because that is purely a string. |
| Only some query operators are supported | Unsupported operators for each field type on the source:
|
| Formula indicators | All contributing indicators must support Data snapshots. |
| Formula methods | Formula indicators that use methods in their formulas are not supported. |
| Manual or external indicators or breakdowns | Only automated indicators, formula indicators, and automated breakdowns are supported. All contributing indicators in a formula indicator must be supported for the formula indicator to be supported. |
| Indicators based on database views | Only supported when the join conditions do not include fields other than sys_id. |
| Database view prefix limitations | If the indicator source is a database view and there is an uppercase character in the database view prefix, the indicator is not supported. Also, if the two tables in the database view have the same prefix, the indicator is not supported. |
| Indicators with more than 250 breakdown/aggregation fields | Only 250 levels of breakdown are supported. |
| Indicators whose collection jobs have more than one timezone | Only daily collection and only one timezone are supported. |
| Historical processing | Only data collected after the enablement date is supported. Attempts to apply more than two levels of breakdown to older data do not return any results. |
| Breakdown matrices | Not applicable. All breakdown combinations are supported by design. |
| Collection periods set on data collector | All collections are daily. |
Field-level limitations (Indicator, breakdown, source, and data collector fields)
| Limitation or unsupported feature | Notes |
|---|---|
| Label for unmatched | The Label for unmatched option on breakdown sources is ignored with Data snapshots. |
| Value when nil | The Value when nil option on automated indicators is ignored with Data snapshots. |
| Security type | Data snapshots does not support the security type defined in the breakdown source. |
| Data collection job settings | Start/end periods, specific time configurations, and other settings do not affect Data snapshots. All data collection is daily. Only the timezone set on the data collection record has an effect. |
| Bucket groups | Not supported |
| Related list conditions | Related list conditions do not apply with Data snapshots |
| Targets and Thresholds | Support only up to two filters. |
| KPI Signals | Support only one filter. |
| Indicator scorecard visualizations | Support only up to two filters. |
| Scoresheets | Manual changes to scoresheets for indicators that are enabled for Data snapshots have no effect. |
| String fields in indicator or source conditions | 4000-character limit |