Salesforce Winter’25 Release Notes | Development – Apex – Page 2 – Salesforce Training Articles & Latest News

Track Apex Unexpected Exceptions with Free-Tier Event Monitoring

Event Log File Browser in Setup can now be used to track unhandled exceptions in Apex code execution, on top of the unhandled exception emails. Apex code can be troubleshooted by analyzing the information captured in the event log files for the Apex Unexpected Exception event type

More Coverage for Unexpected Exceptions in Apex Code Execution

Exceptions triggered by transactions with entry points as @AuraEnabled , @RestResource , and @InvocableAction annotations are now captured in the Apex Unexpected Exception event type. Analyze the event log files that provide information on exceptions triggered by these transactions. A spike in exception data logged in the event log files is possible because of the expanded coverage

SOQL Error and Functionality Changes

SOQL Error and Functionality Changes in this release can impact existing Apex code that relies on old SOQL error messages and functionality, particularly to dynamic SOQL code that handles the parsing of error messages. Apex code should be updated according to the new changes as needed

Support for negative currency values in queries, such as SELECT Name FROM Invoice__c WHERE Balance__c

New error messages with invalid SOQL queries SELECT Id FROM Account USING everything Old: unexpected token: ' ' New: unexpected token: 'everything'

SELECT ParentId, Value FROM InteractionRefOrValue WHERE ParentId IN () Old: unexpected token: ')' New: unexpected token: 'ParentId IN ()'

SELECT FROM ServicePresenceStatus Old: unexpected token: 'FROM' New: unexpected token: 'SELECT FROM'

SELECT Id from $casecomment WHERE isdeleted = false Old: line 1:15 no viable alternative at character '$' New: line 1:15 unexpected token: '$'

SELECT lastmodifieddate, companyna fr$om user Old: unexpected token: user New: missing value at 'user'

New error message in SOQL queries with quotes surrounding an unexpected token SELECT annualrevenue , parentid FROM Account WHERE (isDeleted = false AND NumberOfEmployees != 100) OR (isDeleted = false AND Site = '999') AND ParentId = '000000000000000' LIMIT 50000 Old: unexpected token: AND New: unexpected token: 'AND'

New error message when using NULL literals in WHERE statements with the LIKE keyword SELECT Id, Name, Country__c, State__c, City__c, PAN_Number__c FROM Account WHERE PAN_Number__c LIKE NULL AND Name LIKE '%a%' Old: invalid operator New: unexpected token: 'NULL'

New error message when using more than two nested functions SELECT convertCurrency(calendar_year(convertTimezone(lastmodifieddate))) FROM account Old: expecting a right parentheses, found ‘(’ New: unexpected token: ‘(’

New error messages in SOQL queries with invalid datetime literals SELECT Id FROM Account WHERE SystemModstamp > 2020-12-12t12:12:00-25:00 Old: line 1:67 mismatched character '5' expecting set '0'..'3' New: Invalid datetime: 2020-12-12t12:12:00-25:00

SELECT Id FROM Account WHERE SystemModstamp > 2020-52-12t12:12:00-05:00 Old: line 1:51 no viable alternative at character '5' New: Invalid datetime: 2020-52-12t12:12:00-05:00

New error message when there isn’t a valid bind variable reference after a colon SELECT Id FROM Custom_User_Attribute__c WHERE User__c =: 0050W000007Jz7jQAC Old: Only variable references are allowed in dynamic SOQL/SOSL New: unexpected token: '0050'

Consistency Improved When Iterating Sets

Starting from API version 62.0, modifying elements of a set while iterating the set in a for or foreach() loop throws an exception: System.FinalException: Cannot modify a collection while it is being iterated. In the previous API versions, modifications to sets while iterating were sometimes allowed and generated unexpected results

Example: Below code removes elements while iterating the set, which throws an exception: System.FinalException

Set set_string = new Set {'one', 'two', 'three'}; for (String str : set_string) { System.debug(str); set_string.remove(str); System.debug(set_string.contains(str)); } System.debug(set_string);

Write Mock SOQL Tests for External Objects

Increase code coverage and quality by writing better Apex unit tests for external objects and mock SOQL query responses using the new SOQL stub methods and a new test class. Use basic and joined SOQL queries against external objects and return mock records in a testing context. Apex governor limits apply to the stubbed records

How: Create mock test classes by extending the new System.SoqlStubProvider class and overriding the handleSoqlQuery() class method. Create external object records using either Test.createStubQueryRow() or Test.createStubQueryRows(). Register the mock provider in the test using Test.createSoqlStub() and execute the test code

The SOQL query must be against an external object, either directly with a FROM clause or via a subquery. These features aren’t allowed within a stub implementation

SOQL

SOSL

Callouts

Future methods

Queueable jobs

Batch jobs

DML

Platform events

Salesforce Winter’25 Release Notes | Development – Apex

Salesforce Spring’25 Release Notes | Customization – General Setup

Salesforce Winter’25 Release Notes | Salesforce Mobile App

Antonis Melakis

Salesforce Winter'25 Release Notes | Salesforce Mobile App

Leave a Reply Cancel reply

Recent Posts

Recent Comments

Welcome Back!

Retrieve your password