Designing a job to load binary objects into Salesforce.com

The Salesforce.com connector supports uploading attachment or document type to Salesforce.com using a flat file in Real-time Load Access Method for the Update and Create operations.

1. Create a Salesforce.com connector load job.
2. In the InfoSphere® DataStage® and QualityStage® Designer client, create a new parallel job.
3. In the Designer Client Palette, click Packs and drag the Salesforce.com connector stage into the Parallel Canvas.
4. In the Designer Client Palette, click File and drag a sequential file stage to the parallel canvas.
5. To define the job as a load job, draw an output link from sequential file stage to the Salesforce.com connector stage.
6. Double-click the Pack for Salesforce.com stage to open the link properties.
7. Specify your Salesforce.com login credentials and URL, or load them from a saved connection file.
8. In the Write Operation property, select a Write operation which could be either Update or Create.
9. In the Access Method property, select Real-time load.
10. Click the Large Object Operation category.

Example

Note: 1. The new category Large Object Operation is enabled when you select real-time operation with Create and Update operations. 2. Select Yes for the property Enable Load or Extract Large Object via flat file, so that uploading binary files using the flat file is enabled. 3. Update the Flat File Column Name as this functionality supports loading large object through flat files. 4. The Flat File Column Name must be defined as Base64 binary field, such as the Body field that needs the data to be uploaded onto this field in Salesforce.com such as the Body field in an object on Salesforce.com. 5. You must define the flat file location in the input sequential file for the Base64 field, for example in the Body field as mentioned earlier. 6. It does not support UNC or remote file locations. It supports loading files from direct file location.

Note: When you are designing a Create job following fields are required:

Body:

This field defines the binary file location. For example, C:\\attachInput\\i46depsf.pdf.

Name:

This field describes the name of the attachment or document type. For example, i46depsf.pdf.

ParentId:

ID of the parent object of the attachment. ParentId is for attachment objects only, not for document objects, as unlike attachment objects, documents are not attached to a parent object.

Note: When you are designing an Update job following fields are required:

Body:

This field defines the binary file location. For example, C:\\attachInput\\i46depsf.pdf.

Name:

This field describes the name of the attachment or document type. For example, i46depsf.pdf

Id:

ID field of Attachment.

Example Job

Some example values for the Body, Name, and ParentId fields from the input sequential file are:

C:\\sfqa\\attachInput\\i46depsf.pdf,i46depsf.pdf,0017000000O902EAAR
C:\\sfqa\\attachInput\\IS_QuickStartGuide.pdf,IS_QuickStartGuide.pdf,0017000000O902FAAR
C:\\sfqa\\attachInput\\SALESFORCEJCConnector.bmp,SALESFORCEJCConnector.bmp,0017000000OEZ7VAAX

Note: In the example, only required fields are mentioned for the Objects. The schema can contain other fields that are permitted by the Objects