SOAP Login() retirement (Summer27) and Windows CLI

[colinkenworthy]

Bearing in mind the announced retirement of SOAP Login() in Summer'27, are there any plans to keep Data Loader working from the Windows Command Line? When I check in the Org, it logs in with a SOAP Login. Will it be possible to make a version using Oauth Client Credentials in time for the retirement?

[jwesterman-salesforce]

Yes, we will provide a solution prior to the retirement of SOAP API login().

Would be interested to know how you use the Data Loader CLI.

• Do you use it interactively or with scripts for automated execution?
• If automated, how is the execution triggered?
• Any other details of your use case you feel comfortable sharing?
  It's useful for us to know how it is being used. Thanks.

[Petera-tokara]

My use case is primarily an initial load from an old 3rd party CRM system, essentially for migration from the old system to Salesforce. However, I need to do this many times into test sandboxes and eventually into the main production org so the process is fully validated and repeatable

I use it both interactively (using the DataLoader UI) and extensively in batch mode, driven primarily by Powershell scripts, although I invoke PS manually through the windows Terminal.

Similar to other posters I modify the config.properties with the encrypted username and password, but then I have a large process-conf.xml which does not include the credentials. My powershell scripts selectively invoke process.bat one bean at a time in the appropriate sequence.

[colinkenworthy]

We use the encrypt.bat to set up the credentials file,
We make some process-conf.xml files containing e.g an upsert.

Upsert job gets the record updates from a CSV file and uploads them to salesforce using 'upsert'.

          class="com.salesforce.dataloader.process.ProcessRunner"
          singleton="false">
        <description>Upsert job gets the record updates from a CSV file and uploads them to salesforce using 'upsert'.</description>
        <property name="name" value="fileUpsertProcess"/>
        <property name="configOverrideMap">
            <map>
                <entry key="sfdc.endpoint" value="https://login.salesforce.com"/>
                <entry key="sfdc.username" value="xxxxxxx@xxxxxxx.com"/>
                <!-- password below has been encrypted using key file, therefore it will not work without the key setting: process.encryptionKeyFile
                the password is not a valid encrypted value, please generate the real value using encrypt.bat utility -->
                <entry key="sfdc.password" value=".....4ffdc29ebccc.....a96c2c3b0947be44c0749e9c6.....8a53a3c5a70d57566a04c69d1.....909b25b6ed148376c7271"/>
                <entry key="process.encryptionKeyFile" value="c:\Users\xxxxx\.dataloader\dataLoader.key"/>
                <entry key="sfdc.timeoutSecs" value="600"/>
                <entry key="sfdc.loadBatchSize" value="200"/>
                <entry key="sfdc.externalIdField" value="ExtId__c"/>
                <entry key="sfdc.entity" value="CustObj__c"/>
                <entry key="process.operation" value="upsert"/>
                <entry key="process.mappingFile" value="c:\Users\xxxxx\dataloader\v47.0.0\configs\xxxxx\fieldMapping.sdl"/>
                <entry key="dataAccess.name" value="c:\Users\xxxxx\dataloader\v47.0.0\configs\xxxxx\MyList.csv"/>
                <entry key="dataAccess.type" value="csvRead"/>
                <entry key="process.initialLastRunDate" value="2006-12-01T00:00:00.000-0800"/>
            </map>
        </property>
    </bean>```
Then in windows we schedule a daily task to run process.bat picking up the correct xml file.
Basically straight out of the documentation and /samples/conf/ folders.

[ColinBuckley765486]

Hi

I use the same process as described in the first post by Colin Kenworthy.
Windows PC monitoring files being dropped into a folder, which then triggers 1 of 4 different file uploads routines.
8 file uploads / day, approx 40000 rows of data / day.

Its all automated.

Cheers