Retrieving aggregate results in Apex
|
In Apex, we use any aggregate function like the following way:-
First we have to declare a variable of list of Aggregate results, then the query, after that we have to use a loop and get that aggregate value.
LIST<AggregateResult> noOfEmployees = new LIST<AggregateResult> ();
noOfEmployees = [SELECT COUNT(id) noOfEmp FROM Employee__c WHERE salary__c > 25000 ]; for(AggregateResult sobj : noOfEmployees) { |
// Assuming you have the right partner/enterprise binding to make the call.DescribeGlobalResult describeGlobal = getBinding().describeGlobal();// Token Sobject Name, this can be any Custom Sobject name from your product.String TOKEN_SOBJECT_NAME = "Chatter_Location__c";// Pull the list of Sobjects from the Global DescribeDescribeGlobalSObjectResult[] describeResults = describeGlobal.getSobjects();int indexOfToken = -1;// This variable will have the namespace prefixString namespsacePrefix = null;for (DescribeGlobalSObjectResult descSobjResult : describeResults) { String sobjName = descSobjResult.getName(); if (sobjName != null) { // Try matching each Sobject Name with the TOKEN Sobject indexOfToken = sobjName.indexOf(TOKEN_SOBJECT_NAME); } if (indexOfToken != -1) { // If match is success, then substring the namespace prefix namespsacePrefix = sobjName.substring(0, indexOfToken); break; }}// Here we go, the final namespace prefix is here.!!!System.out.println(namespsacePrefix);Salesforce Example of a Post Install Script
The following sample post install script performs these actions on package install/upgrade. If the previous version is null, that is, the package is being installed for the first time, the script: Creates a new Account called “Newco” and verifies that it was created. Creates a new instance of the custom object Survey, called “Client Satisfaction Survey”. Sends an email message to the subscriber confirming installation of the package. If the previous version is 1.0, the script creates a new instance of Survey called “Upgrading from Version 1.0”. If the package is an upgrade, the script creates a new instance of Survey called “Sample Survey during Upgrade”. If the upgrade is being pushed, the script creates a new instance of Survey called “Sample Survey during Push”. You can test a post install script using the new testInstall method of the Test class. This method takes the following arguments. A class that implements the InstallHandler interface. A Version object that specifies the version number of the existing package. An optional Boolean value that is true if the installation is a push. The default is false. This sample shows how to test a post install script implemented in the PostInstallClass Apex class.
<apex:outputText value="{0,date,{!dateFormat}}">
<apex:param value="{!myDateTime}" />
</apex:outputText>
 |
public class DateFormattingController {
Datetime myDateTime = datetime.newInstance(2010, 12, 31, 23, 59, 59);
List<String> dateFormats = new List<String> {
'dd.MM.yy HH:mm:ss',
'MMM-dd-yyyy hh:mm a',
'EEEEE dd MMMMM yyyy G',
'E hh:mm:ss:SSS z',
'zzzzz (Z), \'Day of the year:\' D'
};
public DateTime getMyDateTime(){
return myDateTime;
}
public List<String> getDateFormats(){
return dateFormats;
}
}
<apex:page controller="DateFormattingController">
<apex:sectionHeader title="Date Formatting"/>
<apex:outputText value="Standard Output Format: {!myDateTime}"/>
<apex:pageBlock >
<apex:pageBlockTable value="{!dateFormats}" var="dateFormat">
<apex:column headerValue="Date Format" value="{!dateFormat}" width="50%"/>
<apex:column headerValue="Output" width="50%">
<apex:outputText value="{0,date,{!dateFormat}}">
<apex:param value="{!myDateTime}" />
</apex:outputText>
</apex:column>
</apex:pageBlockTable>
</apex:pageBlock>
</apex:page>
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 | public with sharing class testJavascript { public String requestStatus { get; set; } public String requestMore { get; set; } public Integer requestNumber { get; set; } public Integer requestCurrent { get; set; } public testJavascript () { requestStatus = ''; requestMore = ''; requestNumber = 10000; requestCurrent = 0; } public void doRequest () { if (requestCurrent <= requestNumber) { Http http = new Http(); for (Integer startPoint = requestCurrent; (requestCurrent <= requestNumber) && ((requestCurrent - startPoint) < 10); requestCurrent++) { HttpRequest req = new HttpRequest(); req.setMethod('GET'); HTTPResponse res = http.send(req); } requestStatus = requestCurrent + ' out of ' + requestNumber + ' processed'; } if (requestCurrent >= requestNumber) requestMore = 'false'; else requestMore = 'true'; }} |
1 |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 | <apex:page controller="testJavascript"><apex:form> <apex:outputpanel id="status"> Status: {!requestStatus} <script>requestContinue = {!requestMore};</script> </apex:outputpanel> <script> function requestMore() { if (requestContinue) doRequest(); } </script> <button onclick="if (doRequest()) return false; else return false;">Start</button> <apex:actionfunction action="{!doRequest}" name="doRequest" oncomplete="requestMore()" rerender="status"></apex:actionfunction></apex:form> |
In Salesforce, if you are trying to perform a Web Service Callout in a test class, you will get an error. For example:
- public String sendHttpRequest(String endpointUrl, String method, DOM.Document body) {
- ...
- HttpRequest req = new HttpRequest();
- req.setEndpoint(endpointUrl);
- req.setMethod(method);
- req.setBody(bodyStr);
- Http http = new Http();
- HttpResponse res = http.send(req);
- return res.getBody();
- }
When your test class runs untill line #9, it will stop the entire test process by throwing the following error:
System.TypeException: Methods defined as TestMethod do not support Web service callouts, test skipped callout
What if the overall test coverage is still under 75%? This will become a roadblock for your deployment. Below is the workaround you can consider:
- public String sendHttpRequest(String endpointUrl, String method, DOM.Document body, Boolean isTest) {
- ...
- HttpRequest req = new HttpRequest();
- req.setEndpoint(endpointUrl);
- req.setMethod(method);
- req.setBody(bodyStr);
- Http http = new Http();
- if(isTest) {
- HttpResponse res = http.send(req);
- return res.getBody()
- } else {
- // You can prepare some simulated data for your test class here
- return simulatedData;
- }
- }
By doing this, you can write different execution as below:
One of the most eagerly awaited Winter ’13 features, at least for developers, has been the ability to test Apex callouts. You can now test HTTP callouts by either
In this blog entry, I’ll focus on the static resource case. As an example, let’s assume that I’m retrieving JSON Account data from an external service. Here’s a simple callout that retrieves JSON account data, parses it, and returns the resulting list of accounts:
public class CalloutAccounts {
public static List<Account> getAccounts() {
HttpRequest req = new HttpRequest();
req.setEndpoint('http://api.example.com/accounts');
req.setMethod('GET');
Http h = new Http();
HttpResponse res = h.send(req);
String jsonData = res.getBody();
List<Account> accounts =
(List<Account>)JSON.deserialize(jsonData, List<Account>.class);
return accounts;
}
}
To test this callout, first, I’ll need to create a file, accounts.json, on my local machine containing test data:
[
{
"Name": "sForceTest1",
"Website": "http://www.sforcetest1.com"
},
{
"Name": "sForceTest2",
"Website": "http://www.sforcetest2.com"
},
{
"Name": "sForceTest3",
"Website": "http://www.sforcetest3.com"
}
]
Now I go to Setup | Develop | Static Resources, click New Static Resource, enter the name jsonAccounts, and select accounts.json for upload. Notice that Force.com set the MIME type based on the extension of the file I uploaded:
Now to define my test method. I’ll use StaticResourceCalloutMock to provide my Account test data when the getAccounts method executes its callout. First, I need to create an instance of StaticResourceCalloutMock and set the static resource, status code and content type header:
StaticResourceCalloutMock mock = new StaticResourceCalloutMock();
mock.setStaticResource('jsonAccounts');
mock.setStatusCode(200);
mock.setHeader('Content-Type', 'application/json');
Now I use Test.setMock to tell the Apex runtime I want to use this instance:
Test.setMock(HttpCalloutMock.class, mock);
Then I can test getAccounts:
Test.startTest(); List<Account> accounts = CalloutAccounts.getAccounts(); Test.stopTest();
And verify I received the expected data:
System.assertEquals(3, accounts.size());
System.assertEquals('sForceTest1', accounts[0].Name);
System.assertEquals('sForceTest2', accounts[1].Name);
System.assertEquals('sForceTest3', accounts[2].Name);
So, putting it all together into a test method in a test class:
@isTest
private class CalloutAccountsTest {
@isTest static void testCallout() {
StaticResourceCalloutMock mock = new StaticResourceCalloutMock();
mock.setStaticResource('jsonAccounts');
mock.setStatusCode(200);
mock.setHeader('Content-Type', 'application/json');
// Set the mock callout mode
Test.setMock(HttpCalloutMock.class, mock);
// Call the method that performs the callout
Test.startTest();
List accounts = CalloutAccounts.getAccounts();
Test.stopTest();
// Verify response received contains values returned by
// the mock response.
System.assertEquals(3, accounts.size());
System.assertEquals('sForceTest1', accounts[0].Name);
System.assertEquals('sForceTest2', accounts[1].Name);
System.assertEquals('sForceTest3', accounts[2].Name);
}
}
In more elaborate scenarios, I might execute several callouts in a single method. For example, let’s assume I have created a file of JSON-formatted Contact data and uploaded it as the static resource jsonContacts. The method I want to test will retrieve Account data as before, then retrieve the Contacts, and go on to do some processing of the combined Account and Contact data:
public class ProcessAccountsContacts {
public static String getJSON(String url) {
HttpRequest req = new HttpRequest();
req.setEndpoint(url);
req.setMethod('GET');
Http h = new Http();
HttpResponse res = h.send(req);
return res.getBody();
}
public static Integer processAccountsContacts() {
String jsonData = getJSON('http://api.example.com/accounts');
List<Account> accounts =
(List<Account>)JSON.deserialize(jsonData, List<Account>.class);
jsonData = getJSON('http://api.example.com/contacts');
List<Contact> contacts =
(List<Contact>)JSON.deserialize(jsonData, List<Contact>.class);
// 'Processing'
Integer result = accounts.size() + contacts.size();
return result;
}
}
I’ll create an instance of MultiStaticResourceCalloutMock, configuring it to provide the appropriate static resource data depending on the URL in the callout request. Here’s the test method in its entirety:
@isTest
private class ProcessAccountsContactsTest {
@isTest static void testCallout() {
MultiStaticResourceCalloutMock multimock =
new MultiStaticResourceCalloutMock();
// 3 test accounts
multimock.setStaticResource('http://api.example.com/accounts',
'jsonAccounts');
// 3 test contacts
multimock.setStaticResource('http://api.example.com/contacts',
'jsonContacts');
multimock.setStatusCode(200);
multimock.setHeader('Content-Type', 'application/json');
// Set the mock callout mode
Test.setMock(HttpCalloutMock.class, multimock);
// Call the method that performs the callouts
Test.startTest();
Integer result = ProcessAccountsContacts.processAccountsContacts();
Test.stopTest();
// Verify response is as expected, given the test data
System.assertEquals(6, result);
}
}
So, testing callouts with static data is very straightforward, but what about more complex use cases? I’ll cover the HttpCalloutMock and WebServiceMock interfaces next time out and show you how to create dynamic response data with dependencies on query parameters or the request body.
In Part I & Part II of this series, I discussed the details of hosting a web service on your computer and exposing it to the internet. If you are working in an enterprise/corporate network environment, your web service is almost always not exposed to the internet. If so, I would encourage you to also read Part I & II of this series, so you get a basic idea on how to expose your web service so that Salesforce can connect to it. In this part, we will do the fun stuff – building an Apex class that can call this web service. Before we proceed, let us revise what happens when Salesforce calls our web service -
1 – Our custom Apex class hosted on the Salesforce.com platform makes an outbound web service call.
2 – The call reaches our modem that forwards it to the wireless router.
3 – Since port forwarding is turned on, the router then forwards the request to our computer’s IP Address.
4 - The computer’s firewall intercepts the request, and since we opened port 80 on the firewall, lets it pass through.
5 – The IIS on the computer receives the web service request, and services it.
Now that we have the basics cleared off, let’s get into the specifics – here are step-by-step instructions on building an Apex class that calls your web service :-
Adding a Remote Endpoint
Testing our class via Anonymous blocks
So, these were the steps you can follow to invoke your web service from Salesforce.com. This approach has various applications – you could build an “event” mechanism so that external systems are alerted whenever something happens in Salesforce.com. Or, you could build an external logging facility that logs each and every page visit to an external database. We will explore some of the additional complexities of this process in the next post.
I have to be honest – I did not know how to do this. Having always programmed in an enterprise environment, I never gave it a thought on hosting something that is open to the internet. Fine, everybody can’t know everything, right ? Anyways, I figured there would be others as ignorant as I am (was :)), so here’s step-by-step instructions on exposing your webservice to the internet.
Part I: Hosting your web service
Part II: Opening your web service to the internet
Part III: Building an Apex class that calls your web service
The other day, I read about the ability to call external web services from Salesforce.com, and decided to give it a try. I come from a Microsoft programming background, so I expected it to be simple & straightforward. I ended up jumping through hoops, and by the end of it, I had already decided to write this post to save others the trouble.
I decided to break the whole process down into four parts -
Part 1 – will focus on how to build the webservice that we will be using.
Part 2 – will focus on how to make the webservice accessible to Salesforce.com from the Internet.
Part 3 – will focus on the Apex code etc. required on the Salesforce side to call the web service.
Part 4 – will focus on advanced issues like error handling, arrays etc.
In this part, we will simply build an old-fashioned asp.net web service. Since this is a fairly routine task for any programmer worth his salt, I will keep the instructions as concise as I can. So, here goes:-
That wraps up our first part – creating a bare bones web service. In the next post, we will see how to expose this web service to the internet so that Salesforce.com can call it.
Using Ping instead of CreateandSendPackage for brevity – Just replace SOAPXMLBody string with the above and change your Username, Password and AccountID with yours. You will need to break out over several string concatenations aka
SOAPXMLBody = SOAPXMLBody + "big long string";
Debug output should look like: