If a column or row in the report does not have a corresponding value, it will be omitted.

[MugTm09]

If a column or row in the report does not have a corresponding value, it will be omitted.

Users don't like the default collapsing because they want to see all elements that match the filter criteria,

even if the count is 0. Is there a way to toggle this collapsing to non-collapse?

[Bhuvan]

@MugTm09 

Try using additional filtering conditions in the report, refer below knowledge article for more details

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0823770

If this helped to answer your query, please mark it helpful & accept the solution.

Thanks,

Bhuvan

[MugTm09]

Thanks, @Bhuvan  .
Unfortunately, Since the record itself does not exist, this KB article could not resolve the issue.

I thought it would be difficult to aggregate data in ServiceNow while taking into account the possible states of non-existent records.

Regards

[Ankur Bawiskar]

@MugTm09 

please share screenshots of what you are referring.

[MugTm09]

Hi, @Ankur Bawiskar .

I'd like to explain this using an Out-of-the-Box (OTB) field instead of a screenshot, specifically using the opened_at field, which contains datetime values.

​Scenario: Assume 10 incidents occurred over the last 7 days. A user wishes to aggregate this data.

​Request:

​When a 7-day filter is applied, the user wants the visualization (on the x-axis, y-axis, or in a pivot table, etc.) granularity for the data display to show the following:

​Daily granularity: 7 \times 1 aggregated point \times 86,400 granular steps per day (seconds)

​Hourly granularity: 7 \times 24 aggregated points \times 1,440 granular steps per day (minutes)

​Minute granularity: 7 \times 24 \times 60 aggregated points \times 24 granular steps per day (hours)

​This means the user explicitly wants to display a massive number of points—calculated as the selected aggregation granularity multiplied by 7—along with a large number of zero-value displays and meaningless aggregation levels, without any automatic collapsing or intelligent binning.

----​Here is another, more problematic example.

​Scenario:

​Assume you have created a simple String type custom field named "Rating" that is designed to contain a single alphabetical character.

​The actual records in the database only contain three values: "A", "B", and "F".

​User Request:

​The user demands a data visualization (e.g., a bar chart, pivot table) that arbitrarily aggregates the data to include non-existent granularity levels such as "S", "C", "D", and "E".

​The purpose of this is to emphasize two points:

​That the count for "S" is zero (highlighting the lack of top performance).

​How bad "F" is (by comparing it against the full, defined rating scale).

Problem:

​It is not possible to aggregate the data using these non-existent items as aggregation granularities and display a count of zero for them, because the visualization tool typically only displays the distinct values found in the actual data ("A", "B", and "F").