{"id":745,"date":"2014-10-30T09:33:01","date_gmt":"2014-10-30T09:33:01","guid":{"rendered":"http:\/\/www.greytrix.com\/blogs\/salesforce\/?p=745"},"modified":"2025-05-30T05:04:15","modified_gmt":"2025-05-30T05:04:15","slug":"invoke-future-methods-through-apex-trigger-for-web-service-callout","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/salesforce\/2014\/10\/30\/invoke-future-methods-through-apex-trigger-for-web-service-callout\/","title":{"rendered":"Invoke Future Methods through Apex Trigger for web service callout"},"content":{"rendered":"\n

While developing applications in force.com<\/a>, sometimes we need to consume external web service in apex trigger. But, callouts cannot be made from apex triggers as that restricts database transaction until the callout is completed and the time limit for this is up to 120 seconds. You can find other callout limits here<\/a>.<\/p>\n\n\n\n

The only way to execute a callout from a trigger is to run it asynchronously and this can be achieved by executing a method with the @future<\/strong> method. Future methods execute asynchronously i.e. one does not need to wait for a response. The thing to keep in mind is, a future method can have native calls, as well as, they can make a call out to an external web service and hence, in order to enable the future method to allow callouts, an extra parameter \u201cCallout=true<\/strong>\u201d needs to be passed.<\/p>\n\n\n\n

For example: –<\/strong><\/p>\n\n\n\n

You have a requirement to call a web service after updating the contact record. Web service callout method (in this example callWebService(Contact cnt) ) is in the Util class which is getting consumed in apex after update trigger.<\/p>\n\n\n\n

Apex trigger\u2019s code:<\/strong><\/p>\n\n\n

\n
\"Param<\/a><\/figure><\/div>\n\n\n


Apex class code:<\/strong><\/p>\n\n\n

\n
\"changed<\/a><\/figure><\/div>\n\n\n


When the above trigger is fired it will throw an error as \u201cCallout from triggers are currently not supported.<\/strong>\u201d<\/p>\n\n\n\n

To resolve this you need to make a small change in your Apex code. Just add<\/strong> @future annotation before the apex method as shown below –
<\/a><\/p>\n\n\n

\n
\"Future<\/a><\/figure><\/div>\n\n\n

About Us<\/strong><\/span>
Greytrix<\/a> as a Salesforce Product development partner offers a wide variety of integration products and services to the end users as well as to the Partners across the globe. We offers Consultation, Configuration, Training and support services in out-of-the-box functionality as well as customizations to incorporate custom business rules and functionalities that requires apex code incorporation into the Salesforce platform.<\/p>\n\n\n\n

Greytrix<\/a> has some unique solutions for Cloud CRM such as Salesforce integration with Sage Enterprise Management (Sage X3<\/a>), Sage Intacct, Sage 100 <\/a>and Sage 300 (Sage Accpac)<\/a>. We also offer best-in-class Cloud CRM Salesforce customization and development services<\/a> along with services such as Salesforce Data Migration<\/a>, Integrated App development<\/a>, Custom App development<\/a> and Technical Support<\/a> to business partners and end users.<\/p>\n\n\n\n

Greytrix GUMU™ integration for Sage ERP \u2013 Salesforce is a 5-star app listed on Salesforce AppExchange<\/a>.<\/p>\n\n\n\n

For more information, please contact us at salesforce@greytrix.com<\/a>. We will be glad to assist you.<\/p>\n","protected":false},"excerpt":{"rendered":"

While developing applications in force.com, sometimes we need to consume external web service in apex trigger. But, callouts cannot be made from apex triggers as that restricts database transaction until the callout is completed and the time limit for this is up to 120 seconds. You can find other callout limits here. The only way\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[20,21,139,192,416,502,539],"class_list":["post-745","post","type-post","status-publish","format-standard","hentry","category-gumu-salesforce","tag-apex-references-in-salesforce","tag-apex-trigger","tag-future-method","tag-invoke-future-methods","tag-salesforce-technical","tag-trigger-in-salesforce","tag-webservice-callout"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/posts\/745","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/comments?post=745"}],"version-history":[{"count":4,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/posts\/745\/revisions"}],"predecessor-version":[{"id":10847,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/posts\/745\/revisions\/10847"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/media?parent=745"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/categories?post=745"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/salesforce\/wp-json\/wp\/v2\/tags?post=745"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}