The recent announcement from Salesforce that it will change its API endpoints on the 1st of January 2016 has a critical impact on the following products:
- S4S, the Sitecore to Salesforce connector - see solutions below.
- G4S, the generic ASP.NET to Salesforce connector - see solutions below.
- FuseIT SFDC Explorer: Download the latest version from our website
- FuseIT SFDC Data Export functionality: Download the latest version from our website.
All customers using these connectors will need to take urgent action to prevent a connection failure after 1 January.
The current endpoint of S4S is www.salesforce.com. Salesforce are retiring this endpoint and advising API users to use login.salesforce.com.
There are two known solutions depending on your S4S version. Please consider both to see which works best for your situation.
Solution 1: Change the environment setting in the connection string
Change the environment value from "Production" to "login.salesforce.com". In versions 1.6.13297 and 1.7.13344 (late 2013) FuseIT introduced the ability to customize the Salesforce endpoint by editing the environment connection string parameter:
<add name="S4SConnString" connectionString="S4S:user firstname.lastname@example.org;password=xxxxxxx;environment=Production" />
<add name="S4SConnString" connectionString="S4S:user email@example.com;password=xxxxxxx;environment=login.salesforce.com" />
For DEV, TEST, UAT, or STAGING servers that point to a Salesforce Sandbox no change is required however you can, for consistency, use the following string.
<add name="S4SConnString" connectionString="S4S:user firstname.lastname@example.org;password=xxxxxxx;environment=test.salesforce.com" />
Solution 2: Request an updated version from FuseIT
If your S4S is version 1.6.13186 or below you will need to email FuseIT and work through an upgrade process. Alternatively customers can download successive versions of S4S from our download server (use the credentials previously provided).
For customers with old S4S versions wishing to migrate to a later version, you may be impacted by BREAKING CHANGES. Customers implement the connector in different ways so the breaking changes may have no effect. If a breaking change is detected a developer will need to implement minor changes and migrate these through to production. If you have questions please contact us at email@example.com.