Updating Miscellaneous API versions
The May '25 release encompassed several packages that were upgraded to Salesforce API version 62. Depending on the specific configuration of your organization, there might be additional, miscellaneous elements that require updating before the Salesforce Spring 2026 release. It is important to note that if you have any custom Apex classes, triggers, or Visualforce pages, it is your responsibility to identify and update these components to Salesforce API version 62.
The following steps will guide you through the process of updating various Apex Classes, Apex Triggers, and Visualforce pages:
Item 1: Verify you’ve completed May ’25 API version updates
Verify that you’ve completed the API version updates for the May ’25 release for each of the following unmanaged packages:
Item 2: Update API Version on Apex Classes
- Navigate to Setup and search for Apex Classes.
- For each of the classes listed below, go to Edit, select the Version Settings tab, and set the Salesforce.com API version to 62.0:
- AppReaderExtension
- AppReaderExtensionTest
- objectDictionaryController
- SortSelectOptions
- testObjectDictionaryController
- testSortSelectOptions
- TxAppReviewBeforeInsertTriggerTest
Item 3: Update API Version on Apex Triggers
- Navigate to Setup and search for Apex Triggers.
- For each of the triggers listed below, go to Edit, select the Version Settings tab, and set the Salesforce.com API version to 62.0:
- TxAppReviewBeforeInsertTrigger
Item 4: Update API Version on Visualforce Pages
- Navigate to Setup and search for Visualforce Pages.
- For the Visualforce pages below, go to Edit, select the Version Settings tab, and set the Salesforce.com API version to 62.0:
- AppReviewProfile
- Decision Letter
- Note: If you have cloned a version of this Visualforce page, please update all cloned versions.
- objectDictionary
- ObjectDictionaryExport
- objectImportHeader
Item 5: Ensure all Apex Classes, Apex Triggers, and Visualforce Pages are API 45 or higher
- Navigate to Setup and search for Apex Class, Apex Trigger, or Visualforce Pages.
- Select the ‘All’ list view, and sort the API Version to ensure the lowest version of each category is above 45.
- If you find an outdated TargetX Package-related Apex Class, Apex Trigger, or Visualforce Page, please uninstall that package:
- Navigate to Setup and search for Installed Packages
- Locate the outdated TargetX Package
- Click Uninstall
- You can also choose to seek assistance by submitting a TX Support Case in the community.
- If you find a third-party related Apex Class, Apex Trigger, or Visualforce Page, please contact that provider for further assistance.
- Finally, if you find an Apex Class, Apex Trigger, or Visualforce Page you created, it will be your responsibility to update the API to a version higher than 45.