Thread Details
  • State Suggested Answer
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 372 subscribers
  • Views 138 views
  • Users 0 members are here
Forum Actions
Related

GET /Reports/:record/records is not paging and results in 500 Internal Server Error.

Ledjon Hoxha

Hi everyone!

I’m working with the SugarCRM API (v11_25) and running into an issue when retrieving report data using the `/Reports/:record/records` endpoint.

According to the documentation (doc reference: /Reports/:record/records GET - Sugar Support) , this endpoint supports the `max_num` and `offset` parameters for pagination. However, these parameters appear to be ignored. Regardless of the values I pass.

For example:

REQUEST
>GET https://{instanceurl}/rest/v11_25/Reports/{recordId}/records?max_num=20

RESPONSE

Contains all report records, with next_offset = -1.


In this case the report I am requesting has only 161 records and they are all returned despite max_num being set to 20.

While small reports are successfully returned, once a report contains a very large number of records, the API still attempts to return the entire dataset in a single response. This results in a very large payload, which I believe is causing the 500 Internal Server Error.

At the moment, this prevents us from loading large reports through the API. 

Is this a known issue? Is there any workaround or configuration change that allows paging results to avoid the large payload and the `500 Internal Server Error`? 

Please let me know if there is a known fix to this or if you have any questions!

Thank you in Advance!

Parents
  • 0

      , , Thank you both for your responses. 
    I am using a SugarCloud instance and I cannot increase the logging level. 

    I checked the logs, and I found this `Tue Nov 25 11:15:53 2025 [24302][1][FATAL] An exception occurred while executing a query: Prepared statement contains too many placeholders; Query: ........  `

    But this only happens only if the report is large in data (up to 60-70k records in my case). 
    For the same report I changed the date range for which I was asking for information and significantly lowered the reports records (to under 10k records) and was able to get the data in this case. It seems like if we are able to paginate, we would be able to get all the needed information. But paging is not working, the server is always trying to return all the data in one response and totally ignores `max_num` parameter. Any idea if there is some other way to paginate?  

Reply
  • 0

      , , Thank you both for your responses. 
    I am using a SugarCloud instance and I cannot increase the logging level. 

    I checked the logs, and I found this `Tue Nov 25 11:15:53 2025 [24302][1][FATAL] An exception occurred while executing a query: Prepared statement contains too many placeholders; Query: ........  `

    But this only happens only if the report is large in data (up to 60-70k records in my case). 
    For the same report I changed the date range for which I was asking for information and significantly lowered the reports records (to under 10k records) and was able to get the data in this case. It seems like if we are able to paginate, we would be able to get all the needed information. But paging is not working, the server is always trying to return all the data in one response and totally ignores `max_num` parameter. Any idea if there is some other way to paginate?  

Children