Timeline for Workaround for the 10 web service callout limit in apex?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 5, 2012 at 21:16 | comment | added | Ryan Elkins | The messy part can come in to play when you have to handle responses and such. It's not so much messy as it can be a bit more work, but it should get it done. | |
| Dec 3, 2012 at 21:30 | comment | added | paul | Actually, I could see doing it with an intermediary service as much, much less messy. The other solutions, which are "correct" if you're doing it with Apex, are inherently messy, because Salesforce has designed it very poorly. With an intermediary service you could send out a single clean JSON string and have an intermediate server do the callouts in a clean way. I'm strongly considering this option now, as I have been fighting with some messy triggers + callouts + scheduled apex. | |
| Dec 2, 2012 at 4:45 | history | answered | Ryan Elkins | CC BY-SA 3.0 |