[SalesForce] call public void method from Anonymous Windows in Salesforce

How can i call public void method from Anonymous Windows in Salesforce for debugging purpose?

Like i have apex class:

public class student{
    {
        public void submit()
        {
            system.debug('This is student class');
        }
    }

and when i am executing this class using below syntax,

student s = new student();
system.debug(s.submit());

getting an error.

Method does not exist or incorrect signature: void debug(void) from the type System

Best Answer

Here you can see the example of calling the apex class method from anywhere

Sample Apex class

public class student{
    public void submit(){
        system.debug('This is student class'); 
    }
    public static void staticFun(){
        System.debug('Hello');
    }
}

Non-Static method create an instance of class then call

student objStudent = new student();
objStudent.submit(); // Output: This is student class

Static Method You can call simply via class name

student.staticFun(); // Output: Hello

In Salesforce you can execute your test code or sample code in the anonymous window. To open an anonymous window follow these steps:

Open Developer console after clicking on you name
In developer console press ctrl+E to open anonymous window
In an anonymous window, you can execute code whatever you want. In your scenario, you can create an instance of student class and call method.
After writing code click execute in debug log you can see output.

In Lighting, you can open developer console via clicking on gear icon (setting icon).

Related Solutions

[SalesForce] Error: Method does not exist or incorrect signature: void schedule

You are trying to pass a Batchable implementation where Schedulable is expected. This is just one reason why it is better to roll both into the same class. Regardless, your schedule method should pass in an instance of BatchEmails_Scheduler:

return system.schedule('<batch_name>', '<cron_string>', new BatchEmails_Scheduler());

Typically, rolling them together reduces the number of classes you have to maintain and adds little overhead:

public with sharing class MyBatch implements Database.Batchable<SObject>, Schedulable
{
    public void execute(SchedulableContext context)
    {
        Database.executeBatch(this);
    }
    public Database.QueryLocator start(Database.BatchableContext context)
    {
        // batch implementation
    }
    public void execute(Database.BatchableContext context, List<SObject> records)
    {
        // batch implementation
    }
    public void finish(Database.BatchableContext context)
    {
        // batch implementation
    }
}

[SalesForce] Method does not exist or incorrect signature: void schedule(String, String, PotentialCustomer) from the type System

The system.schedule method only accepts a class instance which implements Schedulable as its third argument. It's most efficient to just include this implementation detail on your batch itself.

public with sharing class MyBatch implements Schedulable, Database.Batchable<SObject>
{
    public void execute(SchedulableContext context)
    {
        Database.executeBatch(this);
    }
    // batchable implementation below
}

Please note you do not need the global access modifier for batches/scheduled jobs. The public access modifier will suffice.

Best Answer

Related Solutions

[SalesForce] Error: Method does not exist or incorrect signature: void schedule

[SalesForce] Method does not exist or incorrect signature: void schedule(String, String, PotentialCustomer) from the type System

Related Topic