Description
When attempting to create reports, if adding a field from a variable, the report will default to only show the first record retrieved from the query.
The instance log will contain the error: SEVERE *** ERROR *** null:301:2353: <g2:list_item_style> java.lang.NullPointerException.
Further, if using group by, it will recognize other records are available but not show them.
Steps to Reproduce
- Edit a catalog item such as Submit an IT request.
- Add these variables: Incident Number (reference type to incident), Incident description (multi-line text).
- Submit the catalog item a few times to generate some records in sc_req_item.
- Set the system property glide.ui.optimize.lists to false.
- Create a report on the requested item table (sc_req_item), andadd a filter for Item = <catalog item created or Submit an IT Request>.
- Run the report. Observe only one record is displayed, even though there are many records.
- Remove the filter and run the report again. Observe all records are shown.
Workaround
This issue is fixed in all currently supported versions. Please review the Fixed In section to determine the latest available patch your instance can be upgraded to.
The recommended workaround is to have both properties listed below set to their default value of true:
glide.ui.optimize.lists=true
glide.ui.list.optimize=true
Also see the workarounds to the behaviour described in PRB573139/KB0529493 - In list view ACLs on referenced dot-walked records are evaluated only against the specific displayed derived fields .
Dot-walked fields in a list report may not load properly if the referenced property glide.ui.list.optimize is set to true as recommended.
Related Problem: PRB1162821
