Engineering bulletin: Potential issues with SFDC “Winter ‘22” release

    Publication date: 22 September, 2021

    Overview

    During September and October 2021, Salesforce (SFDC) will roll out the Winter ‘22 release to all production customers. As part of the release, the way their access tokens work has changed, and existing access tokens may not function correctly after the upgrade. If issues occur, customers are advised to refresh their Tenfold CRM connection. To consult the major release upgrade date for your Salesforce instance, go to Trust Status, search for your instance, and click the maintenance tab

    Who is impacted

    All Tenfold customers using Salesforce as their CRM could potentially be impacted.

    What is the impact

    After the SFDC upgrade, customers may notice that they are authenticated, but that they are unable to perform certain functions within the Tenfold application, such as automatically creating CRM objects.

    Technical description

    There is an issue when using existing OAuth tokens with the Salesforce Winter ‘22 Release.  Access tokens and refresh tokens that were created prior to the Winter ‘22 release are no longer valid after the upgrade to Winter ‘22 release.  A refresh (described in Remediation, below) will get new access and refresh tokens.

    How can Tenfold help?

    At this time, Tenfold engineering does not have an automated way of detecting or correcting the issue. Manual remediation is recommended.

    Remediation steps

    Important

    Only perform these steps after your new “Winter” token is provided by Tenfold. Do not perform these steps prior to your Salesforce instance being upgraded to Winter ‘22 release.

    1. Log out of SFDC and Tenfold Dashboard and quit browser, then relaunch the browser OR log in using an incognito window or separate browser profile.
    2. Log in to Tenfold Dashboard as an Admin.
    3. Connect to Sandbox (or Production, if applicable).
    4. Authenticate using credentials for Tenfold Integration User. Continue to the next step after your connection is successful.
    5. Change Authentication Type to Default.
    6. Save.

    Missing Something?

    Check out our Developer Center for more in-depth documentation. Please share your documentation feedback with us using the feedback button. We'd be happy to hear from you.