Field normalization and transformation

Release version: Xanadu

Updated August 1, 2024

2 minutes to read

Summarize

Summarized using AI

Summary of Field normalization and transformation

Field normalization and transformation in ServiceNow enhance data integrity and reduce duplication by standardizing field values. Normalization consolidates variations of a field value into a single preferred value to eliminate duplicates and improve search results. Transformation modifies raw input values into standardized formats based on defined rules and conditions, making data more meaningful for organizational use.

Show full answer Show less

Key Features

Normalization: Automatically replaces variations of field values with a single normalized value during data entry, queries, and scripts. It is most effective for descriptive fields like names or units of measurement.
Transformation: Applies rules to convert raw input into standardized values, such as removing suffixes from names or rounding numeric values. Transform rules determine processing order and stopping points.
Field Type Support: Normalization and transformation are enabled on specific field types by default (e.g., string, URL for normalization; decimal, float, integer, numeric for transformation). Administrators can create additional field type records but should avoid altering Sys ID fields directly to prevent data corruption.
Identification and Access: Fields with normalization or transformation have a normalization icon. Users with the normalizer role can access the corresponding records; others see a help page. Visibility of the icon can be restricted by role.
Configuration: Activation requires the Field Normalization plugin. Administrators can enable normalization/transformation per field type, create raw fields to display original input, and define transformation rules using default definitions or custom regex and pattern matching.
Limitations: Field normalization does not support domain separation, meaning it cannot be used in environments where data and processes are segregated by domains.

Practical Implications for ServiceNow Customers

By leveraging normalization and transformation, customers can ensure consistent and accurate data across their ServiceNow environment. This leads to improved data quality, reduced record duplication, and more reliable reporting and search functionality. Proper setup involves enabling the relevant plugins, configuring field types, and defining normalization or transformation rules tailored to organizational needs. Customers should avoid normalizing or transforming Sys ID fields directly to maintain system integrity.

Field Normalization includes normalization and transformation, which are two different ways to alter field values for increased data integrity and reduced duplication.

Normalization

Normalization searches for variations of the same field value and converts them into a single preferred value. By consolidating multiple variations of the same value into a single simple recognizable value, the system eliminates duplicate records and provides better search results. When a process or a user enters a value in a normalized field, the system determines whether to replace it with a normal value. Normalization also automatically adjusts queries to return normalized results and normalizes values in scripts.

While normalization is available for every field in the platform, it works best for descriptive values such as names or standard units of measurement. For example, you might create normalization rules to:

Set the CPU type of a computer CI to a standard model name such as Xeon.
Set the suffix used for the names of corporations to a standard format such as ServiceNow, Inc..

Transformation

Transformation converts raw field input values into standardized values that are more meaningful to an organization. Administrators control when transformation happens by defining rules and conditions for specific fields. For example, you might create transformation rules to:

Remove suffixes from user names such as Jr. and II.
Round computer CI RAM sizes to the nearest whole number such as rounding 4112 MB to 4000 MB.

Transform records make up the rules that define how a field transformation is executed. Order values determine the order in which each rule is evaluated. A check box on each transform enables an administrator to determine where processing stops when a rule evaluates to true.

Enabling normalization and transformation by field type

Field type records specify which data types are available for normalization and transformation. By default, the system supports normalization and transformation for these field types.


Field type	Use to normalize	Use to transform
Decimal	false	true
Float	false	true
Integer	false	true
Numeric	false	true
String	true	true
URL	true	true

A field type entry applies to all fields whose dictionary entry data type matches the field type entry. Administrators can create additional field type records for other data types as needed.

Warning:

Avoid creating field type records for fields that store a Sys ID value such as a reference field, field name field, or a table name field. Directly altering a Sys ID value is more likely to produce data corruption and broken references than to produce meaningful standard values. Instead, normalize or transform the display value associated with the Sys ID. For example, normalize the user name instead of the Sys ID of a specific user.

Identifying normalized fields

The system displays the normalization icon on fields with an associated normalization or transformation record. Users with the normalizer role can click the icon to access the associated normalization or transformation record. Users without the normalizer role instead see a help page. Administrators can configure who sees the normalization icon with a preference called Restrict to roles.