Il se peut que vous deviez créer un enregistrement, puis le mettre à jour avec les informations fournies par un service Web. Cependant, un appel de service Web ne peut pas être effectué après une instruction DML dans la même transaction. Pour pouvoir exécuter l'action requise, la transaction doit être divisée en deux parties afin que la transaction DML soit terminée avant le déclenchement de l'appel du service Web.
Le premier processus insère l'enregistrement, et le deuxième exécute l'appel et peut mettre à jour le nouvel enregistrement inséré.
Page TestWsCallout<apex:page controller="TestWsCallout" tabstyle="Account"> <apex:form > <apex:actionFunction action="{!InsertRecord}" name="InsertRecord_JS" Rerender="statuses" status="Status1" oncomplete="CallWebService_JS();"/> <apex:actionFunction action="{!CallWebService}" name="CallWebService_JS" status="Status2" reRender="statuses, msg"/> <apex:outputPanel id="statuses"> <apex:actionStatus id="Status1" startText="...Inserting Record Into DB..." /> <apex:actionStatus id="Status2" startText="...Calling Web Service..." /> </apex:outputPanel> <apex:outputPanel id="msg"> <apex:pageMessages /> </apex:outputPanel> <div><input name="DoAction" class="btn" type="button" value="Do Action" onclick="InsertRecord_JS();return false;"/></div> </apex:form> </apex:page>public class TestWsCallout{ Account myAccount; public PageReference InsertRecord() { myAccount = new Account(name = 'Test Account'); insert myAccount; // Calling a Web Service here would throw an exception return null; } public PageReference CallWebService() { // Execute a call to a Web Service HttpRequest req = new HttpRequest(); req.setEndpoint('http://MyWebService12345678790.com?id=' + myAccount.Id); req.setMethod('GET'); HttpResponse response = new Http().send(req); // Simulate an update myAccount.Name = 'Test Account 2'; update myAccount; ApexPages.addMessage(new ApexPages.Message(ApexPages.Severity.CONFIRM, 'WebService Called on New Account: ' + myAccount.Name)); return null; } }
000385374

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.