--- sourceDocument: Xanadu Platform Analytics sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/now-intelligence Release : - xanadu ft:locale : - en-US ft:publication_title : - Xanadu Platform Analytics ft:clusterId : - par bundleId : - par workflow : - Platform --- # Report ranges # Report ranges {#ariaid-title1} * Release version: Xanadu * * Updated August 1, 2024 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Use a report range to define data intervals that are used in bar, donut, and pie charts in Platform Analytics data visualizations and Core UI reports.{#c_ReportRanges__ph_czl_p1x_yy} Sometimes it can be helpful to group results into ranges or buckets rather than viewing every result as an individual score. Think of a bar or pie chart which shows the date of creation of incidents. By default, each individual value would be a separate data point, creating an unnecessarily crowded-looking visual. However, segmenting the results into logical groups of dates can add context and help the audience understand which ranges are good, bad, or concerning. Example use case: There is a significant cost involved to a business each time a SLA is breached at a company. A Service Manager can see how many tasks were completed well within the SLA versus how many elapsed during the SLA. This information helps them identify which SLAs may need to be adjusted. Note: Reports only show historical data. It is not possible to set report ranges for dates in the future. Figure 1. Incidents created date with ranges ## How report ranges work {#ariaid-title2} Report ranges work with elements that hold only dates, lists, or integers. {#r_HowReportRangesWork__table_ls3_tbc_zp__entry__2} | Type | Examples | |-|-| | Dates | Using the Created field in the Incident table: Same Day, 2 Days, 2--5 Days, 5--7 Days, 1--2 Weeks, 2--4 Weeks, 1--2 Months, \> 2 Months | | Lists | Using the Priority field in the Incident table: Low, Moderate, High, Critical, Planning | | Integers | Using the Count field in the Incident table: Overloaded, Optimized, Under Utilized | [Table 1. Report range elements list] {#r_HowReportRangesWork__table_ls3_tbc_zp} Report ranges can be globally applied to all date type fields (date, due date, duration, date/time, date time), or you can limit report ranges to a specific table.{#r_HowReportRangesWork__ph_x23_t1x_yy} ## View all report ranges {#ariaid-title3} To view all currently configured report ranges, navigate to ReportsAdministrationReport Ranges or Platform Analytics AdministrationColor SettingsReport Ranges. Figure 2. Report ranges list The following are important columns and their associated data types: {#r_ViewAllReportRanges__table_nr4_rcc_zp__entry__2} | Field | Corresponding data type | |-|-| | Upper value duration | Date - works with elements that store dates. | | Upper value int | Integer - works with elements that store numbers. | | Value list | List - works with elements that store a list item. | [Table 2. Report range list field] {#r_ViewAllReportRanges__table_nr4_rcc_zp} ## Create a report range {#ariaid-title4} Create a report range to define data intervals that are used in bar, donut, and pie charts in reports and data visualizations.{#t_DefineAReportRange__ph_g1r_hdx_yy} ### Before you begin Role required: itil, report_user, report_group, report_global, report_admin, or admin. {#t_DefineAReportRange__ph_report-role-required} ### Procedure 1. Navigate to AllReportsAdministrationReport Ranges. If you have fully migrated to Platform Analytics, navigate to AllPlatform Analytics AdministrationColor SettingsReport Ranges. 2. Select New. 3. Fill in the form (see table): Use the following fields to refine the data displayed in the report and to design the appearance of your report visualization:{#t_DefineAReportRange__p_vhq_cgc_wy} {#t_DefineAReportRange__table_uxv_g2c_zp__entry__2}{#t_DefineAReportRange__drrName}{#t_DefineAReportRange__drrElement}{#t_DefineAReportRange__drrLabel}{#t_DefineAReportRange__drrValList1}{#t_DefineAReportRange__drrColName}{#t_DefineAReportRange__drrUVI}{#t_DefineAReportRange__UVD}{#t_DefineAReportRange__drrDisplay}{#t_DefineAReportRange__drrOrder1} | Field | Description | |-|-| | Name | The name of the table to draw the values from. Note: This field is required before you can select from the Element list. | | Element | The table field to draw the values from. | | Label | The name for the report range that is displayed in reports. | | Value list | For list elements, this field defines which values are within the range. After the range is saved, the value list is populated with the choices of the element. | | Color name | The color from the Color Definitions table to display this report range in. The color appears in the Display field. If you enter a color name, you do not need to enter a color value. Note: When creating reports, colors may not display as specified for ranges on Group by report fields selected via dot-walking. For this feature to work appropriately, select applicable Group by fields from the base table only. | | Upper value int | For integer-type elements, this field defines the upper limit of the range. The upper value of the report range with nearest lower Order defines the lower limit of this range. If no range with a lower Order exists, the lower limit is zero.{#t_DefineAReportRange__drrUVIint} Example: One report range has an upper limit of 10 and an Order of 20. A second report range has an upper limit of 5 and the Order of 19. The first report shows values from 6 to 10 in the formatting specified by this range. The second report shows values of 5 or less. | | Upper value duration | For duration-type elements, this field defines the upper limit of the range. The upper value of the report range with nearest lower Order defines the lower limit of this range. If no range with a lower Order exists, the lower limit is zero.{#t_DefineAReportRange__drrUVDdur} Example: One report range has an upper limit of 10 and an Order of 20. A second report range has an upper limit of 5 and the Order of 19. Values from 5 to 10 display the formatting specified by this range. | | Display | Read-only. Shows the color that is used for the specific report range. | | Order | The order in which the report ranges are used. If a value is defined within more than one label, it is reported under the report range with the lowest order. | [Table 3. Report range form fields] {#t_DefineAReportRange__table_uxv_g2c_zp} Note: Once configured, a report range will show as empty if there's no data available in your report. Context fields such as data labels or legend related to the configured report range will still show and be highlighted. ## Enable the report range module {#ariaid-title5} To use report ranges in your bar and pie charts, you must enable the report range module. ### Before you begin Role required: admin ### Procedure 1. Navigate to AllSystem DefinitionApplication Menus. 2. Open the Reports application menu. 3. In the Modules related list, enable the Report Ranges module. The Modules related list may have over 100 entries. Filter it on the word range to shorten your search. ### Result You can define report ranges for your pie and bar charts. *[\>]: and then