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.
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?
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: 6 years ago
Posted: 30 Jan 2017 16:42 EST
Pranav Sikka (PranavS6)
Accenture Federal Services
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.