3

I am trying to simulate a backup and restore of a sandbox, before doing it in production. I need to export attachments from a source org to a target org. My problem is, when I export the Attachments, I get the files in binary format, but when importing, dataloader can't intrepret the file. I have to do it via dataloader, not via dataloader.io, because we are actually doing a backup using the standard schedule data export. And the files obtained are csv files. Has anyone been able to achieve this via dataloader only?

Improve this question
1

1 Answer 1

Reset to default
1

Not 100% sure I understand the question, but I have been able to take a weekly backup that includes attachments, and then load them into another org. If you include the attachments in the weekly backup, you also get a CSV for the attachments object that provides a link to those files. As long as the file path in the CSV matches where the files are and the parent ids exist in the system, they should load ok.

But - if you are doing a backup/restore, you'll need to link the old parent ids in the attachment csv to the new records you create as part of the restore I think? Also, I would reduce the batch size for the dataload to something like 5, because you quickly hit heap size limits.

Improve this answer
1
  • What i wanted was to be able to import an attachement/document using dataloader based upon extracted attachments/documents from dataloader itself. The biggest problem, is the content. I am getting the body in base64, which is quite normal, but the problem is that datalaoder can't upload it. Using the standard scheduled data export of salesforce, the documents is well generated into a csv and a folder with the contents, but not with dataloader. And i can't use the standard fucntionality because salesforce support told me that this is available only on production environment
    – vanessen
    Oct 5, 2015 at 13:44

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .