Stack trace error "No matching records: com.glideapp.report.charting_v2.exceptions.ChartDataGenException" is thrown when no data is returned for a multi-level pivot report - Known Error

Stack trace error "No matching records: com.glideapp.report.charting_v2.exceptions.ChartDataGenException" is thrown when no data is returned for a multi-level pivot report Description When a multi-level pivot report doesn't have any data to return the following error is logged to the [syslog] table:

No matching records: com.glideapp.report.charting_v2.exceptions.ChartDataGenException: No matching records: com.glideapp.report.charting_v2.datagen.pivot.PivotDataGenerator.validatePivotData(PivotDataGenerator.java:123) com.glideapp.report.charting_v2.datagen.pivot.PivotDataGenerator.generateJSONResponse(PivotDataGenerator.java:70) com.glideapp.report.charting_v2.datagen.pivot.PivotDataGenerator.generate(PivotDataGenerator.java:42) com.glide.processors.report.run.PivotRunProcessor.processRequest(PivotRunProcessor.java:26) com.glide.processors.report.run.ReportRunProcessor.process(ReportRunProcessor.java:44) com.glide.processors.XMLHttpProcessor.processJavaAJAX(XMLHttpProcessor.java:151) com.glide.processors.XMLHttpProcessor.process(XMLHttpProcessor.java:104) com.glide.processors.AProcessor.runProcessor(AProcessor.java:474) com.glide.processors.AProcessor.processTransaction(AProcessor.java:199) com.glide.processors.ProcessorRegistry.process0(ProcessorRegistry.java:178) com.glide.processors.ProcessorRegistry.process(ProcessorRegistry.java:167) com.glide.ui.GlideServletTransaction.process(GlideServletTransaction.java:31) com.glide.sys.Transaction.run(Transaction.java:2037) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748)

Steps to Reproduce

1. Create a new report as follows:

Source Type: Table Table: Incident Type: Multi-level pivot table Select Columns: Active - Incident table Select Rows: Assigned to

2. Open the filter conditions and add the following filter (To ensure 0 rows returned): Created | after | Today

3. Run the report.

> Expected behavior: Message appears on screen: "Cannot generate the report. No matching records"

> Actual behavior: Message appears on screen: "Cannot generate the report. No matching records" Error is generated in syslog table : No matching records: com.glideapp.report.charting_v2.exceptions.ChartDataGenException: No matching records: com.glideapp.report.charting_v2.datagen.pivot.PivotDataGenerator.validatePivotData(PivotDataGenerator.java:124) com.glideapp.report.charting_v2.datagen.pivot.PivotDataGenerator.generateJSONResponse(PivotDataGenerator.java:69) com.glideapp.report.charting_v2.datagen.pivot.PivotDataGenerator.generate(PivotDataGenerator.java:41) com.glide.processors.report.run.PivotRunProcessor.processRequest(PivotRunProcessor.java:35) com.glide.processors.report.run.ReportRunProcessor.process(ReportRunProcessor.java:45) com.glide.processors.XMLHttpProcessor.processJavaAJAX(XMLHttpProcessor.java:168) com.glide.processors.XMLHttpProcessor.process(XMLHttpProcessor.java:121) com.glide.processors.AProcessor.runProcessor(AProcessor.java:531) com.glide.processors.AProcessor.processTransaction(AProcessor.java:229) com.glide.processors.ProcessorRegistry.process0(ProcessorRegistry.java:188) com.glide.processors.ProcessorRegistry.process(ProcessorRegistry.java:177) com.glide.ui.GlideServletTransaction.process(GlideServletTransaction.java:31) com.glide.sys.Transaction.run(Transaction.java:2147) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748)

Workaround After carefully considering the severity and frequency of the issue, and risk of attempting a fix, it has been decided not to address this issue. We do not make this decision lightly, and we apologize for any inconvenience. If you have any questions regarding this problem, contact ServiceNow Customer Support.