Write a method with more than one parameter in the Developer Console

debuggingdeveloper-console

I'm trying to debug this method on the developer console:

string groupId='';
List <String> selectedUsers='';
List <String> updatedUsers='';
Boolean userUpdatedBool=false;


UsersController.addRemoveUsers(groupId,List selectedUsers,List updatedUsers,
userUpdatedBool);

but I get this error popup: Title: Execute Anonymous Error, Error: Line: 7, Column: 31 Unexpected token '('.

does anyone know how should I write this, so the developer console can accept it? Previously I was debugging another this method:
string userId=''; UsersController.fetchUsers (userId); with one String parameter and it was working perfectly, but now that I have List parameters and more than one I can't make it work.

Best Answer

You're writing the code as if you were trying to declare a parameter list. You need to actually pass in data:

String groupId = '...';
String[] selectedUsers = new String[] { '005...','005...' };
String[] updatedUsers = new String[] { '...', '...' };
Boolean userUpdatedBool = false;
UsersController.addRemoveUsers (groupId, selectedUsers, updatedUsers, userUpdatedBool);

Adjust your inputs as necessary.

Related Solutions

[SalesForce] How to speed up Developer Console

To set up perspective you need to load some log first:

enter image description here

Then click on the "Perspective All" button and then navigate to "View Panels". Turn some off and save new perspective as "New one".

enter image description here

By the way you can use for example Force.com IDE too:

enter image description here

[SalesForce] How to best analyze limit problems in the Developer Console

With respect the Execution Order Limits tab, I set the Profiling logging level to finest and captured a log.

The Finest Profiling Logging Level

The Execution Overview Limits did populate for me:

Developer Console Execution Overview Limits

Note that the values displayed are being extracted from the LIMIT_USAGE_FOR_NS logging messages (which appear at the Finest Profiling logging level.) If for some reason the LIMIT_USAGE_FOR_NS entries are missing from your log then the limits tab won't be populated. This may occur if the maximum debug log size is reached and the entries are truncated out of the log.

For the Execution Order Save Order tab...

I believe each line represents a distinct sObject type. E.g. Account, Contact, Opportunity, custom sObjects, ...

Each column is for a CODE_UNIT_STARTED log event. If you click in the coloured cell and then on "Select line in Log Panel" it will take you to the corresponding Execution Log CODE_UNIT_STARTED event. This will tell you the applicable ID (Trigger ID), if it is a before/after insert/update trigger etc...

enter image description here

The colours will depend on the type of event. Looking at the source code for my first event I can see it has the CSS class .BEFORE_TRIGGER_NODE, which is red. You can see all the events and corresponding colours in https://na2.salesforce.com/sCSS/32.0/sprites/1415904510000/Theme3/default/gc/CSI.css

After pulling it apart I also found the official documentation on the colours - Execution Overview: Save Order, Limits, Timeline, and Executed Units

Color Type

Red Before trigger

Orange After trigger

Green Validation rule

Blue Assignment rule

Purple Workflow rule

Finding the best way to analyse a limit problem really depends on what limit you are hitting. The managed packages will probably have separate limits and you will see this next to the LIMIT_USAGE_FOR_NS log messages.

If you are hitting the limits in your code you may want to check the values using the Limits calls in Apex.

E.g.

System.debug(LoggingLevel.Debug, 'someMethod() - Current Query Rows: ' + Limits.getQueryRows() + '/' + Limits.getLimitQueryRows());
System.assert(Limits.getQueries() < Limits.getLimitQueries(), 'Reached Query Limit...');

Best Answer

Related Solutions

[SalesForce] How to speed up Developer Console

[SalesForce] How to best analyze limit problems in the Developer Console

Related Topic