Trend Reports and Dashboard shows inaccurate data by week across the end of a year. Due to Incorrect Week-Year Mapping in PostgreSQL - Known Error

Trend Reports and Dashboard shows inaccurate data by week across the end of a year. Due to Incorrect Week-Year Mapping in PostgreSQL Description On instances using a PostgreSQL database, an incorrect year reference ( yearref ) is returned for the non-ISO week functions sunday_week and monday_week . As a result, the column data displays trends for future dates where no actual record data exists.

This issue affects reports and dashboards that group or summarize data by week across the end of a year. As a result, reports may display an unexplained empty week in one year, a duplicated week in another, or records appearing in the incorrect annual bucket.

Steps to Reproduce

Alternate Steps to Reproduce (March 31, 2026): (You may create the report on Opened field as well. Change steps accordingly)

a. Create Data Visualization report with

Source: Incident as data source with filter as Created > 2025-12-15 00:00:00 and Created < 2026-01-16 00:00:00)

Weekly Trend on Created date field

b. Create some demo incidents with Created date updated to be between 2025-12-15 and 2026-01-15

c. Configure the properties like below for sunday_week

glide.db.week_numbering = sunday_week glide.ui.filter.first_day_of_week = 1 glide.ui.date_format.first_day_of_week = 1

or configure monday_week like below

glide.db.week_numbering = monday_week glide.ui.filter.first_day_of_week = 2 glide.ui.date_format.first_day_of_week = 2

d. Refresh the report and you may see that one of the aggregate date shows up for Dec 2026. When you click on that column bar, you will not see any data

Expected: Not show trend column bars for non existing data.

Original Steps to Reproduce

1. On an Oracle or RaptorDB instance, create a table called u_time_trend_test that includes a String column named c_name. 2. Set glide.db.week_numbering to monday_week. 2. Run the following scripts:

var gr = new GlideRecord("u_time_trend_test"); for (var i = 0; i

gr.setValue("c_name", "ABC".at(i % 3)); var sysId = gr.insert();

var startDate = new Date('2024-11-15'); var futureDate = new Date(startDate); futureDate.setDate(startDate.getDate() + i); var formattedDate = futureDate.toISOString().split('T')[0];

var gr2 = new GlideRecord("u_time_trend_test"); gr.addQuery("sys_id", sysId); gr.setValue("sys_created_on", formattedDate); gr.update(); }

This creates 100 records on u_time_trend_test.

3. Run the following scripts:

var ga = new GlideAggregate('u_time_trend_test'); ga.addQuery('sys_created_on', '>=', '2024-12-27'); ga.addQuery('sys_created_on', ' ga.addAggregate('COUNT'); ga.addTrend('sys_created_on', 'week'); ga.orderBy('sys_created_on'); ga.groupBy('c_name'); gs.trace(true); ga.query(); gs.trace(false);

var k = 0; while(ga.next()){

var tref = ga.getValue('timeref'); var sco = ga.getValue('sys_created_on'); gs.log(++k + " " + tref + " " + sco + " " + ga.getDisplayValue('c_name')); }

Actual (If timezone is set to GMT): *** Script: 1 12/23/2024 2024-12-27 00:00:00 A *** Script: 2 12/23/2024 2024-12-28 00:00:00 B *** Script: 3 12/23/2024 2024-12-29 00:00:00 C *** Script: 4 12/30/2024 2025-01-01 00:00:00 C *** Script: 5 12/30/2024 2025-01-02 00:00:00 A *** Script: 6 12/29/2025 2024-12-30 00:00:00 A *** Script: 7 12/29/2025 2024-12-31 00:00:00 B

(If timezone is set to Los Angeles): *** Script: 1 12/23/2024 2024-12-27 00:00:00 A *** Script: 2 12/23/2024 2024-12-28 00:00:00 B *** Script: 3 12/23/2024 2024-12-29 00:00:00 C *** Script: 4 12/23/2024 2024-12-30 00:00:00 A *** Script: 5 12/30/2024 2025-01-02 00:00:00 A *** Script: 6 12/29/2025 2024-12-31 00:00:00 B *** Script: 7 12/29/2025 2025-01-01 00:00:00 C

Expected: The start of the week is correct.

Note: This line "*** Script: 4 12/23/2024 2024-12-30 00:00:00 A" is correct because sys_created_on in Los Angeles time is actually 2024-12-29 16:00:00.

In addition, make sure to test for other years, make sure it also works if setting:

glide.db.week_numbering = sunday_week glide.ui.filter.first_day_of_week = 1 glide.ui.date_format.first_day_of_week = 1

and

glide.db.week_numbering = monday_week glide.ui.filter.first_day_of_week = 2 glide.ui.date_format.first_day_of_week = 2

Workaround This problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.

Until a permanent fix is available, you can use this workaround to resolve the issue.

1. Set the following properties to the specified values for improved report appearance:

glide.db.week_numbering = iso_week glide.ui.filter.first_day_of_week = 2 glide.ui.date_format.first_day_of_week = 2 Servicenow Document : https://www.servicenow.com/docs/r/xanadu/now-intelligence/reporting/modify-add-calendar-sys-props.html