Default currency values in lists

  • Release version: Yokohama
  • Updated January 30, 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 Default currency values in lists

    In ServiceNow lists, currency values are displayed according to the user’s session currency and formatted based on the user’s locale. This ensures that currency amounts are clear and relevant to the user’s context when viewing records containing currency or price fields.

    Show full answer Show less

    Currency Display Behavior

    • Currency field type: Values show in the user’s session currency.
    • Price field type:
      • Calculated: Displays value in session currency.
      • Fixed: Shows the currency value exactly as entered by the user.
      • Multiple: Shows value in session currency if available; otherwise, converts the first entered value.
    • A Globe icon appears beside currency values when the session currency differs from the entered currency. Clicking it cycles through three display modes:
      • Value as entered by the user.
      • Value converted to session currency.
      • Value as entered with the session currency equivalent shown in brackets.
    • Record previews always show currency values as originally entered but formatted for the user’s locale.

    Aggregation of Currency Values

    Aggregation operations such as total, average, minimum, and maximum can be performed on currency columns. The process aggregates reference currency values from all records, then converts the aggregate to the user’s session currency for display.

    Important considerations:

    • The displayed aggregate might be unexpected due to currency conversion rate changes between when individual records were created and when aggregation occurs.
    • For Fixed price types, reference values used in aggregation may be outdated.
    • For Multiple price types, only the reference value of the first price entered is used in aggregation.
    • Currency fields store values with four decimal places; aggregates also display with four decimals. Upgrading customers should configure the glide.currencyprice.useallfractiondigits property to maintain this precision.

    Filtering on Currency Fields

    Filters on currency fields require entering both a currency code and numeric value. Filtering compares the filter’s value converted to reference currency against the reference currency values stored in records.

    Key notes on filtering:

    • Filtering results might be inconsistent if conversion rates used during filtering differ from rates used when individual record values were calculated.
    • For Fixed price fields, the reference value used in filtering can be outdated.
    • For Multiple price fields, only the first entered reference value is used for filtering.

    Practical Impact for ServiceNow Customers

    This functionality ensures currency values in lists are user-friendly and localized, supporting multi-currency environments effectively. Understanding the nuances of currency type behavior, aggregation, and filtering helps customers anticipate potential discrepancies due to currency rate changes and data storage limitations. Configuring related system properties ensures precision in currency displays and calculations.

    In lists, default currency values appear in the user’s session currency, formatted for display in the user’s locale. Typically, a formatted number follows the currency symbol.

    Different field types appear as follows in lists:
    Field Description
    Currency field type Value expressed in the user’s session currency.
    Price field type
    • Calculated: Value in the user’s session currency.
    • Fixed: Currency value, as entered by the user.
    • Multiple: Value associated with the user’s session currency if this value exists. Otherwise, the first value entered converts to the user’s session currency.
    A Globe icon appears beside the currency value that enables you change to one of the following values:
    • Value as entered by the user.
    • Value in session currency.
    • Value as entered and, in brackets, the value in reference currency.

    The icon appears when the user’s session currency is different from the currency entered. Clicking the icon cycles through the listed displays. In the preview for the record, currency values appear as entered, formatted in the user’s locale.

    Aggregation

    Aggregation operations can be used on currency columns. Aggregation operations include total, group by, average, minimum, and maximum. Aggregation is done in two steps:
    • Aggregate the reference currency values for all records.
    • Convert this aggregate to the user’s session currency for display.
    Note:
    The resulting value may not be what you expect. The conversion rate used for the value that appears for the currency field, and for its reference currency, that is used for the aggregation, may have changed.
    This limitation extends to different price types.
    • For price type fixed, the calculated reference value can be old.
    • For price type multiple, the reference value of the first price entered is used. The other values are not used.

    The aggregate value is shown formatted in user’s locale with a currency symbol. Currency fields are stored with four decimal places, and aggregates have four decimal places. For upgrades, you must set the glide.currency_price.use_all_fraction_digits property. See Change default currency decimal places for more information.

    Filtering

    You can set up filters on currency fields. The currency value is entered as a currency code and numeric value. Filtering is done in two steps:
    • The filter currency value is converted to the reference currency.
    • The filter’s calculated reference value is compared with the reference value in the records.

    Matching records are shown in the list view.

    Note:
    At times, the filtering results might not provide the expected result. The conversion rate used when you run the filter might be different than the conversion rate used when calculating the reference values in the individual records. This limitation extends to the following price types:
    • For a Fixed price field type, the calculated reference value can be old.
    • For a Multiple price field type, it uses the reference value of the first price, and does not use the other values.