Salesforce v60.0 — Breaking Changes Checklist

7 items total3 critical~3 hours for a typical integration

Before You Upgrade

1.Review the official Salesforce API v60.0 release notes for a comprehensive list of all changes.
2.Identify all Salesforce API endpoints and objects your integration interacts with.
3.Analyze your integration's code for any dependencies on fields, features, or behaviors mentioned in the v60.0 release notes.
4.Consult the 'Deprecated Features' section of the Salesforce documentation to confirm any removed endpoints or functionalities.
5.Test your integration thoroughly in a sandbox environment running API v60.0.
6.Backup your integration code and any related configuration files.

0/3

Review changes to existing API behaviors, field behaviors, and feature deprecations that might impact your integration's logic.

Verify if any fields your integration uses now require new permissions.Criticalmedium

Some fields may have had their access requirements changed, potentially leading to 'INSUFFICIENT_ACCESS' errors if not updated.

⚠ Your integration may encounter permission errors when accessing specific fields.

Identify and update integrations using features or endpoints that have been fully deprecated and removed in v60.0.Criticalmedium

Salesforce removes deprecated features at certain release cycles. Ensure your integration doesn't rely on these removed components.

⚠ API calls to removed features will fail, potentially breaking core integration functionality.

Check for any changes or deprecations in enum values used in API requests or responses.Higheasy

Modifications to picklist or other enumerated field values can cause validation errors if your integration sends outdated values.

⚠ Your requests might be rejected due to invalid enum values, or your parsing logic may break.

0/2

Understand changes related to security protocols, authentication methods, and access controls.

Review any updates to OAuth 2.0 flows or related security parameters.Mediummedium

Changes in OAuth 2.0 can affect how your application authenticates and obtains access tokens.

⚠ Authentication failures or unexpected token expiration could occur.

Verify if Cross-Origin Resource Sharing (CORS) policies have been updated that might affect your web-based integrations.Loweasy

Adjustments to CORS can impact browser-based clients trying to access the Salesforce API.

⚠ Web applications may be unable to make API calls due to browser security restrictions.

0/2

Assess changes to standard and custom object fields, relationships, and metadata.

Examine if any standard or custom field types have changed that could affect data storage or retrieval.Highmedium

Changes in field types (e.g., from Text to Long Text Area) might require adjustments in how you handle data.

⚠ Data corruption, data truncation, or failed data operations can occur.

Determine if any new fields have become required that your integration needs to populate.Mediumeasy

If a previously optional field is now mandatory, your create or update operations will fail without it.

⚠ Record creation or update operations may fail if required fields are not provided.

✓Monitor your integration's logs for any new errors or warnings after the upgrade.
✓Perform regression testing on all critical integration workflows.
✓Verify that data integrity is maintained for all data processed by the integration.
✓Check user feedback for any reported issues related to the integration's performance or functionality.
✓Keep an eye on Salesforce communications for any hotfixes or urgent updates related to API v60.0.

Deprecatr AI monitors 150+ providers, maps changes to your codebase, and delivers migration checklists before your team hits a breaking change.