Salesforce v61.0 — Breaking Changes Checklist

7 items total2 critical~1.5 hours for a typical integration

Before You Upgrade

1.Consult the official Salesforce release notes for v61.0 to identify all documented breaking changes.
2.Identify and document all Salesforce API endpoints and objects your integration currently uses.
3.Set up a dedicated sandbox environment for testing the v61.0 API version.
4.Review the checklist items and assign responsibilities for each task.
5.Notify stakeholders about the planned upgrade and potential impact.

0/3

Understand modifications in API response structures and field behaviors that could affect your existing logic.

Review and adjust logic for currency fields with increased precision.Criticalmedium

Certain currency fields now support greater precision, potentially impacting calculations or data storage if not handled.

⚠ Data truncation or incorrect financial calculations in your integration.

Identify and remove usage of any deprecated fields or objects that have been retired in v61.0.Higheasy

Salesforce periodically retires APIs and fields. Ensure your integration does not rely on endpoints removed in this release.

⚠ API calls referencing removed fields or objects will fail.

Verify that your integration correctly handles API version-dependent behaviors for core objects.Mediummedium

Be aware of subtle changes in how standard Salesforce objects behave across different API versions.

⚠ Unexpected data retrieval or manipulation due to altered object behavior.

0/2

Ensure your authentication methods and security configurations remain compatible with v61.0.

Confirm your OAuth 2.0 flows are compatible with any authentication protocol updates.Criticalmedium

Salesforce may introduce security enhancements or changes to OAuth 2.0 flows, requiring adjustments to your authorization process.

⚠ Inability to authenticate and access Salesforce data.

Review IP address restrictions and ensure they align with any enhanced validation logic.Mediumeasy

IP-based security controls might have stricter validation or new enforcement mechanisms in v61.0.

⚠ Legitimate API requests being blocked due to stricter IP validation.

0/2

Thoroughly test your integration in a sandbox environment before deploying changes to production.

Execute your comprehensive regression test suite against a v61.0 sandbox.Highmedium

Ensure all critical functionalities and workflows perform as expected after the upgrade.

⚠ Undiscovered bugs and functional regressions in production.

Validate key performance benchmarks and user experience metrics.Mediummedium

Monitor API response times and overall integration performance to catch any degradation.

⚠ Degraded integration performance impacting end-user experience.

✓Monitor API error logs closely for any unusual activity or failures.
✓Gather user feedback on integration performance and functionality.
✓Review metrics for any unexpected changes in data accuracy or processing times.
✓Perform a final verification of all critical business processes.
✓Keep the v60.0 sandbox available for a rollback if necessary.

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