An error occured during resolving the report definition - null
Hi All - I am getting "An error occured during resolving the report definition - null" when launching the user portal in v7.1.9. I found the article on PDN(https://pdn.pega.com/support-articles/report-definitions-cause-null-pointer-exceptions) and it seems this issue existed in v7.1.7 and there was a HFix provided which I assume should already be resolved in v7.1.9. But it seems not fixed in v7.1.9. So do I need to create SR to get the corresponding HFix for 7.1.9?
I have a SQL function defined for one of the column in my report definition as well as corresponding repeating grid column to enable the pyID sorting based on Number and not String. Which I believe should be causing this issue.
Pegasystems
IN
This issue was fixed in December 2015 in 7.1.7 by which time 7.1.9 was already available. Is your issue exactly same as the one described in the support article in PDN? The issue was fixed in 7.2 which was under development when this hotfix was created for 7.1.7 (7.1.9 was already available at that time). Would you consider upgrading to 7.2?
JPMC
US
Thanks Rajiv Nistala for your reply! We upgraded to v7.1.9 last month and we can not upgrade again to 7.2. Yes we are seeing exactly same exception in log.
I didn't see any unexpected behavior on UI. But I see this exception in log file so wondering if we it would cause any issue in 7.1.9 and if a HFix is required to be applied.
Pegasystems
IN
Please raise an SR for 7.1.9 with details and support can do the necessary follow up.
Hi Dhirendra,
Please let us know the SR number if you end up opening one.
Thanks,
Lochan
JPMC
US
Hi Lochana - I raised SR-A20064 ticket.
Pegasystems Inc.
US
Thanks Dhirendra! I've updated your thread!
Accepted Solution
Pegasystems Inc.
US
Upon reviewing the associated SR, the resolution was as follows for this customization issue:
pyUserAssignmentCountByUrgency report definition referenced in Sub-reports section of Data Access tab of pyOperatorsByWorkGroup report definition is customized. With OOTB pyUserAssignmentCountByUrgency the issue isn't seen.
Accenture Federal Services
US
We experienced the same issue in our system even though we had not changed the pyUserAssignmentCountByUrgency, but upon further investigation once we unchecked the "Report on descendant class instances" option on the Data Access tab of the sub report the error went away.