You need to sign in to do that
Don't have an account?
Luke@TWS
Max Callout Size
Getting the error:
System.CalloutException: IO Exception: Exceeded max size limit of 100000 with response size 100697
When calling my web service to bring in all of the cities/towns in Texas. Can't think of any way to make the list any smaller, having problems with a few other lists too. Anyone know of a work around for large amounts of data?
System.CalloutException: IO Exception: Exceeded max size limit of 100000 with response size 100697
When calling my web service to bring in all of the cities/towns in Texas. Can't think of any way to make the list any smaller, having problems with a few other lists too. Anyone know of a work around for large amounts of data?
If this is the case, is the callout going to have to extract Cities/Towns in Texas all the time a button or trigger is fired, or this is just a one off extract?
Luke@TWS wrote:
Getting the error:
System.CalloutException: IO Exception: Exceeded max size limit of 100000 with response size 100697
When calling my web service to bring in all of the cities/towns in Texas. Can't think of any way to make the list any smaller, having problems with a few other lists too. Anyone know of a work around for large amounts of data?
The only suggestion here will be to put LIMIT on the resultset. I think managing this effectively will stop you from exceeding at anytime.
For example 25 cities out on display at a time, anonther 22 is pulled while the previous, hidding when the control (\/) is clicked or highlighted.
I'd like to add another angle at this problem : you should never present users with that much options to select from all at once ... it's just too much to read for any human being anyhow.
So, the technical solution (splitting up the choices via paging / A-B-C-D-... lists or whatever) actually will also bring you better user interface design, not too mention a quicker responding interface !
I understand that this will mean making some modifications to the webservice that's being called (do you have access to the code behind it ?) but if you do, it's worth it.
The exact same reasoning is behind the max number of results you can get from google searches (usability) or the 'queryMore' priciple in the SFDC API (performance).
rgds,
David