Messages and limitations of the Salesforce(deprecated) connector

Specification limits

• In order to perform data reading and writing with this connector, 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.

• You cannot use the COUNT() aggregate function. Please use instead COUNT(fieldName).

• COUNT(Id) will give the correct number of records.

• Cannot retrieve value from an address type field.

• The field value of junctionIdList will output the first record ID only.

• Location type field value cannot be retrieved after API34.0.

Notes

• When using aggregate functions, values in the log files may appear in exponential notation.

Specification limits

• In order to perform data reading and writing with this connector, 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.

Notes

• This operation cannot perform a rollback when an error occurs, unlike the database connectors. 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 a piece of data (constraint violation or invalid value, etc.), those errors cannot be detected by monitoring exceptions in a script.

  If you want to use the error information for each piece of data as data, you need to select Get in Whether or not to get result per rows and then 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.

• The data type is defined for the fields of the object. The API sends and receives data according to the defined data type format rules, but this connector extends the rules for some data types.

  = Remarks =

  For details, refer to Data type format.

Specification limits

• In order to perform data reading and writing with this connector, 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.

Notes

• This operation cannot perform a rollback when an error occurs, unlike the database connectors. 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 a piece of data (constraint violation or invalid value, etc.), those errors cannot be detected by monitoring exceptions in a script.

  If you want to use the error information for each piece of data as data, you need to select Get in Whether or not to get result per rows and then 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.

• As of the next API version, when Writing method is set to Update only and schema definition/key is true for a non-ID field, or when Writing method is set to Update and Insert, a MALFORMED_QUERY error will be thrown when a value is input the field specified to be the key beyond the precision of a Java Integer.

  • API 7.0

  • API 14.0

  • API 18.0

  • API 23.0

  Choose a field that differs from the key or use an API version newer than the above.

• From the next API version, if Writing method is set to Update and Insert and the relationship field definition is used for the Reference Type, an INVALID_FIELD error will be returned when the record's reference type value is set to null or an empty string.

  • API 14.0

  • API 18.0

  • API 23.0

  
  

  To write the value as null or an empty string, use an API version newer than the above.

• The data type is defined for the fields of the object. The API sends and receives data according to the defined data type format rules, but this connector extends the rules for some data types.

  = Remarks =

  For details, refer to Data type format.

Specification limits

• In order to perform data reading and writing with this connector, 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.

Notes

• This operation cannot perform a rollback when an error occurs, unlike the database connectors. 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 a piece of data (constraint violation or invalid value, etc.), those errors cannot be detected by monitoring exceptions in a script.

  If you want to use the error information for each piece of data as data, you need to select Get in Whether or not to get result per rows and then use the results data for handling error detection etc. in the subsequent processing.

• As of the next API version, when Writing method is set to Update only and schema definition/key is true for a non-ID field, or when Writing method is set to Update and Insert, a MALFORMED_QUERY error will be thrown when a value is input the field specified to be the key beyond the precision of a Java Integer.

  • API 7.0

  • API 14.0

  • API 18.0

  • API 23.0

  Choose a field that differs from the key or use an API version newer than the above.

• The data type is defined for the fields of the object. The API sends and receives data according to the defined data type format rules, but this connector extends the rules for some data types.

  = Remarks =

  For details, refer to Data type format.

Specification limits

• In order to perform data reading and writing with this connector, 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.

Notes

• This operation cannot perform a rollback when an error occurs, unlike the database connectors. 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 a piece of data (constraint violation or invalid value, etc.), those errors cannot be detected by monitoring exceptions in a script.

  If you want to use the error information for each piece of data as data, you need to select Get in Whether or not to get result per rows and then 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.

• If the field of the external key is specified as numeric type, and a value is written beyond the precision of the Java Double data type, the 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.

• The data type is defined for the fields of the object. The API sends and receives data according to the defined data type format rules, but this connector extends the rules for some data types.

  = Remarks =

  For details, refer to Data type format.

Specification limits

• In order to perform data reading and writing with this connector, 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.

• Cannot retrieve value from an address type field.

• Location type field value cannot be retrieved after API34.0.

Notes

• This field value will be obtained as null from the next API version when using a formula with a child-parent relationship field or when using a child-parent relationship field as an aggregate condition in a GROUP BY clause.

  • API 18.0

  • API 23.0

  When retrieving a field value, please use an API version newer than the above.

• The field value will be obtained as null when "toLabel" or "convertCurrency" functions are used with the following API version.

  • API 18.0

  • API 23.0

  • API 26.0

  When retrieving a field value, please use an API version newer than the above.

Specification limits

• In order to perform data reading and writing with this connector, 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 connector, 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.

Notes

• This operation cannot perform a rollback when an error occurs, unlike the database connectors. Succeeded data are updated while error data are left not to be updated.

  Therefore, if errors exist in a piece of data (constraint violation or invalid value, etc.), those errors cannot be detected by monitoring exceptions in a script.

  If you want to use the error information for each piece of data 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).

• The data type is defined for the fields of the object. The API sends and receives data according to the defined data type format rules, but this connector extends the rules for some data types.

  = Remarks =

  For details, refer to Data type format.

Specification limits

• In order to perform data reading and writing with this connector, 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 connector, 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.

Notes

• This operation cannot perform a rollback when an error occurs, unlike the database connectors. Succeeded data are updated while error data are left not to be updated.

  Therefore, if errors exist in a piece of data (constraint violation or invalid value, etc.), those errors cannot be detected by monitoring exceptions in a script.

  If you want to use the error information for each piece of data 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).

• The data type is defined for the fields of the object. The API sends and receives data according to the defined data type format rules, but this connector extends the rules for some data types.

  = Remarks =

  For details, refer to Data type format.

Specification limits

• In order to perform data reading and writing with this connector, 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.

• In this connector, 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.

Notes

• This operation cannot perform a rollback when an error occurs, unlike the database connectors. Succeeded data are updated while error data are left not to be updated.

  Therefore, if errors exist in a piece of data (constraint violation or invalid value, etc.), those errors cannot be detected by monitoring exceptions in a script.

  If you want to use the error information for each piece of data 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.

Specification limits

• In order to perform data reading and writing with this connector, 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 connector, 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.

Notes

• This operation cannot perform a rollback when an error occurs, unlike the database connectors. Succeeded data are updated while error data are left not to be updated.

  Therefore, if errors exist in a piece of data (constraint violation or invalid value, etc.), those errors cannot be detected by monitoring exceptions in a script.

  If you want to use the error information for each piece of data 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).

• The data type is defined for the fields of the object. The API sends and receives data according to the defined data type format rules, but this connector extends the rules for some data types.

  = Remarks =

  For details, refer to Data type format.

Specification limits

• In order to perform data reading and writing with this connector, 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.

• In this connector, 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.

Notes

• If the number of query result was zero (0), a message file "Records not found for this query" is stored on Salesforce server instead of CSV file.

  In this case, this operation does not output CSV file.

• If batch process is otherwise "Completed", this operation does not output CSV file.

• If an unexpected error occurs while writing to a CSV file, the content written up to the point of failure will not be Rolled Back. To allow for Rolling Back, please use the [Transaction] functionality.

• The format of the data written to the CSV file depends on the API specification.