--- sourceDocument: Australia Platform Analytics sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/now-intelligence Release : - australia ft:locale : - de-DE ft:publication_title : - Australia Platform Analytics ft:clusterId : - par bundleId : - par workflow : - Platform --- # Limitations and requirements for Data snapshots # Limitations and requirements for Data snapshots {#ariaid-title1} * Freigeben Version: Australia * * Aktualisiert 12. März 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer Several features of indicators and breakdowns are not supported with Data snapshots and multiple breakdowns. ## Instance-level limitations {#limitations-mlb__section_fw3_dhl_5dc} {#limitations-mlb__table_r42_chl_5dc__entry__2} | Limitation or unsupported feature | Notes | |-|-| | Database requirements | Only instances with the [RaptorDB Professional (PostgreSQL) database](https://www.servicenow.com/docs/access?context=raptordb&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US) are supported, not Oracle or MariaDB/MySQL. (Checked when plugin is activated.) | | Domain separation | Domain-separated instances are not supported. | [ ] {#limitations-mlb__table_r42_chl_5dc} ## Table-level limitations {#limitations-mlb__section_oyy_j3l_5dc} {#limitations-mlb__table_table-limitations__entry__2} | Limitation or unsupported feature | Notes | |-|-| | System tables | System tables (named sys_\*) are not supported. | | Benchmarking indicators | Not supported | [ ] {#limitations-mlb__table_table-limitations} ## Indicator- and breakdown-level limitations {#limitations-mlb__section_pyy_j3l_5dc} {#limitations-mlb__table_indicator-limitations__entry__2} | 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: * Boolean/ChoiceTable/Reference: ISEMPTYSTRING * SysClassName: INSTANCEOF * String: MATCH_PAT and MATCH_RGX * Currency: NOT_EQUALS, LESS_THAN, GREATER_THAN, LESS_THAN_OR_EQUALS, GREATER_THAN_OR_EQUALS, BETWEEN, EQUALS * Relative Dates: LESS_THAN, LESS_THAN_EQ, GREATER_THAN, GREATER_THAN_EQ, BETWEEN {#limitations-mlb__ul_s42_chl_5dc} | | Formula indicators | All [contributing indicators](https://servicenow-prod.fluidtopics.net/zamNVg2135oSvT9fSCJtZA#gloss-contributing-indicator "An indicator that is used in the formula of a formula indicator. A contributing indicator can be an automated or a formula indicator.") 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](https://servicenow-prod.fluidtopics.net/zamNVg2135oSvT9fSCJtZA#gloss-automated-indicator "An automated indicator uses an indicator source as its data set. The indicator source specifies a table or database view, conditions for filtering records from that source, and the frequency at which you expect to display the data. The indicator applies an aggregator and optional conditions to this data. The indicator also specifies a data collection job and any breakdowns to apply."), [formula indicators](https://servicenow-prod.fluidtopics.net/zamNVg2135oSvT9fSCJtZA#gloss-formula-indicator "Produces a computed indicator score from one or more other indicators. Besides indicator scores, the formula can include calculations such as the gap between an indicator score and the indicator target."), and [automated breakdowns](https://servicenow-prod.fluidtopics.net/zamNVg2135oSvT9fSCJtZA#automated-breakdown "Automated breakdowns are based on a breakdown source, which is a set of records from a table. The breakdown maps these records, known as breakdown elements, with fields on tables that indicators collect scores from. Scores collected from mapped tables can then be grouped and filtered based on the values in the mapped fields and the breakdown elements.") are supported. All contributing indicators in a formula indicator must be supported for the formula indicator to be supported. | | Indicators based on [database views](https://servicenow-prod.fluidtopics.net/zamNVg2135oSvT9fSCJtZA#gloss-database-view "A database view defines table joins for reporting purposes. For example, a database view can join the Incident table to the Metric Definition table. This view can be used for an indicator source.") | 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. | [ ] {#limitations-mlb__table_indicator-limitations} ## Field-level limitations (Indicator, breakdown, source, and data collector fields) {#limitations-mlb__section_section_field-limitations} {#limitations-mlb__table_indicator-field-limitations__entry__2} | 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 | [ ] {#limitations-mlb__table_indicator-field-limitations}