Timeline for How to make triggers not fire when we use API tools like Data Loader?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 5, 2015 at 22:52 | comment | added | thereistonsonenotany | Kaw is right that you should not be skipping code that sets values or updates related objects unless you are being very careful. When I have skipped triggers in the past, it's been because I had some older data that did not conform to the current business rules, and just needed to be loaded for the purposes of completeness. This shouldn't be something you are doing a majority of the time. If it is, I would suggest carving out exceptions in the trigger logic itself e.g. don't create a related record/update a field if XX condition is not met. | |
| Mar 5, 2015 at 22:32 | comment | added | Kaw Sumit | Its a choice you need to make between time and functionality. I would suggest strongly not to skip triggers as it can lead to data inconsitency at various levels and once data has gone bad it cannot be updated later. I suggest you set a size which is not very less nor very high. salesforce provides an option of bulk API for faster processing use that, but dont skip triggers. | |
| Mar 5, 2015 at 22:30 | comment | added | sfdcIndicat0r | Hi Kaw - my code is bulkified, and I understand that I can configure the API tools to have them load one record at a time... I have asked other people in my org who uses Data Loader to configure it that way, but they said loading record one by one is way too slow. | |
| Mar 5, 2015 at 22:25 | history | answered | Kaw Sumit | CC BY-SA 3.0 |