This article shows you how to create a Salesforce custom object, then use Talend components to write and read data to a custom component.
To create a Salesforce custom object, you must have a Salesforce administration account.
Scroll down, and on the left-hand side, select Build > Create > Objects.
The Custom Objects window appears:
At the top of the table, click New Custom Object. The New Custom Object dialog appears:
Scroll down to the Custom Fields & Relationships section.
Click New to create a new field.
Select the data type for the field. For example, select data type text, as highlighted:
In this example, you will create a field named acct_firstname. It is not required and isn't unique, so it can contain a null value.
On this screen, set the security level for the acct_firstname field. Select Visible for all profiles.
Name the field acct_lastname. It is not required and is not unique, so it can contain a null value.
Click Next and set the field-level security by selecting Visible for all profiles.
Expand Administer > Manage Users > Profiles on the left-hand side.
Click Edit for the Profile Name for which you want to set the permission. For example, set the permission for the “Customer Support Team” profile:
Scroll down to the my_account_objects permission as shown below:
Select the boxes to set permissions for the group profile.
In this example, select all permissions.
Log in to the Salesforce workbench (https://workbench.developerforce.com/query.php) with the user login that belongs to the “Customer Support Team” to verify the my_account_objects permissions.
Note: when creating a Salesforce custom object and custom fields, Salesforce will append __c to custom objects and custom fields.Example: my_account_objects__c for custom objects and acct_firstname__c and acct_lastname__c for fields.
Use Talend components to write, then read, data from Salesforce custom object:
Verify data insertion in Salesforce my_account_objects__c by using Salesforce workbench:
This due to Salesforce setting a limited time of transaction, as shown in the link below:
The workaround is to limit the transaction to read/write data to Salesforce.