Skip to main content
Solved

Salesforce SOAP API login() Retirement

  • August 5, 2026
  • 6 replies
  • 89 views

jglick
Contributor
Forum|alt.badge.img+6

As per this post last year, Salesforce is retiring the SOAP API login().  Any news from FME on when the Salesforce readers and writers will be updated?  

Best answer by garethatsafe

Hi ​@johnglick82 thanks for bringing attention to this. I see you’d previously inquired about this, so I infer this is a matter of significant concern for your existing Salesforce integrations. 

I took a quick look at the internal ticket for this work and, while I can’t provide a specific timeline, can confirm that this change has been acknowledged and prioritized by our product development team.

As previously mentioned IDEA-2203 is our internal reference for this.

6 replies

garethatsafe
Safer
Forum|alt.badge.img+11
  • Safer
  • Best Answer
  • August 5, 2026

Hi ​@johnglick82 thanks for bringing attention to this. I see you’d previously inquired about this, so I infer this is a matter of significant concern for your existing Salesforce integrations. 

I took a quick look at the internal ticket for this work and, while I can’t provide a specific timeline, can confirm that this change has been acknowledged and prioritized by our product development team.

As previously mentioned IDEA-2203 is our internal reference for this.


garethatsafe
Safer
Forum|alt.badge.img+11

Hi ​@jglick following up on this, my colleague ​@desiree_at_safe clarified that the SalesforceConnector may be relevant here: it connects via OAuth2 and enables querying (no writing) of Salesforce data. Does this meet your needs, or are you also looking to write data?


jglick
Contributor
Forum|alt.badge.img+6
  • Author
  • Contributor
  • August 13, 2026

Hi ​@garethatsafe, writing is a requirement so the connector will not work in these cases.  


garethatsafe
Safer
Forum|alt.badge.img+11

Hey ​@jglick darn, I guessed as much. Thanks for confirming & have a great weekend!


desiree_at_safe
Safer
Forum|alt.badge.img+24

You might still be able to write and update records in Salesforce using the Salesforce REST API via the HTTPCaller transformer.

While I haven't set this up personally, here's a general guide to get you started:

  1. Authentication: Set up a Salesforce Web Connection in FME using OAuth 2.0 (see Salesforce's Authorization Through External Client Apps or Connected Apps and OAuth 2.0 guide).
  2. Creating/Updating Records: Check out Salesforce's Working with Records Guide. You can send JSON payloads to the REST endpoints:
    • POST to /services/data/vXX.0/sobjects/{sObject}/ to Create
    • PATCH to /services/data/vXX.0/sobjects/{sObject}/{Record_ID} to Update
    • PATCH to /services/data/vXX.0/sobjects/{sObject}/{Ext_ID_Field}/{Ext_ID_Value} to Upsert
    • DELETE to /services/data/vXX.0/sobjects/{sObject}/{Record_ID} to Delete
    A quick note on Upsert: it looks like the field you reference as {Ext_ID_Field} needs to be marked as an External ID field on the object in Salesforce first, or the call will fail.

A dedicated writer is definitely still the ideal long-term solution, and this ties into the same discussion tracked under IDEA-2203. In the meantime, hopefully this provides a workable path forward!

If you need any help setting this up, feel free to submit a Support Case with us. Hope this helps! 🙂 And thank you again for flagging this!


jglick
Contributor
Forum|alt.badge.img+6
  • Author
  • Contributor
  • August 22, 2026

Hi ​@desiree_at_safe.  Yes, that is an option and I use the REST API with HTTP callers in some cases.  The current writer supports bulk updates via the SOAP API, and should be updated to use the newer Bulk API.  And to clarify, I simply need to know that Safe is updating the current writer, so I know if I need to create a create a custom transformer for cases where the current writer is being used.  In any case there’s always a solution in FME, so I’m not worried, just need to plan 😊