A few clients w/ high traffic web forms (Dogwood, TCC) have run into the problem where multiple campaign member inserts for the same campaign run into record locking issues on the campaign, due to the standard rollups (we think). See http://boards.developerforce.com/t5/Apex-Code-Development/UNABLE-TO-LOCK-ROW-on-CampaignMember-junction-object/m-p/388025
Fix: include optional batch class like Nick has to create the CM's asynchronously. Devise web forms to write reference to campaign to contact rec, rather than inserting the CM directly (or use apex webservice and do the CM insert in try/catch. Batch does cleanup.
This could also be an optional add-on to GWBase, either managed or unmanaged. But would be good not to have to deploy it from scratch for each client that needs it.
A few clients w/ high traffic web forms (Dogwood, TCC) have run into the problem where multiple campaign member inserts for the same campaign run into record locking issues on the campaign, due to the standard rollups (we think). See http://boards.developerforce.com/t5/Apex-Code-Development/UNABLE-TO-LOCK-ROW-on-CampaignMember-junction-object/m-p/388025
Fix: include optional batch class like Nick has to create the CM's asynchronously. Devise web forms to write reference to campaign to contact rec, rather than inserting the CM directly (or use apex webservice and do the CM insert in try/catch. Batch does cleanup.
This could also be an optional add-on to GWBase, either managed or unmanaged. But would be good not to have to deploy it from scratch for each client that needs it.