Sorry for the late response to all your comments on my post. The workaround I used was to build a brand new BIRT report, much simpler that does the minimum.
However, the issue with the original report still persist and my client hopes it will someday be fix.
As the time flies, I completely forgot it and this morning, I saw Dusko's post and that reminds me that I have to correct this!
As we speak, we are planning our migration to MAS. However, I still want to correct the report to make it work in 7.6.1.3 prior to the migration.
The simpliest way for me is Andrey's approach. The BIRT report has 20 DataSets. I made the changes this morning in each DataSet and sadly, the error persist.
Our 7.6.1.3 instance runs on Java 8.0.7.20.
Have a nice day!
Danny
------------------------------
Danny Cordeau
Universite de Sherbrooke
------------------------------
Original Message:
Sent: 03-23-2026 11:47
From: Dusko Delic
Subject: Since 7.6.1.3, I have issues with a Birt Report
Danny, this is a known pain point with the 7.6.1.3 upgrade. As Steven mentioned, it's DT392958 - the BIRT scripted data source tries to pull mxe.report.birt.escapeEquals and mxe.report.birt.removeEmoji from the context map, gets null, and throws the NPE.
Two practical workarounds if you can't wait for an LA fix:
- Andrey's approach - add this to your DataSet open script before the SQL runs:
context = mxReportScriptContext;
context.getMXReportContext().put("mxe.report.birt.removeEmoji", false); - Steven's suggestion - grab the patched
MXReportDataSetImpl.class from a MAS instance (if you have access to one) and use it in your BIRT Designer. Lower risk since it only affects preview, not the Maximo server.
For what it's worth, this kind of cross-version compatibility issue is exactly why a lot of 7.6 shops are looking at alternative ways to get reporting data out of Maximo without depending on BIRT at all - whether that's direct SQL, custom APIs, or newer AI-based query tools.
Hope one of these gets you unblocked!
------------------------------
Dusko Delic
Code Development Limited
Original Message:
Sent: 04-04-2025 10:48
From: Danny Cordeau
Subject: Since 7.6.1.3, I have issues with a Birt Report
Good morning,
Since migrating to 7.6.1.3, we've been having issues running a particular Birt report. In the designer (4.8 version), when I try to view my report in my browser and enter my wonum, I get an error message stating that my fetch method on my main DataSet returns a null value when it should return a Boolean value. This report runs without issue in Birt 4.3.1 but not in version 4.8. Therefore, I'm unable to get it to work in Maximo 7.6.1.3. Could you please provide some possible solutions or how to debug my report to make it work again?
Thanks!
Danny
#Administration
#Reporting
------------------------------
Danny Cordeau
Universite de Sherbrooke
------------------------------