function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
RP@TranseraRP@Transera 

Unable to delete records using the command line version of DataLoader

Well, I can update records and extract them but I'm having a problem deleting them
 
BTW, this is happening on the windows & linux command line programs BUT doesn't happen when I use the GUI version!
 
I run an extract to generate a .csv file I want to use for delete.  I have a good .sdl file and the .csv file generated from the extract will run deletes when using the GUI version of the data loading too.
 
The password is passed in on the command line...
 
I'm using the Id to delete the records. 
 
SDL file
=================
#Mapping values
#Thu Apr 20 15:59:40 PDT 2006
ID=Id
 
config.properties
==================
#Loader Config
password=
outputError=error.csv
extractionSOQL=
queryRequestSize=500
username=xxxxxx@xxx.com
endpoint=
extractionTarget=daily_calls_extract.csv
mappingFile=daily_calls_delete.sdl
operation=delete
entity=Daily_Calls__c
assignmentRule=
dataAccessObject=daily_calls_extract.csv
batchSize=200
lastBatchRow=0
outputSuccess=
rowToStartAt=0
outputDirectory=
insertNulls=false
 
Sample from the .csv file
=====================
"ID"
"a0730000000VshsAAC"
"a0730000000VshtAAC"
 
 
 
Anyone here have any ideas?
 
 
Trace from the command line too.
===============================

        at com.sforce.soap.partner.SoapBindingStub.describeSObject(SoapBindingStub.java:1170)
        at com.salesforce.lexiloader.client.PartnerClient.setFieldTypes(PartnerClient.java:343)
        at com.salesforce.lexiloader.controller.LoaderController.setFieldTypes(LoaderController.java:109)
        at LoaderEngineRunner.main(LoaderEngineRunner.java:105)
2145 [main] INFO LoaderEngineRunner  - Creating Map
2153 [main] INFO LoaderEngineRunner  - About to perform delete
Exception in thread "main" java.lang.NullPointerException
        at com.salesforce.lexiloader.controller.LoaderController.executeAction(LoaderController.java:103)
        at LoaderEngineRunner.main(LoaderEngineRunner.java:115)
[root@tiger download]#

EnderEnder
Change your config file operation from "delete" to "deletes"  -- Yes, I know its stupid.  Yes, there should be a better debug message.




RP@TranseraRP@Transera

Thanks for the reply. changing it to 'deletes' doesn't work.  Actually I can type anything in there and it will echo it back and then throw an exception.

What's the next thing the program tries to do after this?  its already logged in and check to verify the file exists.  does it try to parse the file next?  If I had some idea I may be able to resolve this!!

Any help here would be great.

 

 

shapoorshapoor
I don't see an endpoint specified in your config.properties file.  The doc says that you should execute a delete operation using the GUI and then use the config file generated from the GUI operation as a template for your CLI usage.