Creating Custom Age in Days gruops

[brandimore]

Hello

The out of the box groupings for dates is a bit limiting and we want to create our own. I see you can create buckets but there's no mention in this document in how to apply it.

We want a report that is grouped by custom groupings

0 - 7 days

7-30 days

etc...

I've created the bucket group now what? How do you apply that to a report?

https://docs.servicenow.com/bundle/helsinki-performance-analytics-and-reporting/page/use/performance-analytics/task/t_CreateABucketGroup.html

[Adam Stout]

Buckets are for PA.  For Reporting, you want Report Ranges: https://docs.servicenow.com/bundle/kingston-performance-analytics-and-reporting/page/use/reporting/c...

You need report_admin to manage report ranges, but prior to Jakarta (I believe), you had to be an admin to see the module.  If you have report_admin but don't see the module, just type in "sys_report_range.list" in the nav menu.

[Dennis R]

Adam is right; there's an important distinction between report ranges used for normal reports and bucket groups used for Performance Analytics indicators. Which are you trying to create and use? Report ranges are pretty straight-forward. Bucket groups are kind of brain-bending to folks who haven't worked with PA for a while. If you're looking for a specific use, we can probably help you get it set up.

[brandimore]

Hi Dennis

Thank you both for the responses! I am playing with report ranges and I wanted to confirm something. From what I can see, you can only have 1 range against a date. Therefore, if you create a range against the Created field in the Incidents Fact table, anytime someone pulls that date field into a report and into a bar chart for example, the range created will be used for that in all reports right?

I ask because some managers like to see different ranges and I'm thinking I'll need to create a range that is more of a global standard.

Am I correct in this thinking?

Thanks

[Adam Stout]

Yes, they are global to the table/field. There are positives and negative about this.  Consistency is good, but when managers need to see it a specific (and different way) we have an issue.

However, you can get around this if you only need it in a few reports by creating a view.  Then you can put the report range on the view instead of on the incident table proper.