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

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!

0 Frédéric Rinaldi 12 days ago

Hi,

with a 500 Internal Server Error, you should see in your php/apache log more details that will guide you to understand the issue.

Can you provide us with the error log content so we could help you ?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Rodrigo Manara 11 days ago

Sometimes error 500 is related on how your Report logic is build, I guess if you check sugar logs you should be able to see it.

Common error 500 = this is incompatible with sql_mode=only_full_group_by

Rodrigo Manara

Sr. Developer
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Ledjon Hoxha 11 days ago

Frédéric Rinaldi , Rodrigo Manara, 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?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Frédéric Rinaldi 11 days ago in reply to Ledjon Hoxha

hi Ledjon Hoxha ,

inside SugarCloud, you can ask the php error log from the Suagr Insight menu.

You can also create a case on the Sugar Support Portal.

I am also surprise because Sugar must avoid Large report to be displayed : https://support.sugarcrm.com/documentation/sugar_versions/14.0/ent/application_guide/reports/#null
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Rafael Fernandes 2 days ago

Hi Ledjon Hoxha ,

I can confirm this is indeed a bug and will be fixed in the next release.

Thank you for reporting it to us and improving Sugar.

rafa

Rafael Fernandes

Staff Developer Advocate | SugarCRM
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel