Instance-level limitations

• Database: Only instances with RaptorDB Professional (PostgreSQL) are supported; Oracle and MariaDB/MySQL are not.
• Domain Separation: Data snapshots are not supported in domain-separated instances.

Table-level limitations

• System Tables: Tables prefixed with sys are unsupported.
• Table Size and Change Volume:
  • Change Data Capture (CDC) requires manageable delta tracking; very large indicator sources or those with over 30 million records are unsupported due to performance risks.
  • If any contributing table has more than 1 million changes in the last month, data snapshots are disabled for that indicator.
• Benchmarking Indicators: Not supported at the table level.

Indicator- and breakdown-level limitations

• Benchmarking indicators and indicators without conditions are not supported.
• Scripted breakdown mappings and aggregations are unsupported.
• Breakdowns on purely string or numeric fields are not supported; however, breakdowns on Choice fields (strings or integers) are supported (e.g., Incident.Category supported, but Short Description is not).
• Only specific query operators are supported, varying by field type; several common operators are unsupported.
• Formula indicators require all contributing indicators to support data snapshots; formula methods within formulas are not supported.
• Only automated and formula indicators and automated breakdowns are supported; manual or external indicators/breakdowns are excluded.
• Indicators based on database views are supported only if join conditions involve sysid fields exclusively, without uppercase characters in prefixes, and no duplicate prefixes across tables.
• Indicators can have up to 250 breakdown or aggregation fields.
• Only daily collection jobs with a single timezone are supported; multiple timezones are not supported.
• Historical data processing supports only data collected after data snapshot enablement; older data with more than two breakdown levels returns no results.
• Breakdown matrices are not applicable; all breakdown combinations are supported by design.
• Collection periods and time configurations on data collectors are ignored; all collections are daily, respecting only the timezone on the collection record.

Field-level limitations

• The Label for unmatched option on breakdown sources is ignored.
• The Value when nil option on automated indicators is ignored.
• Security types defined in breakdown sources are not supported.
• Data collection job settings such as start/end periods or specific time configurations do not affect data snapshots; only the timezone on the data collection record matters.
• Bucket groups are not supported.
• Related list conditions do not apply to data snapshots.

Additional feature-specific limitations

• Targets and Thresholds: Support up to two filters.
• KPI Signals: Support only one filter.
• Indicator Scorecard Visualizations: Support up to two filters.
• Scoresheets: Manual changes to scoresheets have no effect for indicators enabled with data snapshots.
• String fields in indicator or source conditions: Limited to 4000 characters.

Practical Implications for ServiceNow Customers

When planning to leverage data snapshots, ensure your instance uses RaptorDB Professional and is not domain-separated. Large data sources or highly dynamic tables may not be eligible due to size and change volume constraints. Design indicators and breakdowns within supported parameters, avoiding unsupported field types, operators, and scripted elements. Understand that data snapshots operate on daily collections and have limited support for multi-timezone and historical data. Awareness of these limitations will help you optimize your indicator configurations and maintain expected performance and data integrity when using data snapshots.