Purpose
/SFDCINPUT defines a Salesforce.com object as a source of records.
/SFDCDATA defines a Salesforce.com object as an auxiliary source such as a lookup source.
Format
/SFDCINPUT connection {object_extract|soql_extract}
/SFDCDATA connection object_extract
where
| object_extract | = | OBJECT object_name [FIELDS field [,field...]] [ALIAS alias] |
| soql_extract | = | QUERY soql_text extract_options ALIAS alias |
Arguments
| connection | The value that identifies the Salesforce.com connection defined through /SFDCCONNECTION. This connection value must match either the alias defined for the service URL or, if an alias were not defined, a string of the service URL as defined in / SFDCCONNECTION. |
| object_name | The name of the Salesforce.com object that is the source of records. The name can be in the form of a string or identifier. |
| field | The name of a field to be extracted from the object. The name can be in the form of a string or identifier. |
| soql_text |
A SOQL statement in the form of a string. You can provide the string in any valid format. For a summary of valid naming and formatting conventions for identifiers and constants, see Syntax reference in the Connect help. The result of executing the statement should be the set of records that defines the Salesforce.com object source. You must define a field alias in the SOQL statement. |
| alias |
A name you assign to the Salesforce.com object. You can use this alias name to reference the object from other options. The name must adhere to the rules described for an identifier. For a summary of valid naming and formatting conventions for identifiers and constants, see Syntax reference in the Connect help. When you do not assign an alias, use the object_name argument to reference the object in other options. An alias is mandatory when the source of records is defined via an SOQL statement (i.e., SoQL soql_text). It is optional when the source is defined via an object (i.e., OBJECT object_name). When you define an alias for the source reference the source only through the alias; you can no longer reference the object directly in other options. |
Location
The option may appear anywhere in the task definition.
Character encoding
If the character encoding is not set when extracting a text column from a database table, Connect ETL attempts to extract the text column in the database server’s character encoding. When Connect ETL does not support the database server’s character encoding, Connect ETL extracts the column in locale encoding. A column extracted in locale encoding could be extracted differently when Connect ETL expands the encoding support in a future release.
To prevent the possibility of output being changed in a future Connect release, define the character encoding for the target or for each extracted text column.