Forums - Thread Details
  • State Not Answered
  • Replies 5 replies
  • Subscribers 318 subscribers
  • Views 1662 views
  • Users 0 members are here
Forum Actions
Related

HTTP 500 server internal error

Vinicius Sant'Anna

Hi, I'm customizing a dashlet, but when I try to receive data from SugarCRM on demand using filter API. But, when setting max num filter to -1 (no data limit), I get 500 (Internal Server Error).

I'm trying to bring over 8600 records. If I put 8000 instead of -1 right there, I can bring the records and recieve 200. But, I can't have this kind of limit on my request because my aplication needs this records.

What should I do?

Parents
  • 0

    Why are you using a dashlet if you need that amount of data? What is the purpose of having all these records in the frontend? Is it to draw some sort of graph? Show a report like thing? The best approach would be to have a recursive javascript function that retrieves the data using the offset property of the api.

    First take 1000, take 1000 again until you get nothing new and then stop. For the 500 error. I think you ran into a bug there but of course if you are on cloud support can help you out with that. If you really really need that amount of data in the frontend you could ofcourse always overwrite the default behaviour of the api but I wouldn't do that just to be sure you don't kill the server when 10 people are opening the dashlet.

Reply
  • 0

    Why are you using a dashlet if you need that amount of data? What is the purpose of having all these records in the frontend? Is it to draw some sort of graph? Show a report like thing? The best approach would be to have a recursive javascript function that retrieves the data using the offset property of the api.

    First take 1000, take 1000 again until you get nothing new and then stop. For the 500 error. I think you ran into a bug there but of course if you are on cloud support can help you out with that. If you really really need that amount of data in the frontend you could ofcourse always overwrite the default behaviour of the api but I wouldn't do that just to be sure you don't kill the server when 10 people are opening the dashlet.

Children
No Data