New answers tagged

1

When I look at the results of the following coding, I would still use if (!list.isEmpty()) { DML list; } List<Account> accs = new List<Account>(); System.debug(Limits.getCpuTime()); // 1 // loop 1 for (Integer i = 0; i < 100000; i++) { insert accs; } System.debug(Limits.getCpuTime()); // 2039 // loop 2 for (Integer i = 0; i < 100000; i++...


0

API call limit is only for inbound calls. Outbound calls are governed by the per transaction and maximum timeout limits. Reference: Salesforce Developer Limits Quick Reference


2

It looks like an issue with the Trigger Code, it can be a code quality issue (SOQL Query in a loop, excessive use of SOQL, etc. ). I think that you can still load your data but a code review should be done to bulkify the triggers code. If the Business logic implemented in the trigger (on that object you're loading) can be bypassed, you can deactivate the ...


Top 50 recent answers are included