Jump to content

Recommended Posts

Posted

I believe the setting api.xmlmc.queryExec.maxResultsAllowed under Home > System > Settings > Advanced in the Admin panel will allow you to change the default of 1000 rows

  • Like 1
Posted

@Catherine @Dan Munns I would advise being careful with changing this setting... I mean is ok to change it for a report for example but I would suggest to revert it back to the default value once the report is complete... This setting governs all the queries executed in an instance.. increase this and busy instances might find they experience performance issues because queries are now returning a much larger result set...

Posted

Hi @dan

You are right that in many areas like with standard searches, paging is put in place to manage performance issues caused by returning too many results.  Extending this value does give way to other reports causing performance issues, or possibly where APIs have been used to interact with Hornbill.   I would also suggest that upping this value on the api.xmlmc.queryExec.maxResultsAllowed setting should be done with caution and keep an eye open for performance issues and adjust the number accordingly.

James

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...