Has Jakarta placed a limit on the length of reports?

[HugoFirst]

I have several reports which contain a (relatively) large number of lines.

Recently, we upgraded to Jakarta Patch 4 and the reports come back with this error:

Now a "full report" wojudl have a total number of lines   of about 1,400.   So I am NOT bumping up on the 10,000 limit.

Has anyone else run into this?

[HugoFirst]

OK, I have enough data to make some sense of this.

----- start text of solution -----

The property glide.pdf.max_rows appears to control the number of lines allowed in a PDF file WITHIN LIMITS.

I tested by setting up a report of Linux servers which contains about 7,000 lines.

In the UI, I exported to PDF and ran into the 1,000 limit.

I then set the value of glide.pdf.max_rows to 2,000.

Again, I exported the report of Linux serves and ran into a limit of 2,000.

I was sure I had it!   But I was celebrating too soon!

I increased the value of glide.pdf.max_rows to 10,000 and exported the report and got this error:

Value of property 'glide.pdf.max_rows' must be less or equal than 5,000. Default max row number applied (1,000)

List truncated, max rows (1,000) exceeded

Looks like I need to use a different format for the report.    

----- end of text of solution -----

Michael,   since your answer led me to the solution, would you copy the pertinent text, add any additional thoughts that you'd like and reply to this message?   I want to give you the credit for the Correct Answer.

[Michael Ritchie · Accepted solution]

Steve,

Great research and I am sorry the documentation is wrong.   As mentioned in the Export limit properties product documentation the glide.pdf.max_rows system property will allow you to override the default setting of 1000.   This system property might not exist in your instance since the default is set in server side java by the ServiceNow developers but you can create your own system property with a name of glide.pdf.max_rows and type of Integer and set your own custom limit.   I have also confirmed that the server side code also sets a 5000 cap on the number of rows being exported.   So your custom system property can be between 1000 and 5000.

I have submitted feedback on the Product Documentation site stating that the default should be updated to reflect 1000 instead of 5000.   I also suggested noting that the max cannot exceed 5000 as well.

[HugoFirst]

Thanks for the feedback Michael. One other thought I have is that the value of the sys property could be checked at insert/update time and an error message returned at that time.   This may be cumbersome to implement,   but from a "user's perspective", this would be the best time to learn about the restriction.

[Michael Ritchie]

Completely agree but its definitely going to be a hard thing to implement.   The sys_property table is globally used and is basically a meta data table.   The defaults are happening in server side java and aren't directly linked other than querying the sys_property metadata table as things are happening.