Starting November 20, the site will be set to read-only.
On December 4, 2023,
Apex Code Development (90768)
General Development (55146)
Visualforce Development (37251)
Lightning (18265)
APIs and Integration (17146)
Trailhead (11680)
Formulas & Validation Rules Discussion (11337)
Other Salesforce Applications (8116)
Jobs Board (6655)
Force.com Sites & Site.com (4842)
Mobile (2694)
You need to sign in to do that
Don't have an account?
Depton Hi guys,
I updated a file with 50 rows and got the "40 succeed" but "0 errors"
I have then put separately the 10 rows and I got "0 success" and "0" errors
Did you ever had the same issue, no error, no update.
I have full privileges.
Is there anything in the monitoring set up that might help me to check if there is any trigger or "whatever" not allowing me to do the update!
Is the first time I am having this issue???
Got it!
I checked the 7 rows that were not being recognised and realised that one of the date fields had text data instead
I still think that this is unusual, I am pretty sure that before when I got this kind of errors, the data loader was giving me some help.
I am running data loader version 22, but even with that, it is unusual this behaviour........well...
Fixed it so thank you very much!
All Answers
I think it happens if you have some bad characters or formatting error in your csv file at 41st row, please check the 41st row.
It sounds like you have the data loader settings configured so that it's starting the data load at line 11. Check your settings, at the bottom of the settings page, where it says "the last batch finished at [###] Use [###] to continue from your last location."
Hi Guys,
Thanks for the help!
I have checked both things and nothing..Start row is 0 and also I have checked the file, copy and paste it in a new one, saved it as txt and then back to CSV's.....Nothing...
When I open the file I got the SYLK: File format is not valid error, but that happened to me for years and never had this issue with random rows!!!
I have investigate further and the rows that fail are the 13,14, 17, 33,34, 43....still looking for the other ones..So don't know what else I can do!!
I have updated one of the records manually without a problem.
Will keep trying!
A good test is to see how many rows Data Loader thinks are in the file. When you are starting the load and you select your csv file, you should receive a pop-up saying:
Initialization succeeded
Your operation will contain ## records
Where ## is the number of rows in your file. When you do the load, does this say 50 records? If it says less than 50, then it sounds like the file is corrupt in some way.
Other than that, the other responses seem like they could be the issue, but if you have tested I am not sure.
If it does say 50 records, can you please create a support case and attach your file to the case? Then respond to this thread with the case # and I will take a look.
Hope this helps.
Jay
Thanks Jay,
But I have to follow internal procedure, maybe tomorrow morning I will create a case.
The file exactly contains 48 rows so data loader said
Your operation will contain 47 records (first one for the columns as always)
Thanks again guys!
image link:
http://www.freeimagehosting.net/hrmc6
Got it!
I checked the 7 rows that were not being recognised and realised that one of the date fields had text data instead
I still think that this is unusual, I am pretty sure that before when I got this kind of errors, the data loader was giving me some help.
I am running data loader version 22, but even with that, it is unusual this behaviour........well...
Fixed it so thank you very much!
That is very strange.
Feel free to open the cased tomorrow, and we can follow up to see if it is a bug with the Data Loader.
Thanks again
Jay
Object names are out of sync with configuration. Please contact the administrator.
During data loading I am getting the above error
Please help me in solving that error