Write Multi Data

Operation Name

Function Overview

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

Data Model

Properties

Basic Settings

Required Settings

Property Action

Option Settings

Item name	Required/Optional	Use of Variables	Description	Supplement
Encoding	Required	Available	Select or input the character encoding of the file to be read. When input, you can specify encode supported in Java SE Runtime Environment. Refer to "Supported Encodings"(http://docs.oracle.com/javase/7/docs/technotes/guides/intl/encoding.doc.html) for details.	For default values, please refer to Default Encodings.
Base64 field input form	Required	Not Available	Specify the input data type of items in Base 64 data type. [Base64 data]:(default) Base64 Data is inserted. [File path]: File path is inserted.	If you select [file path], please specify absolute path on the DataSpider File System. If you select [file path], the prohibited characters on the DataSpider File System except for the path delimiter "/" cannot be used.
Number of input data fields to be added to the output schema	Required	Not Available	Select the number of input data items to be added to output schema. [0]:(default) The input data schema is not displayed. [1-30]: The selected number of schemata are added.	If the number of 1 or more is selected, the selected number of schemata named [input_value_column_index(n)] are displayed in the output schema. The values of the input data items are set in the order of rows from the beginning. If the number of items is less than the selected value, the remaining schema will be set by null. Please refer to Schema about the schema to be added.

Large Data Processing Settings

Comment

Schema

Input Schema

Output Schema

<?xml version="1.0" encoding="UTF-8" ?>
<table>
  <row>
    <column>result_id</column>
    <column>result_is_success</column>
    <column>result_error_status_code</column>
    <column>result_error_message</column>
    <column>result_row_number</column>
    <column>target_object</column>
    <column>input_value_column_index1</column>
    :
    <column>input_value_column_index30</column>
  </row>
  <row>
    :
  </row>
</table>

Reading Schema by Mapper

Large Data Processing

Transaction

Usage on PSP Script

Available Component variables

Usage Example of Writing Multi Data

• Example: Multiple writing of "Account" and "Contact" records is performed by one Insert call.
  
  
  • Details of the example
    

    Category	Description	Supplement
    Specification Requirements	One record of "Account" data and multple records of "Contact" data that are tied to the "Account" data need to be written. If any of data writing fails, it needs to be handled as failure-for-all.	Input data are 200 records or less.
    Settings	A file is output by the [Generate Multi Data File] process, in the order of "Account" data and then "Contact" data. An updating is performed by the [Write Multi Data] process, based on the contents of the output file. Specify [Checked] in [AllOrNone Header (allOrNone)] of the global resource property.	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)	Data Input Image	This is the data input image, for writing to the "Account".
    (2)	Data Input Image	This is the data input image, for writing to the Contact. Here, "Account.AccountCode__c" is specified in the [Relationship definition]
    (3)	Settings for Creating Multiple Data File	Each input data (1) and (2) is written to a file in this order by the [Generate Multi Data File] process. Specify "/data/Sample.csv" as [Output File] for both.	For details, please refer to Order of Records and Chunk.
    (4)	Script Image	This is the script implementation image of this description.
    (5)	Settings for Writing Multiple Data	An update is performed based on the file with accumulated data by the [Write Multi Data] process . Specify "/data/sample.csv" as [Input file] Specify "3" for [Number of input data fields to be added to output schema].
    (6)	Result Data Writing Mapping Image	This is the mapping image of outputting the result data to a CSV file after writing. Since the number "3" is specified for [Number of input data fields to be added to output schema] in (5), the values of the input data items can be handled up to three items from the beginning as well as the results data.
    (7)	Resulting Data Image(With allOrNone)	This is the resulting data image of writing with the setting of [Checked] for [AllOrNone Header(allOrNone)] in the global resource property. If one or more errors occur regarding the data in a Insert call, all records in the same call will be rollbacked.
    (8)	Resulting Data Image(Without allOrNone)	This is the resulting data image of writing with the setting of [Not Checked] for [AllOrNone Header(allOrNone)] in the global resource property. Even if one or more errors occur regarding the data in a Insert call, a rollback will not take place and the records updatings become effective.

Order of Records and Chunk

• Example; In the case that the data is accumulated in the order of the object type below.
  
  

  Account 1, Account 2, Contact 1, Contact 2, Contact 3, Case 1, Account 3, Account 4, Contact 4

  
  The divided chunks are below.
  • Chunk 1: Account 1, Account 2
  • Chunk 2: Contact 1, Contact 2, Contact 3
  • Chunk 3: Case 1
  • Chunk 4: Account 3, Account 4
  • Chunk 5: Contact 4

Multi Data File Format

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.

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 and the processing log in WARN level is output.
  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, use the results data for handling error detection etc. in the subsequent processing.


• If the Foreign key field in the relationship definition is specified as numeric type, and a value is written beyond the precision of the Java Double data type, the result value will be rounded.
  Specify the field as text type to avoid the value from rounding off.


• As of the next API version, If a value is written beyond the precision of the Java Double data type, the value will be rounded.
  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).
  • API 7.0
  • API 14.0
  • API 18.0
  • API 23.0
  To write the value without rounding, use an API version newer than the above.