Related content:

Discussion Error occurred during import of SmarDisputeBase.jar. Question Error occured during hotfix import Question ORA-24345: A Truncation or null fetch error occurred in report definition Question Error during report def execution Question ORA-24345: A Truncation or null fetch error occurred in report definition while using Pega OOTB property in reporting Question error occurred during fetching instance configuration Question error occured during resolving the report definition - InvalidReferenceException .< Property_name > Unexposed properties cannot be selected for classes mapped to external tables Question ORA-24345: A Truncation or null fetch error occurred while fetching the report. Question An error occured on executing the query for the report definition Question Report definition error - caught exception during autocommit check
Contact a Moderator

Question

8
Replies
2413
Views
DPSSingh Member since 2009 53 posts
JPMC
Posted: 4 years ago
Last activity: 3 years 8 months ago
Closed
Solved

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.

Low-Code App Development Upgrades System Administration
Close popover
Moderation Team has archived post
Posted: 4 years ago

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?

Posted: 4 years ago

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.

Posted: 4 years ago

Please raise an SR for 7.1.9 with details and support can do the necessary follow up.

Posted: 4 years ago

Thanks Dhirendra! I've updated your thread!

Accepted Solution
Posted: 4 years ago

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.

Posted: 3 years ago

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.
Share this page LinkedIn
Copied!