Bulk Write Data(Insert)

Operation Name

Function Overview

• "Salesforce Developer Documentation"-(https://developer.salesforce.com/docs)
  • Bulk API Developer's Guide

Data Model

Properties

Basic Settings

Required Settings

Property Action

Item name	Description	Supplement
Create Schema...	Allows the addition and deletion of the items for the CSV data's header row to be registered with the batch. Please refer to Create Schema for setting methods.

Bulk Operation Settings

Option Settings

Property Action

Item name	Description	Supplement
Display Table Information...	You can check the table structure of the object you are operating. For more information on how to view the table structure, please refer to Display Table Information	Click [Load All Table Information....] if you would like to check the table structure of other objects.
Load All Table Information	Retrieve all possible table information After running, you can verify the retrieved information from [Table Information].
Read schema definition from file...	Select a file from the file chooser and read the name of field API on the first line of the file specified in the comma-separated values. Set this as the schema definition.	Please specify "UTF-8" encoding for the selected file.

Large Data Processing Settings

Comment

Schema

Input Schema

Output Schema

<?xml version="1.0" encoding="UTF-8" ?>
<table>
  <row>
    <column>Label/API set in the [Schema Definition]</column>
       :
    <column>RESULT_inputRowNumber</column>
    <column>RESULT_BATCH_id</column>
    <column>RESULT_BATCH_state</column>
    <column>RESULT_BATCH_stateMessage</column>
    <column>RESULT_ROW_id</column>
    <column>RESULT_ROW_success</column>
    <column>RESULT_ROW_created</column>
    <column>RESULT_ROW_error</column>
  </row>
  <row>
    :
  </row>
</table>

Reading Schema by Mapper

Large Data Processing

Transaction

Usage on PSP Script

Available Component variables

Process Flow

Usage Examples of Get Results

• Example: The updating results after [Bulk Write Data(Upsert)] to the "Account" is output to a CSV file.
  
  
  
  

  Number in the Image	Name	Description	Supplement
  (1)	Input Data Image	This is a sample image of data input, for updating to the "Account". Here, the [External ID field]is designated as "AccountCode__c".
  (2)	Settings for updating to the "Account"	Here, the setting is done using the [Bulk Write Data(Upsert)].
  (3)	Setting to obtain or not obtain the data of batch processing results	Here, [Obtain the batch results after waiting until the task is completed] is checked in the [Bulk Operation Settings] tab.
  (4)	Script Image	This is the script implementation image of this description.
  (5)	Resulting Data Mapping Image	The result data, from update to "Account", is read, and the data required for mapping is passed on to the subsequent processing.
  (6)	Resulting Data Image	This is the resulting data image obtained output as CSV file when updated to the "Account".

Relationship definition

• Example: Updating (Insert, Update, Upsert) the "Contact"
  
  
  • Details of the example
    
    

    Category	Description	Supplement
    Specification Requirements	Regarding to the update processing of "Contact", it needs to set the referring object ID in the the "Account" ID item (Reference Item). As for the relationship to the referring "Account", it needs to tie to the record according to the AccountCode of the input data.
    Settings	Upon updating to "Contact", by passing the value of the Account Code (External key item created before hand: AccountCode__c) of the "Account", which is the referred object, to Mapper, the ID of the corresponding referred object is automatically obtained and set the relationship to the "Account" ID Item (Reference Item).	The items and some of the settings used in this description are usage examples. This is something that is not always in the Salesforce organization that you are using. Please use this function after adjusting and verifying your settings.

    
    
    
  • Coordination Image
    
    
    
    

    Number in the Image	Name	Description	Supplement
    (1)	The Data Image of the "Account"	This is the data image of the object which is refered by the "Contact".
    (2)	The External Key of the "Account"	Pre set "AccountCode__c" as external key.
    (3)	Data Input Image	This is the data input image, for updating to the "Contact".	This is the data which has the "Account Code".
    (4)	Settings for the updating (Insert, Update, Upsert) to the "Contact".	Here, the "Account ID", "Last Name", "First Name", "E-mail" are the four considered items for updating.
    (5)	Relationship Definition Setup	The external key of the referred object in "Foreign key field" should be selected. Here, the external key "Account.AccountCode__c" is selected as the key item for setting the relationship.	If no value is selected, the ID of the corresponding record of the referred object will be passed to Mapper.
    (6)	The Updating Results Data Image of the "Contact"	This is the updating results data image of the "Contact".	The relationship is correctly setup to accomodate the record that responded to the "Account Code".

Create Schema

Display Table Information

Specification Limits

• In order to perform data reading and writing with this adapter, API's of Salesforce organization must be published.


• All permissions for reading/writing data and other operations, as well as data access control, depend upon the profile, shared rule setting and API specifications in Salesforce.


• The objects and fields that can be used may differ by API version. For details, please refer to the Salesforce documentation.


• An item whose data type is "base 64" cannot be handled in this component.


• In this adapter, the job contet type "CSV" is used.
  It is not possible to create a job with another contet type, or to create batches for jobs with other content types.

Main exceptions

Notes

• This operation cannot perform a rollback when an error occurs, unlike the database adapters. Succeeded data are updated while error data are left not to be updated.
  Therefore, if errors exist in units of data (constraint violation and invalid value, etc.), those errors cannot be detected by monitoring exceptions in a script.
  If you want to use the data-level error information as data, [Obtain the batch results after waiting until the task is completed] must be checked and then use the results data for handling error detection etc. in the subsequent processing.


• If a value is written beyond the precision of the Java Double data type, the value will be rounded by the Bulk API.
  For example, if the value (1,234,567,890,123,456.78) is written to a numerical (16,2) field, it will be saved as (1,234,567,890,123,456.80).