Category: Salesforce

Salesforce – Mock callouts in Apex

May 11th, 2021
Reading Time: < 1 minute
To mock callouts in Apex, you can create a class that implements the HttpCalloutMock interface. This allows you to define the desired response for an HTTP request made during testing. Here’s an example of how you can create a mock class for callouts:
```
   private class RestMock implements HttpCalloutMock {

        public HTTPResponse respond(HTTPRequest req) {
            HTTPResponse res = new HTTPResponse();
            res.setHeader('Content-Type', 'text/json');
            res.setBody('{}');
            res.setStatusCode(200);
            return res;
        }
    }
  
```
In your test method, you can use the Test.setMock method to associate your mock class with the HTTP callout. Here’s an example of how to use the mock in a test:
```
@isTest static void myTest() {
        Test.setMock(HttpCalloutMock.class, new RestMock());
        
        // Some stuff...

        Test.startTest();
        // Test-related stuff...
        Test.stopTest();
        
    }
```
By using this approach, you can simulate different scenarios and responses to ensure your code handles callouts correctly during testing.

Migrate $User, $Profile, $Label and $Api to Lightning Components

May 11th, 2021

Reading Time: < 1 minute

We can’t use $User, $Profile, $Label, and $Api in Lightning. We need to implement a server-side solution.

Migrating your code to Lightning Components can be a daunting task. Fortunately, with a few simple steps, you can migrate your $User, $Profile, $Label and $Api components to Lightning Components.

The original JS button

alert($User.Email)

Create a Lightning component

Create a Lightning component: JSMUserInfo.cmp

<aura:component implements="force:lightningQuickAction" controller="JSMUserInfoService" >
  <aura:attribute name="user" type="JSMUserInfo" />
  <aura:handler name="init" value="{!this}" action="{!c.doInit}"/>
 
  Id: {!v.user.Id}
  <br/>
  First name: {!v.user.FirstName}
  <br/>
  Last name: {!v.user.LastName}
  <br/>
  Email: {!v.user.Email}
 
</aura:component>

Create a js controller

JSMUserInfo.js


({
  doInit : function(component, event, helper) {
    var action = component.get("c.getUserInfo");
    action.setCallback(this, function(response) {
      var state = response.getState();
      if(state == "SUCCESS" && component.isValid()){
        console.log("success") ;
        var result = response.getReturnValue();
        console.log(result);
        console.log(result.FirstName);
        component.set("v.user", result);
 
   }else{
     console.error("fail:" + response.getError()[0].message); 
    }
   });
  $A.enqueueAction(action);
}
})

Create an Apex class

A wrapper class containing the user info we need


public class JSMUserInfo{
  @AuraEnabled
  public String Id {get;set;}
  @AuraEnabled
  public String FirstName {get;set;}
  @AuraEnabled
  public String LastName {get;set;}
  @AuraEnabled
  public String Email {get;set;}
}

Create a service Apex class

The server-side controller that exposes the User’s info


public class JSMUserInfoService {
 
@AuraEnabled
public static JSMUserInfo getUserInfo(){
  try{
    JSMUserInfo info = new JSMUserInfo();
    info.Id = Userinfo.getUserId();
    info.FirstName = Userinfo.getFirstName();
    info.LastName = Userinfo.getLastName();
    info.Email = Userinfo.getUserEmail();
    return info;
  }catch(Exception e){
     throw new AuraHandledException(e.getMessage()); 
  }
 
  } 
}

We can use a similar approach for $Api or any other global variable

$Profile


@AuraEnabled
public static Profile getProfileInfo(){
  try{
    String profileId = UserInfo.getProfileId();
    Profile profile = [SELECT Id, Name FROM Profile WHERE Id =:profileId];
    return profile;
  }catch(Exception e){
    throw new AuraHandledException(e.getMessage()); 
  }
}

$Site


@AuraEnabled
public static JSMSiteInfo getSiteInfo(){
  try{
    JSMSiteInfo info = new JSMSiteInfo();
    info.Prefix = Site.getPathPrefix();
    info.Domain = Site.getDomain();
    info.Name = Site.getName();
    return info;
  }catch(Exception e){
    throw new AuraHandledException(e.getMessage()); 
  }
}

Migrate sforce.connection.query to Lightning equivalent

January 14th, 2018

Reading Time: 2 minutes

Are you looking for a way to migrate your existing Salesforce Apex code with sforce.connection.query to its Lightning equivalent? You’ve come to the right place!

The sforce.connection.query class is used to execute SOQL queries in Salesforce JavaScript buttons.

As you probably know, JavaScript buttons are not supported in Lightning Experience (LEX). In particular, you can’t use REQUIRESCRIPT.

In this post, the idea is to show how to migrate a particular JavaScript button that uses sforce.connection.query sentence.

Suppose our JavaScript button is like this:

{!REQUIRESCRIPT("/soap/ajax/37.0/connection.js")} 
{!REQUIRESCRIPT("/soap/ajax/37.0/apex.js")} 
var query ="SELECT Id, Name FROM Account LIMIT 10";
var queryRecords= sforce.connection.query(query);
var records = queryRecords.getArray("records"); 
//Do something with the records...

A Lightning equivalent solution requires several steps. I assume that you have some knowledge about Lightning Components development as well as Apex development.

Well, let’s go!

Create a Lightning component called MyQueryResult and Its JavaScript controller

MyQueryResult.cmp

<aura:component controller="MyQueryResultService" >
 <aura:attribute name="queryResult" type="SObject[]" />
 <aura:handler name="init" value="{!this}" action="{!c.doInit}"/>
 
    <!-- It just displays the results. Modify It depending on your needs -->
    <aura:iteration items="{! v.queryResult}" var="item">
        {!item.Id} - {!item.Name}<br/>
     </aura:iteration>
</aura:component>

MyQueryResult.js

({
    doInit : function(component, event, helper) {
        var myQuery = 'SELECT Id, Name FROM Account LIMIT 10';
        var action = component.get("c.executeQuery");
        action.setParams({
            "theQuery": myQuery
        });
        action.setCallback(this, function(response) {
            var state = response.getState();
            if(state == "SUCCESS" && component.isValid()){
                console.log("success") ;
                var queryResult = response.getReturnValue();
                console.log(queryResult);
                component.set("v.queryResult", queryResult);
            }else{
                console.error("fail:" + response.getError()[0].message); 
            }
        });
        $A.enqueueAction(action);
    }
})

We will need also a service (an Apex class) to execute our query

MyQueryResultService

public class MyQueryResultService {
    @AuraEnabled
    public static List<sObject> executeQuery(String theQuery){
        try{
            String query = String.escapeSingleQuotes(theQuery);
            return Database.query(query);
        }catch(Exception e){
            throw new AuraHandledException('Error doing the query: '+theQuery+' Error: '+e.getMessage());
        }
    }
}

After that, we need a quick action pointing to our component.

The last step is to add our quick action to the layouts we need

Read more about this at Lightning Alternatives to JavaScript Buttons