To Do: Browse Tasks | Gantt Chart | Reporting | Admin

Submitted By:
Peter Morelli (pmorelli)
Category:
None
Percent Complete:
100%
Priority:
4
Start Date:
2006-02-24
End Date:
2006-03-09
Task Summary:
transparently deal with batch inserts greater than the limit
Original Comment:
currently we limit to 200. have asf automatically chunk inserts greater than 200.

forum post:
the modified rforce we use does do batch inserts (if you see a case where it doesn't, please file a bug!), but it doesn't transparently deal with the 200 batch size limit. So, it'll happily add more than 200 elements, and you'll get a failure. It's a good suggestion, and I'll file a bug to deal with this transparently (multiple calls in batch sizes of 200).

ASF is subject to rate limiting, just like any other API integration. If you're an EE org, you won't be blocked, however, we will start calling you if you do over 1MM a day. ;o) DE orgs are limited to 5000 api requests in a 24 hour period. DE orgs are also limited to 5 concurrent requests.

In general, we try to follow API best practices: http 1.1, gzip request and responses, batch, MRU disabled (at least for the default 7.0 endpoint) There are some additional tips for things we can't control, like sharing rules, in this excellent post from Lexi, the creator of the Dataloader.

http://blog.sforce.com/sforce/2006/02/data_loading_ma.html

Hope that helps.

--pete
Assigned To
user_name
dchasman
Dependent On Task
summary
Hours:
8
Status:
Closed

No Tasks are Dependent on This Task

No Related Tracker Items Have Been Added

No Comments Have Been Added

Task Change History

Field Old Value Date By
status_id1 2006-02-28 01:36 dchasman
start_date2006-02-24 2006-02-28 01:36 dchasman
end_date2006-03-09 2006-02-28 01:36 dchasman
dependent_on_id100 2006-02-28 01:36 dchasman
percent_complete0 2006-02-28 01:35 dchasman
dependent_on_id100 2006-02-28 01:35 dchasman
start_date2006-02-24 2006-02-28 01:35 dchasman
end_date2006-03-09 2006-02-28 01:35 dchasman
assigned_to_id5023 2006-02-28 01:35 dchasman