Field normalization and transformation

  • Release version: Zurich
  • Updated July 31, 2025
  • 2 minutes to read
  • 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 Field normalization and transformation

    Field normalization and transformation in ServiceNow Zurich release provide mechanisms to standardize field values, increasing data integrity and reducing duplication. Normalization consolidates variations of the same value into a preferred, consistent value, improving search accuracy and record uniqueness. Transformation converts raw input values into standardized formats that better align with organizational needs, based on defined rules and conditions.

    Show full answer Show less

    Key Features

    • Normalization: Automatically replaces variant field values with a single preferred value during data entry, query execution, and scripting. Ideal for descriptive fields like names or units (e.g., standardizing CPU types or company suffixes).
    • Transformation: Applies rule-based conversions to field values, such as removing suffixes from user names or rounding numeric data. Rules have defined evaluation order and control over processing continuation.
    • Field type support: Normalization and transformation are enabled by default for certain field types (e.g., string, URL). Numeric types support transformation but not normalization. Administrators can add support for other data types as needed.
    • Safe usage guidance: Avoid applying normalization or transformation directly to Sys ID fields (such as references) to prevent data corruption. Instead, apply normalization or transformation to the display values associated with those IDs.
    • User interface: A normalization icon indicates fields with normalization or transformation rules. Users with the normalizer role can access these rules directly, while others see a help page. Visibility of this icon can be role-restricted by administrators.

    Practical Benefits

    By implementing field normalization and transformation, ServiceNow customers can expect:

    • Improved data consistency across records, reducing duplication and errors.
    • More accurate and reliable search results due to standardized field values.
    • Greater control over how data input is processed and stored, aligning with organizational standards.
    • Enhanced administrative oversight with clear rule management and user role-based access to normalization settings.

    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 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.