//Option 1

execute (scope) {
   foreach(myObject__c obj: scope) {
       totalSum += obj.field_to_sum__c; //<== Line 1
   }
}

//Option 2

execute (scope) {
   Integer localSum = 0;
   foreach(myObject__c obj: scope) {
       localSum += obj.field_to_sum__c;
   }

 totalSum += localSum;  //<== Line 2
}

public with sharing class TestController2 {
    @AuraEnabled
    public static integer getTestResult(integer pageNumber) {
        return pageNumber + 1;
    }
}

34.0 APEX_CODE,DEBUG;APEX_PROFILING,INFO;CALLOUT,INFO;DB,INFO;SYSTEM,DEBUG;VALIDATION,INFO;VISUALFORCE,INFO;WORKFLOW,INFO
23:30:39.143 (143052245)|EXECUTION_STARTED
23:30:39.143 (143081946)|CODE_UNIT_STARTED|[EXTERNAL]|01pU0000001YzfB|TestController2.getTestResult
23:30:39.143 (143501666)|METHOD_ENTRY|[1]|01pU0000001YzfB|TestController2.TestController2()
23:30:39.143 (143599706)|SYSTEM_MODE_ENTER|false
23:30:39.143 (143634027)|SYSTEM_MODE_EXIT|false
23:30:39.143 (143644512)|METHOD_EXIT|[1]|TestController2
23:30:39.144 (144047168)|FATAL_ERROR|Internal Salesforce.com Error
23:30:39.144 (144066440)|CUMULATIVE_LIMIT_USAGE
23:30:39.144 (144066440)|LIMIT_USAGE_FOR_NS|(default)|
  Number of SOQL queries: 0 out of 100
  Number of query rows: 0 out of 50000
  Number of SOSL queries: 0 out of 20
  Number of DML statements: 0 out of 150
  Number of DML rows: 0 out of 10000
  Maximum CPU time: 0 out of 10000
  Maximum heap size: 0 out of 6000000
  Number of callouts: 0 out of 100
  Number of Email Invocations: 0 out of 10
  Number of future calls: 0 out of 50
  Number of queueable jobs added to the queue: 0 out of 50
  Number of Mobile Apex push calls: 0 out of 10

23:30:39.144 (144066440)|LIMIT_USAGE_FOR_NS|Vendavo|
  Number of SOQL queries: 0 out of 100
  Number of query rows: 0 out of 50000
  Number of SOSL queries: 0 out of 20
  Number of DML statements: 0 out of 150
  Number of DML rows: 0 out of 10000
  Maximum CPU time: 0 out of 10000
  Maximum heap size: 0 out of 6000000
  Number of callouts: 0 out of 100
  Number of Email Invocations: 0 out of 10
  Number of future calls: 0 out of 50
  Number of queueable jobs added to the queue: 0 out of 50
  Number of Mobile Apex push calls: 0 out of 10

23:30:39.144 (144066440)|CUMULATIVE_LIMIT_USAGE_END

23:30:39.144 (144134140)|CODE_UNIT_FINISHED|TestController2.getTestResult
23:30:39.147 (147174875)|EXECUTION_FINISHED

public with sharing class TestController2 {
    @AuraEnabled
    public static integer getTestResult(integer pageNumber) {
        return pageNumber + 1;
    }
}

34.0 APEX_CODE,DEBUG;APEX_PROFILING,INFO;CALLOUT,INFO;DB,INFO;SYSTEM,DEBUG;VALIDATION,INFO;VISUALFORCE,INFO;WORKFLOW,INFO
23:30:39.143 (143052245)|EXECUTION_STARTED
23:30:39.143 (143081946)|CODE_UNIT_STARTED|[EXTERNAL]|01pU0000001YzfB|TestController2.getTestResult
23:30:39.143 (143501666)|METHOD_ENTRY|[1]|01pU0000001YzfB|TestController2.TestController2()
23:30:39.143 (143599706)|SYSTEM_MODE_ENTER|false
23:30:39.143 (143634027)|SYSTEM_MODE_EXIT|false
23:30:39.143 (143644512)|METHOD_EXIT|[1]|TestController2
23:30:39.144 (144047168)|FATAL_ERROR|Internal Salesforce.com Error
23:30:39.144 (144066440)|CUMULATIVE_LIMIT_USAGE
23:30:39.144 (144066440)|LIMIT_USAGE_FOR_NS|(default)|
  Number of SOQL queries: 0 out of 100
  Number of query rows: 0 out of 50000
  Number of SOSL queries: 0 out of 20
  Number of DML statements: 0 out of 150
  Number of DML rows: 0 out of 10000
  Maximum CPU time: 0 out of 10000
  Maximum heap size: 0 out of 6000000
  Number of callouts: 0 out of 100
  Number of Email Invocations: 0 out of 10
  Number of future calls: 0 out of 50
  Number of queueable jobs added to the queue: 0 out of 50
  Number of Mobile Apex push calls: 0 out of 10

23:30:39.144 (144066440)|LIMIT_USAGE_FOR_NS|Vendavo|
  Number of SOQL queries: 0 out of 100
  Number of query rows: 0 out of 50000
  Number of SOSL queries: 0 out of 20
  Number of DML statements: 0 out of 150
  Number of DML rows: 0 out of 10000
  Maximum CPU time: 0 out of 10000
  Maximum heap size: 0 out of 6000000
  Number of callouts: 0 out of 100
  Number of Email Invocations: 0 out of 10
  Number of future calls: 0 out of 50
  Number of queueable jobs added to the queue: 0 out of 50
  Number of Mobile Apex push calls: 0 out of 10

23:30:39.144 (144066440)|CUMULATIVE_LIMIT_USAGE_END

23:30:39.144 (144134140)|CODE_UNIT_FINISHED|TestController2.getTestResult
23:30:39.147 (147174875)|EXECUTION_FINISHED

While creating a custom object, in object classification, we have this three options(either all enabled/disabled).
I want to know difference between these three.

Here is the image of object classification.

I've got a visualforce page the is outputting a data table with a list of accounts in the account hierarchy.  One of the columns displayed is the account record type.  We have translated the record type values in the translation workbench and they display correctly translated on the standard acccount page layout.  However, when we try to render them in a dataTable, they show the English values when a non-English user is logged in.  Anyone have any good workarounds for this?  Here is the code we are using:

<apex:column >
    <apex:facet name="header">{!$ObjectType.Account.Fields.Type.Label</apex:facet>
    <apex:outputText style="{!IF(pos.currentNode,'font-weight: bold;','')}" value="{!pos.account.RecordType.Name}" />
</apex:column>

Hi,

How to sort the list  as case insensitive. I am used the method as

listname.sort();

It will sort the records. But it will display the records in sort order which are having caps lock as first letter. After that display's the records in sort order which are having small letters as first letter. Please help me how sort the list as case insensitivly.

Thanks,

Lakshmi.

Hello Everyone,

I am facing problem with translation. The issue, I have picklist with values. I have added translations for pick list values based on the language. The problem when i try to query or when i try invoke in formula field i getting actual value instead of traslation value.Can anybody help on this.

Regards,

Insane

Recently, I was writing some classes that needed to detect if the org they were in was a sandbox or not and determine which endpoint to call accordingly. Since there isn's an isSandbox method in Apex, I had to create my own. This will work in visualforce controllers/extensions and from standard classes. You can read the full details at http://www.ericsantiago.com/eric_santiago/2011/12/determining-salesforce-server-pod-and-if-sandbox-via-apex.html

Code as follows

public String currentPod { 
            String server;
            
            if (ApexPages.currentPage() != null){ //called from VF page
            		server = ApexPages.currentPage().getHeaders().get('X-Salesforce-Forwarded-To');
            } else { //called via standard class
            		server = URL.getSalesforceBaseUrl().getHost();
            }
            
            if ( server != null && server.length() > 0){
                server = server.substring(0 ,server.indexOf('.'));
                
            }
            return server ; 
   }

   public Boolean isSandbox {
            String pod = currentPod();
            if (pod != null && pod.length() > 0 && pod.toUpperCase().startsWith('C')){
                return true;
            }
            return false;
   }

Hi All,

I am trying to pull in the Account Owner's Name to a custom object using a formula. However just see an option for the Account Owner ID.

TIA

David

Hello All, 

Newbie here.  My question relates to insuring referential integrity among some custom objects.  I have created custom objects:

OrderItem //a detail on an Order (participates as such in a Master/Detail relationship to Order.)  OrderItem refers to a Product, and a quantity ordered for some requestedDate.  Ultimately, upon fulfillment it will be updated to reflect date fulfilled, quantity variances and the like.

Authorization //an independently persistent object that refers to an Account and a Product and contains a StartDate (and optionally an EndDate).  AProduct is said to be authorized at anAccount on aDate IFF there exists an Authorization referring to that Account and Product with a StartDate <=  aDate <= EndDate.

When constructing an Order (for some Account), one writes some number of OrderItems - each relating to some Product.

The referential integrity issue is that to be valid, an OrderItem should only refer to a Product which is Authorized for the Account on the OrderItem.requestedDate.

Now the easy way to make this work would be to Filter the list of Products shown to the user at OrderItem creation time.  But the filter functionality doesn't seem to be available for lookup items, only master/detail lookups.  Maybe this is due to the Beta status of the functionality, or maybe it has to do with my level of account - Not sure.

If someone can tell me how to get the filter working so that only valid choices are offered, that would be great.

But failing the capacity to filter, then I'd like to Validate the OrderItem against the Authorizations for the Account.  

For extra credit, there's also the fact that the set of Authorizations for an Account is actually the transitive closure of all Authorizations for that Account and it's Parent (recursively to it's highest level Parent).  

So - if someone has any words of wisdom (or even better) example code, I'd be grateful.  Especially if there's some way to make this work without getting into APEX and so on.  I'm a business level user.

Thoughts?

Thanks all,

SandwichMaven

So I just burned a couple of hours trying to figure out what was breaking in my code. I figured it out but I still don't understand what is happening. You can paste the code below into the system log and execute.

Boolean someNullBoolean;
Contact c = new Contact(LastName = 'lname');
c.HasOptedOutOfEmail = someNullBoolean;
//c.HasOptedOutOfEmail should be null as it was contructed as null and we are also assigning the value of null, right? WRONG!

system.debug(c);
//cool, the value of HasOptedOutOfEmail is displaying as null, that makes sense
system.debug('HasOptedOutOfEmail; ' + c.HasOptedOutOfEmail);
//wait, what?!? HasOptedOutOfEmail is now false? I thought we set it to null

//eh, none of this should matter right? let's try to insert this contact
insert c;

//aw snap,
//System.DmlException: Insert failed. First exception on row 0; first error: INVALID_TYPE_ON_FIELD_IN_RECORD, Email Opt Out: value not of required type: {0}: [HasOptedOutOfEmail]

Is this a bug, some expected behvior with booleans I don't understand, or am I in the matrix?

Thanks,

Jason