|
Component family
|
Business/Salesforce
|
|
|
Function
|
This component loads data into Salesforce Analytics Cloud from a
local CSV file.
|
|
Purpose
|
This component allows you to load data into Salesforce Analytics
Cloud from a local file.
|
|
Basic settings
|
Property Type
|
Either Built-In or Repository.
Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.
|
|
|
|
Built-In: No property data stored
centrally.
|
|
|
|
Repository: Select the repository
file in which the properties are stored. The connection fields that
follow are completed automatically using the data retrieved.
|
|
|
User Name and Password
|
Enter the Web service authentication details.
To enter the password, click the […] button next to the
password field, and then in the pop-up dialog box enter the password between double quotes
and click OK to save the settings.
|
|
|
End Point
|
Enter the WebService URL required to connect to Salesforce. For
example, https://login.salesforce.com/services/Soap/u/32.0.
Note that the version in the URL should be 32.0 or later.
|
|
|
Schema and Edit schema
|
A schema is a row description. It defines the number of fields to be processed and passed on
to the next component. The schema is either Built-In or
stored remotely in the Repository.
-
For the fields of numeric type (for example, byte, short,
int, long, float, double, and BigDecimal), their length and
precision values need to be specified. The default length
and precision values are 10 and 2,
and you can also specify their custom values in the schema
editor.
-
For the fields of date type, you need to specify the
format of the date in the schema editor. For more
information about the supported date format, see Analytics Cloud External Data Format
Reference.
Since version 5.6, both the Built-In mode and the Repository mode are
available in any of the Talend solutions.
The Schema list and the Editor schema button disappear if the
Custom JSON Metadata check box
is selected.
|
|
|
|
Built-In: You create and store the schema locally for this
component only. Related topic: see Talend Studio
User Guide.
|
|
|
|
Repository: You have already created the schema and
stored it in the Repository. You can reuse it in various projects and Job designs. Related
topic: see Talend Studio User Guide.
|
|
|
|
Click Edit schema to make changes to the schema. If the
current schema is of the Repository type, three options are
available:
-
View schema: choose this option to view the
schema only.
-
Change to built-in property: choose this option
to change the schema to Built-in for local
changes.
-
Update repository connection: choose this option to change
the schema stored in the repository and decide whether to propagate the changes to
all the Jobs upon completion. If you just want to propagate the changes to the
current Job, you can select No upon completion and
choose this schema metadata again in the [Repository
Content] window.
|
|
|
Operation
|
Select an operation to perform on the dataset:
-
Append: Append all data
to the dataset. Create a dataset if it does not
exist.
-
Upsert: Insert or update
rows in the dataset. Create a dataset if it does not
exist.
-
Overwrite: Create a new
dataset with the given data, and replace dataset if it
already exists.
-
Delete: Delete the rows
from the dataset.
Note
-
A metadata JSON file is required for the Append, Upsert, and Delete operations.
-
The data and metadata for the Append and Upsert operations must match the dataset
on which the operation is happening. All columns,
dimensions, and measures must match exactly.
-
The Append operation
is not allowed if you specify any column as the primary
key.
-
You must specify one (and only one) column as the
primary key on which the Upsert or Delete operation is based. You can do
that by clicking Edit
schema and selecting the check box next
to the column you want to set as the primary key.
-
The metadata for the Delete operation must be a subset of the
dataset columns.
|
|
|
Name
|
Type in the name of the dataset into which the data will be
loaded.
|
|
|
CSV File
|
Specify the path to the local CSV file to be loaded.
|
|
Advanced settings
|
Encoding
|
Select an encoding type used to generate the JSON metadata file
that describes the structure of the data to be loaded.
|
|
SalesforceWave Metadata Descriptor
|
Auto Generate JSON Metadata Description
|
Select this check box to generate the JSON metadata description
automatically.
|
|
|
Header
|
Specify the number of lines to ignore in the CSV file.
This field appears only when the Auto
Generate JSON Metadata Description check box is
cleared.
|
|
|
Unique API Name
|
Specify the unique API name for the object in the JSON metadata
description.
This field appears only when the Auto
Generate JSON Metadata Description check box is
cleared.
|
|
|
Label
|
Specify the display name for the object in the JSON metadata
description.
This field appears only when the Auto
Generate JSON Metadata Description check box is
cleared.
|
|
|
Fully Qualified Name
|
Specify the full path that uniquely identifies the record in the
JSON metadata description.
This field appears only when the Auto
Generate JSON Metadata Description check box is
cleared.
|
|
|
Custom JSON Metadata
|
Select this check box to use a customized JSON metadata
file.
This check box appears only when the Auto
Generate JSON Metadata Description check box is
cleared.
|
|
|
JSON Metadata
|
Specify the path to the customized JSON metadata file.
This field appears only when the Custom JSON
Metadata check box is selected.
|
|
|
Generate JSON in File
|
Select this check box to write the JSON metadata description in a
local file.
This check box disappears when the Custom
JSON Metadata check box is selected.
|
|
|
Folder
|
Specify the directory where you want to store the generated JSON
metadata file.
This field appears only when the Generate
JSON in File check box is selected.
|
|
|
tStatCatcher Statistics
|
Select this check box to gather the Job processing metadata at the
Job level as well as at each component level.
|
|
Global Variables
|
ERROR_MESSAGE: the error message generated by the
component when an error occurs. This is an After variable and it returns a string. This
variable functions only if the Die on error check box is
cleared, if the component has this check box.
A Flow variable functions during the execution of a component while an After variable
functions after the execution of the component.
To fill up a field or expression with a variable, press Ctrl +
Space to access the variable list and choose the variable to use from it.
For further information about variables, see Talend Studio
User Guide.
|
|
Usage
|
This component can be used as a standalone component.
|
