[SalesForce] Access variables in @Remoteaction

I have a @RemoteAction function in my Apex Class. I have a public static variable in this class. When I access this variable in the @RemoteMethod, there is error saying variable doesn't exist. When I make the class, method, and variable all global, the code compiles, but the variable is still null.

Can anyone help me in what am I doing wrong?

Best Answer

Notice that your RemoteAction is static. If the static variable you are trying to reference is set by instance logic in your controller, the new transaction context of the RemoteAction will lose that stateful information.

Works:

static Object myProperty
{
    get
    {
        if (myProperty == null)
        {
            // instantiate
        }
        return myProperty;
    }
    private set;
}

Doesn't Work:

static Object myProperty;
public MyController()
{
    myProperty = somethingStateful;
}

If myProperty depends on stateful information, it's not really static after all, even if you declare it so. Any state you want to maintain in your RemoteAction must be passed through parameters.

Related Solutions

[SalesForce] Call @future from @RemoteAction

Yes.

Could an exception, or the transaction rollback in Calculate cycle 13 be undoing the @Future?

The below works alright, so it sounds like the invocation of the plugin may be wanting.

RemoteController.cls

public class RemoteController {

    @RemoteAction static public void someAction() {
        RemoteController.deferStuff();
    }

    @Future static public void deferStuff() {
        insert new Account(Name = 'Future');
    }

}

RemotePage.page

<apex:page controller="RemoteController">
    <apex:outputLink onclick="RemoteController.someAction(function() {});">
        someAction()
    </apex:outputLink>
</apex:page>

[SalesForce] accessing static variables in method

When a page invokes a method the view state - the values of the fields of the class - are automatically re-populated immediately before the method runs. But static variables are not part of that mechanism (by design). Removing Static from the declarations and referencing them as normal non-static variables in SaveAgreement should address the problem.

More detail in e.g. An Introduction to Visualforce View State.

The simplest solution is to just do everything in the SaveAgreement method:

Public PageReference SaveAgreement() {

   Policy__c Pid=[select id from policy__c where Policy_Name__c='Health Insurance'][0];
   Id PolId = Pid.id;
   Account aa = [Select id from Account where name=:Name][0];
   Id Nameid = aa.id;

   ... just use the PolId and Nameid local variables here ...
}

but if you need to keep the logic spread across the 3 mthods:

Public Class PolicyHolderDetails { 

    Public ID PolId{get;set;}
    Public ID NameId{get;set;}

    Public void CheckInsurance(){
        Policy__c Pid=[select id from policy__c where Policy_Name__c='Health Insurance'][0];
        PolId = Pid.id;
    }

    Public void Save(){ 
        Account aa=[Select id from Account where name=:Name][0];
        NameId = aa.id;
    }

    Public PageReference SaveAgreement() {
        ... reference the PolId and NameId fields here ...
    }
}

Best Answer

Related Solutions

[SalesForce] Call @future from @RemoteAction

[SalesForce] accessing static variables in method

Related Topic