{"id":6274,"date":"2017-09-22T22:16:24","date_gmt":"2017-09-22T22:16:24","guid":{"rendered":"http:\/\/www.jitendrazaa.com\/blog\/?p=6274"},"modified":"2022-07-18T11:18:40","modified_gmt":"2022-07-18T15:18:40","slug":"enterprise-territory-management-auto-account-assignment-using-apex","status":"publish","type":"post","link":"https:\/\/www.jitendrazaa.com\/blog\/salesforce\/enterprise-territory-management-auto-account-assignment-using-apex\/","title":{"rendered":"Enterprise Territory Management – Auto Account Assignment using Apex"},"content":{"rendered":"

Using\u00a0Territory Management<\/strong><\/a>\u00a0in Salesforce,\u00a0<\/strong>we can auto assign territories to Account and give access to users working in common region. When we create Account, Territory Assignment rules automatically runs. On Account update we have a checkbox on page layout allowing to run Territory rules. However,\u00a0Lightning experience\u00a0<\/strong>does not support Territory Assignment checkbox yet on page layouts.<\/p>\n

Unfortunately, Apex also does not support Account Assignment using Territory rules. Only way left is to use Salesforce API<\/a>. Question is, just to run\u00a0Enterprise Territory Management\u00a0<\/strong>rules, should we import WSDL and convert it to respective Apex classes ? There must be some better way.<\/p>\n

Then I remembered this article<\/a> which I wrote around 5 years back. Instead of importing WSDL into Salesforce and converting it to Apex classes, we can take help of SOAP UI<\/strong><\/a> to find the request format and using\u00a0HttpRequest,\u00a0<\/strong>we can simulate request.<\/p>\n

Below animation shows code in action :<\/p>\n

\"Demo
Demo of Enterprise Territory Management Assignment rules using Apex in Salesforce<\/figcaption><\/figure>\n

How to get Salesforce SessionId in future Method, Batch Apex or any other Async Apex<\/h3>\n

Only challenge in invoking API from Queueable Interface is getting sessionId.<\/p>\n

You might think that we can pass session Id directly to Queueable class\/ It works in classic mode however I saw internal server error if user in Lightning experience mode. It works fine from anonymous Apex, but then fails if execution starts from Account Trigger.<\/p>\n

For solution, Credit goes to @mattandneil<\/a> for this Solution on twitter TIL series. We need to create a below Visualforce page to get sessionId and then use in our code. I tested this and works in both classic and Lightning.<\/p>\n