[SalesForce] Data Loader v38 (Winter 17)

I just downloaded Data Loader 38.0.0. The login has changed – instead of popping up a web window to log in, it just asks for user name, password and login URL (default is login.salesforce.com). I've tried both the production instance I'm trying to load to and my dev org. Neither has trusted IP ranges so security tokens should not be an issue. Nonetheless I get Error: Check your username and password. If you still can't log in, contact your Salesforce admin.

The only login flow available to me in v38 is direct password authentication. I am offered OAuth in v37 and it works fine.

Any thoughts? Why was OAuth removed from v38?

Best Answer

As commented by Charles, v38.0.1 is now available:

DataLoader V38.0.1 fixed Oauth option missing issue caused by release script and a bug in field mapping UI after sorting by column names.

Partial answer, to at least get you going until the missing OAuth authentication can be resurrected.

You will need to append your security token to the end of the password unless your current IP address is listed under Trusted IP Ranges.

Conversely, if the Organization has restricted IP addresses enabled you will only be able to login from those IP addresses and you won't need the security token.

I'll try pinging the Salesforce Docs team to see if they can clarify the confusing point in the Data Loader documentation.

Caspars comment with the link to the Github project would be a good place to raise the missing OAuth issue.

Issue created by Mohith - New Version 38.0 of dataloader has oauth option missing

Randomly searching the projects code, it occurs to me that it will need to have access to the OAuth Client secret to get the flow started as the correct connected app. You can see this at line 86 of AuthenticationRunner. If the sfdc.oauth.clientsecret was missing from the config then you wouldn't even get the OAuth option.

Related Solutions

[SalesForce] Data Loader Stuck

I had the same issue. I used the salesforce export csv file and at the bottom of the csv it had junk values such as the name of the report and the salesforce copyright info. Just delete.

Sample output at end of the CSV

[SalesForce] Challenging scenario while implementing a trigger

When we want to distinguish record creation between data loader and User Interface we generally prefer to create a new boolean field on an object and set that field value as true while inserting data using dataloader and make that field as false from user interface.

trigger Atrigger on employee__C( after insert, before update){

if(Trigger.isInsert){
// create log record with incident field value as new employee

    if(employee__c.isBulkUpload){
         //set incident as inactive.
    }

}

if(Trigger.Isupdate){

// create log record and check if the status in inactive/active and create the //log accordingly
// check for

}

}

Best Answer

Related Solutions

[SalesForce] Data Loader Stuck

[SalesForce] Challenging scenario while implementing a trigger

Related Topic