I need to make 5 callouts serially. I have written 5 different apex classes. I want to chain these callouts from JavaScript controller using Async/Await or Promises. Had anyone worked on such scenario? Any problems or blockers? Each call is taking few seconds – so no timeout issue. I am logging each callout results, so I might get uncommitted work pending exception. Please suggest
Apex Callouts – Chaining from JavaScript Controller Using Async/Await or Promise
apexcalloutlightning-web-components
Related Solutions
This will require triggers and @future methods.
- For every object that you want to apply this to, you will need to create a trigger that covers the desired events (before/after, insert/update/delete, etc. . .). In other words this will require one trigger per object; there is no way to have a generic trigger.
- Create a helper method marked
@future(callout=true)that accepts the necessary parameters. This method will make the actual callouts. - Have your triggers call the helper method, when applicable.
Something to note:
You will likely run into governor limits. A transaction can only make 10 callouts so bulkifying this will be hard unless you can concatenate all of the updates into the body of one message. You could also circumvent this by only making the callout on single record transactions.
If you care calling this trigger on a Before Insert, there is not ID for the object before insert. Before update is okay, but this won't work on before insert. You will want to do after insert.
As pointed out by someone else, you are passing in a JSON string when the opptycall.post is expecting an ID type. You can pass in Trigger.new.[0].Id. Be careful here, your code is not bulkified so this won't behave as expected when you bulkupdate.
trigger OppUpdate on Opportunity (before insert, before update) {
for (Opportunity Opp : Trigger.new) {
if (Opp.StageName == 'ClosedWon') {
opptycall.post(JSON.serializePretty(Trigger.new));
system.debug(JSON.serializePretty(Trigger.new));
system.debug(JSON.serialize(trigger.new));
}
}
}
The other thing you want to be aware of is that your code with the @future call means that the opportunity is getting updated and saved and then the callout is happening after that record is saved. Your callout is updating the opportunity after it gets a response. Small detail here, but it might help you with troubleshooting. In your log files, you'll see a FutureHandler log that looks like this. That is where you'll see the debug information:
I'm using the developerconsole to view the logs.
Best Answer
There's no concern there. As long as each callout occurs before the DML in each Apex transaction, you'll be fine. For example, you can write your logic like this:
Each result will have been obtained from a separate transaction that each had their own separate governor limits.