[SalesForce] Why use ESAPI for encoding

The Mass Update And Mass Edit From List View app should be able to get you where you want to be.

It is correct that you will want a number field on the PaperAuthor object in order for you to have a field to sort the records.

The one-to-many model which the tool's examples describe will work in this scenario. The 'one' in this case is the Paper and the 'many' is the PaperAuthor, the Author object is really irrelevant to the problem which you're solving for.

You might consider putting a few formula fields on the PaperAuthor object to retrieve any relevant information from the Author record to display within the related list. This could help your users better know which Authors they are dealing with in the list.

Although the error says to commit or rollback before making the callout, and you are doing the rollback, SFDC seems to ignore this when the callout is executed - this could be because of batch context but I didn't have time to explore that.

OK, here are some ways to work around the error

Option 1 You will need two batchable classes and one custom object Deferred_Callouts__c.

• Batchable class 1 - use the Database.savepoint - rollback sequence to get the rendered template. Then save the email recipient id and body in the custom object Deferred_Callouts__c. insert these all in the finish() method - which then invokes Batchable class 2
• Batchable class 2 - Read all the Deferred_Callouts__c and construct the callouts

Considerations:

• You are limited in the # of callouts so you'll need to be careful of limits in the batch size passed as scope.

Option 2 You will need one batchable class, one custom object Deferred_Callouts__c, and a workflow

• Batchable class 1 - use the Database.savepoint - rollback sequence to get the rendered template. Then save the email recipient id and body in the custom object Deferred_Callouts__c. insert these all in the finish() method

• Use a workflow that executes upon Create of Deferred_Callouts__c that uses an outbound message action to send via SOAP to the end point (assumes endpoint supports SOAP)

Option 3

You will need to use the Dan Appleman Async Framework as presented at Dreamforce that allows for unlimited async operations. This is well worth understanding.

This is my personal favorite as the solution is extensible to all your async needs over time

Option 4 Do what Alexander suggested and use the simulated merge field approach here . If you have formulas in the template, this will be difficult. This avoids altogether the DML operations.