---
sourceDocument: Brazil Platform Analytics
sourceDocumentLink: https://www.servicenow.com/docs/r/now-intelligence

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Map a bucket group to a field

# Map a bucket group to a Data snapshots source field {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read  
To be able to filter Data snapshots scores by a numeric field on the source table, map a bucket group to that field. The bucket group splits that field into value ranges.

## Before you begin

Role required: pa_power_user or higher

## About this task

There are two types of fields that you can map a bucket group to:

* A normal numeric table field
* A [calculated field](https://www.servicenow.com/docs/SAYEkH1d7Qjsj7I4aT4WVg#gloss-calculated-field "Shows the difference between two date/time fields on a Data snapshots source table. For example, a calculated field on the Created and Updated fields shows the time difference between when a record was created and the last update made to it. Often requires a bucket group mapping.") that you created on two date/time fields. You have to map a bucket group to a calculated field to use that field as an indicator filter in KPI Details. For more information, see [Create a calculated field for a Data snapshots source](https://www.servicenow.com/docs/hN_J2sPBSzCmk3lMXl8tQA "Show the length of time that has passed between two date/time fields on a Data snapshots source table. For example, calculate Age as the difference between Created and Updated. Use this value as an aggregate field on an indicator or in a bucket group mapping.").
{#map-bucket-group-to-ds-source__ul_byr_rt5_bkc}  
Note:  
You can also map a bucket group to a Choice field. Doing so replaces the Choices in the field with the values in the Bucket group.

## Procedure

1. Navigate to AllPlatform Analytics AdministrationBreakdownsBucket Group Mappings and select New.
2. Fill in the fields as follows:  
   {#map-bucket-group-to-ds-source__table_gk4_fv5_bkc__entry__2}

   | Field | Contents |
   |-|-|
   | Indicator | The name of the Data snapshots indicator that you want to use a bucket group for |
   | Field type | Select from Calculated fields or Table fields |
   | Field/Calculated field | Name of the field that you are mapping the bucket group to |
   | Bucket group | Name of the bucket group that you are mapping to the field. If none of the existing bucket groups meet your needs, create one as described in [Create a bucket group](https://www.servicenow.com/docs/7OIuZPdkIMt0ipvB1_aJzw#t_CreateABucketGroup "Specify a group of buckets into which you want to recategorize data."). |
   [ ]

   {#map-bucket-group-to-ds-source__table_gk4_fv5_bkc}
3. Select Update.
{#map-bucket-group-to-ds-source__steps_bx3_3vk_hkc}

## Mapping a bucket group to a table field {#map-bucket-group-to-ds-source__example_lgn_vv5_bkc}

You want to filter the count of resolved incidents by the length of time it took to resolve them. You have created a Data snapshots source named incident_dataset, which you use for Data snapshots indicators on the Incident
\[incident\] table. You have also created an indicator named Resolved incidents, which is a record count on the Incident table of incidents where the Resolve time \> 0. The Resolve time field contains the time taken to resolve
each incident, which is the data that you want to filter indicator scores by.

However, Resolve time is a numerical field of time in seconds. The range of values of this field on your instance is from 0 to something over 9 million. Technically, you are not allowed to use a numerical field to filter
indicator scores, and practically, you would not want to. Instead, you have to split these values into discreet buckets.  
You look through the existing bucket groups but cannot find one that is suitable. So you calculate the number of seconds in a day, and you create a bucket group called Resolution time based on days:

* Unresolved: 0-1 second
* \< 1 day: 1-86,400 seconds
* 1-5 days: 86,400-432,000 seconds
* 5-30 days: 432,000-2,592,000 seconds
* 30-90 days: 2,592,000-7,776,000 seconds
* \> 90 days: 7,776,000 seconds +
{#map-bucket-group-to-ds-source__ul_rkb_tx5_bkc}
Figure 1. The Resolution Time bucket group  
Now, you create a bucket group mapping of the Resolution time bucket group to the Incident.Resolve time field.{#map-bucket-group-to-ds-source__table_jfr_vy5_bkc__entry__2}

| Record field | Value |
|-|-|
| Indicator | Resolved incidents |
| Field type | Table fields |
| Field | Resolve time |
| Bucket group | Resolution time |
[Table 1. Mapping of Resolution time buckets to Resolve time field]

{#map-bucket-group-to-ds-source__table_jfr_vy5_bkc}  
On KPI Details, you open the Resolved incidents indicator. In the filter panel, you expand Resolve time and see the Resolution time buckets. You select the buckets that interest you and also select Display as separate time series.Figure 2. The Resolved incidents indicator grouped by Resolve time

You have a separate time series of counts for resolved incidents in each resolution time bucket.

## Mapping a bucket group to a calculated field {#map-bucket-group-to-ds-source__example_yhs_x1v_bkc}

You would like to examine how old incidents were when they resolved. There is no field on Incident \[incident\] that tallies incident age. Therefore, you create a calculated field on the Incident table that shows the difference between the Created and Updated time stamps. The last time the incident was updated serves as a proxy for when the incident was resolved. (For more information, see [Create a calculated field for a Data snapshots source](https://www.servicenow.com/docs/hN_J2sPBSzCmk3lMXl8tQA "Show the length of time that has passed between two date/time fields on a Data snapshots source table. For example, calculate Age as the difference between Created and Updated. Use this value as an aggregate field on an indicator or in a bucket group mapping.").)Figure 3. Calculated field for incident age

The Age calculated field appears under Eligible calculated fields on the Data snapshots source for the Incident table. It is eligible because both fields in the formula are listed as fields that can be used as filters.
Figure 4. Age as an eligible calculated field for incident indicators  
However, you still can't use the Age field to filter indicator scores in KPI Details. It is a numeric field. To use the Age field, you have to map a bucket group to the field. Fortunately, there is a suitable bucket group called Incident Age Range that is provided in the base system. You map this bucket group to the Age field on the Resolved Incidents indicator.{#map-bucket-group-to-ds-source__table_n2d_kdc_ckc__entry__2}

| Record field | Value |
|-|-|
| Indicator | Resolved incidents |
| Field type | Calculated fields |
| Calculated Field | Age |
| Bucket group | Incident Age Range |
[Table 2. Mapping of Incident Age Range buckets to Age field]

{#map-bucket-group-to-ds-source__table_n2d_kdc_ckc}

On KPI Details, you open the Resolved incidents indicator. You look for Age under the filters but don't find it. Therefore, you select Configure on the Filters panel and select the Age
filter.
Figure 5. Selecting the Age filter for Resolved incidents on KPI Details

Now you can filter scores by Age. You choose every age bucket and Display as separate time series, to get a separate line for each bucket.
Figure 6. The Resolved incidents indicator grouped by Age

*[\>]: and then


