Salesforce has made important updates to how SOQL queries handle certain edge cases, which may impact existing Apex code that relies on old SOQL error messages and functionality. Specifically, these changes affect dynamic SOQL queries and error parsing. In this post, we’ll explore what’s new and how to adapt your code to these changes.
What’s Changing?
New Error Messages for Invalid SOQL Queries
Salesforce has introduced clearer, more descriptive error messages when dealing with invalid dynamic SOQL queries. This helps you pinpoint issues faster and more accurately. Here are some examples of the new error handling and functionality changes and Understand SOQL Errors with New Features:
Example 1: Negative Currency Values in Multi-Currency Orgs
Old Behavior:SELECT Name FROM Invoice__c WHERE Balance__c < USD-500 would fail.
New Support:You can now handle negative currency values in multi-currency orgs. This query is now valid.
Example 2: Clarified Error Messages for Invalid Keywords
Old Error:SELECT Id FROM Account USING everything returned the cryptic error: unexpected token: '<EOF>'
New Error:Now, you’ll receive a more specific message: unexpected token: 'everything'
Example 3: Parenthesis Errors Now More Descriptive
Old Error:SELECT ParentId, Value FROM InteractionRefOrValue WHERE ParentId IN () resulted in: unexpected token: ')'
New Error:A clearer message is provided: unexpected token: 'ParentId IN ()'
Example 4: Improved FROM Clause Errors
Old Error:SELECT FROM ServicePresenceStatus would give: unexpected token: 'FROM'
New Error:The error message now reads: unexpected token: 'SELECT FROM'
Example 5: Special Character Issues Now Identified More Clearly
Old Error:SELECT Id from $casecomment WHERE isdeleted = false showed: no viable alternative at character '$'
New Error:Now, it will read: unexpected token: '$'
Example 6: Ambiguous Query Issues Fixed
Old Error:SELECT lastmodifieddate, companyna fr$om user produced: unexpected token: user
New Error:Now, the error message reads: missing value at 'user'
Example 7: Complex Nested Functions in Queries
Old Error:SELECT convertCurrency(calendar_year(convertTimezone(lastmodifieddate))) FROM account resulted in: expecting a right parentheses, found ‘(’
New Error:Now, the system clarifies: unexpected token: ‘(’
Example 8: Invalid Datetime Literals
Old Error:For queries like SELECT Id FROM Account WHERE SystemModstamp > 2020-12-12t12:12:00-25:00, you’d receive: mismatched character '5'
New Error:The system now throws: Invalid datetime: 2020-12-12t12:12:00-25:00
Example 9: Bind Variables
Old Error:SELECT Id FROM Custom_User_Attribute__c WHERE User__c =: 0050W000007Jz7jQAC would return: Only variable references are allowed in dynamic SOQL/SOSL
New Error:Now, you’ll see: unexpected token: '0050'
How to Adapt Your Code
If you rely on parsing error messages or dynamic SOQL query functionality in your code, it's critical to review these changes. Some key considerations include:
Error Handling:Ensure that your code properly handles the new error formats, especially if your logic depends on catching and parsing specific SOQL errors.
Multi-Currency Handling:Take advantage of the new support for negative currency values, particularly if you work in multi-currency orgs.
Complex Queries:Be mindful of the new limits around nested functions and null literals. You may need to rewrite or simplify certain dynamic SOQL queries to avoid runtime errors.
By updating your code now, you’ll ensure smoother operations and fewer issues when running dynamic SOQL queries in your org. Stay ahead of the curve by embracing these improvements and optimizing your SOQL queries accordingly.
This update applies to all Salesforce editions, so whether you're in Professional, Enterprise, or Unlimited, you’ll want to review your current Apex code and test any affected queries.
Conculsion
These SOQL error and functionality changes may seem subtle, but they can have a significant impact on your Salesforce implementation, especially if you rely heavily on dynamic SOQL. The new error messages provide much-needed clarity, helping developers identify and fix issues more efficiently. Keep these updates in mind as you fine-tune your Apex code for the future!
Comments