[SalesForce] how to pass the map from one method to onother method

I have trigger after insert and after update

if(trigger.isinsert){
Forecastcheckemail fr=new Forecastcheckemail(trigger.newmap,null);
fr.SendEmail();
}
If(trigger.Isupdate)
{
Forecastcheckemail fr=new Forecastcheckemail(trigger.newmap,trigger.oldmap);
fr.SendEmail();
}

Apex Class:

I want newOppMap in sendEmail() Method as well.
But i am getting error in the line Opportunity opp = newOppMap.get(id);…..Please suggest

Best Answer

You can simply pass the new map in fr.SendEmail(); method

fr.SendEmail(Trigger.NewMap);

and your method will be

public void SendEmail(map<Id, Opportunity>){

}

Or Another way use a private map in the controller to store the new map and old map and when you controller constructor called. Just assign the old and new map to private variables and use those variables in wherever you want

Related Solutions

[SalesForce] Moving Triggers to Utility Class

The error message "Field expression not allowed for generic SObject" means that you're trying to use "dot" syntax where it isn't allowed or can't be performed.

In this case, it's because the code is referencing a generic sObject (which might not have the expected field on it) and the compiler can't verify the existence of .Product__c on it. You can either cast the generic sObject to its proper type or reference a collection of a concrete type, Sampling__c in this case and the compiler will be satisfied.

Now that you've got a method parameter named oldMap which is being passed in with the concrete type, you can reference it in your code. In addition, you've also still got access to the Trigger static references when this code is being called from within the trigger's context.

public void updateSamplingAE2(List<Sampling__c> sampling, Map<Id, Sampling__c> oldMap) {
    // not sure what the s reference is, left it as is

    // changed the reference from Trigger.oldMap to the method param oldMap
    if (Trigger.isUpdate && oldMap.get(s.id).Product__c != s.Product__c) {
        //do stuff
    }
}

[SalesForce] How to cover afterUndelete method when you can’t Undelete

I would adopt a different handler pattern in that case, personally. If it's forcing you to implement methods you don't even need, it is probably not optimal. I usually opt for a much simpler framework with no interfaces or abstract classes.

But from a pure coverage perspective you can hit the method by simply calling:

new MyHandler().afterUndelete(new Map<Id, SObject>());

In this case, you don't really care what's in the map, since the entire existence of the method is just garbage boilerplate required by your framework.

Best Answer

Related Solutions

[SalesForce] Moving Triggers to Utility Class

[SalesForce] How to cover afterUndelete method when you can’t Undelete

Related Topic