Skip to main content

Invalid constructor syntax, name=value pairs can only be used for SObjects (Line: 90)


If you bumped to this entry, I would like to thank you.I 'll update the content as below.Since my explanation not really helpful at previous post.You still able to view old post at OBSOLETE section below at the end of this post.

I always accidentally face this exception : Invalid constructor syntax, name=value pairs can only be used for SObjects because I instantiate inner class like SObject such as below :

WrapperObj obj = new WrapperObj (paramId=a.Id,isChecked=a.Primary__c,Account=a);

While that only valid for SOBJECT.For inner class, we should use this.Without name value pair.

WrapperObj obj = new WrapperObj (a.Id,a.Primary__c,a);


public class MyExtension {
    
    //other code
    
    public void retrieveInfo(){
        List<WrapperObj >  listAccountObject = new List<WrapperObj > ();
        List<Account > listAccount = [Select Id,Primary__c from Account  where Id=:acct.Id];
        
        if(listAccount.size()>0){
            for(Account a: listAccount ){
        //INVALID WAY FOR CONSTRUCTOR#2
              WrapperObj obj = new WrapperObj (paramId=a.Id,isChecked=a.Primary__c,Account=a);
  
    //CORRECT WAY FOR CONSTRUCTOR#2
     WrapperObj obj = new WrapperObj (a.Id,a.Primary__c,a);
     
    //ANOTHER CORRECT WAY FOR CONSTRUCTOR#1
     WrapperObj obj = new WrapperObj ();
     obj.paramId=a.Id;
     obj.isChecked=a.Primary__c;
     obj.myAccount=a;
              
           }
  }
    }
    
 //inner class
    public class WrapperObj {
    
         public String paramId {get;set;}
         public Boolean isChecked {get;set;}
         public Account myAccount {get;set;}
         
   //CONSTRUCTOR#1
         public WrapperObj(){
  }
  
   //CONSTRUCTOR#2
         public WrapperObj (String paramId,Boolean isChecked,Account acct){
            this.paramId=paramId;
            this.isChecked=isChecked;
            this.myAccount=acct;
    
         }

    }
}

Have a nice day.

Thanks.
-------------------------------------------OBSOLETE---------------------------------------------------------
*Yawn* Sometimes the best of us always forget the basic one.

If we create inner class , it is not allowable to instantiate it like we always do for standard object as below:

Series s = new Series(name='s1');

We should instantiate and define using longer way like this:

Series s=new Series();
s.name='s1';

Good Luck~


Comments

Popular posts from this blog

Search Solution Basics

When is it a good time to create a customized search solution? You're developing an external knowledge base for user support. You're in the mood for a fun Friday night. The sales reps just started using the Sales Cloud in Lightning Experience. You want to put your company branding in the search bar. What differentiates SOSL from SOQL? Syntax SOSL searches the search index instead of the org database. SOSL searches more efficiently when you don't know in which object the data resides. All of the above. SOSL works with: REST only SOAP only REST, SOAP, and Apex SOQL only What does a search for a single object look like in SOSL? FIND {cloud} RETURNING Account FIND in ACCOUNT RETURNING "cloud" FIND "cloud" in ACCOUNT FIND (cloud) RIGHT NOW! What does a search for multiple objects look like in SOSL? FIND {sneakers} RETURNING ALL ARTICLES FIND {sneakers} in ALL OBJECTS FIND {sneakers} RETURNING Product2, Content

Process Builder is not fired when field update is called from Approval Process

Scenario In Final Approvals section ; in Approval Process we have field update to update Status field. In Process Builder , we have some action that need to be done when Status field is updated in Approval Process.However this process builder is not fired. Solution To handle this, in Field Update in Approval Process , check Re-evaluated Workflow Rules after Field Change as picture below. What happen if field updated from Approval Process. Workflow - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Process Builder - does not fires untill Re-evaluate workflow checkbox is ticked on your field update Trigger - will fire if conditions are matched This is explained in article here  . Field Updates That Re-evaluate Workflow Rules If  Re-evaluate Workflow Rules After Field Change  is enabled for a field update action, Salesforce  re-evaluates all workflow rules on the object if the field update results in a change to the value of the fi

Tips and Tricks : Test class for Invocable method

Issue : I got 100% coverage in my sandbox but when run validation for deployment it returns 0% coverage It turn out that in my sandbox, I am depending on Process Builder to Invocable Apex class, as long I manipulate test data that fire Process Builder it will call Invocable class. This is not useful when deploying it to Production although it gets deployed together with Process Builder. The correct way is to direct call Invocable method inside test class itself. Example of class : 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 28 29 30 31 32 33 global class MyCustomObject_StatusUpdate_Util { @InvocableMethod ( label = ' Update Quote Status ' ) public static void updateQuote ( Request [] requests ) { Set < Id > setOppId = new Set < Id >(); List < SBQQ__Quote__c > listQuoteToUpdate = new List < SBQQ__Quote__c >(); for ( Request request : requests ) {