Eloqua Bulk API Connector > Mappings and mapping tasks with Eloqua Bulk API Connector > Eloqua Bulk API Targets in Mappings
  

Eloqua Bulk API Targets in Mappings

You can use an Eloqua Bulk API object as a single target in a mapping. When you write data to Eloqua Bulk API, you can map up to 100 fields to the target.
You configure Eloqua Bulk API source properties on the Target page of the Mapping Task wizard.
The following table describes the Eloqua Bulk API target properties:
Property
Description
Batch Size
You can write or upsert data in a batch to Eloqua. Specify the number of rows to upsert in a batch to Eloqua.
Auto Delete of Definitions
When you enable the Auto Delete of Definitions option, the Secure Agent deletes the definitions after the duration specified by Eloqua Bulk API 2.0.
Duration for Auto Delete of Definitions
When you do not enable the Auto Delete of Definitions option, specify a value in this field. The Secure Agent uses the value you specify to delete the definitions.
If you do not enable the Auto Delete of Definitions option and do not provide any value for duration of deleting the definitions automatically, the default value is P7D, which stands for seven days.
Duration for Data Retention
When you do not enable the Auto Delete of Definitions option, specify a value in this field. The Secure Agent uses the value you specify to retain the data definitions.
If you do not enable the Auto Delete of Definitions option and do not provide any value for duration of retaining the data, the default value is P2D, which stands for two days.
Identifier Field Name
Mandatory. The Secure Agent searches for the specified identifier field name in the Eloqua application and the imported data.
By default, the field is empty.
If you specify a field that is not a part of the field list in the Identifier Field Name field, the Secure Agent considers the following default values for the Account and Contact objects:
  • - For Account object, the default value is M_Company.
  • - For Contact object, the default value is C_EmailAddress.
For custom object, the following error message occurs: 'Identifier Field Name:' Must be a string value, at least 1 character and at most 100 characters long and must be contained within fields.
Update Multiple Matched Records
When the connector fetches the records associated with the sepcified Identifier field name, the Secure Agent updates the matched records. You must set the Update Multiple Matched Record field to true to update the records.
Default value is false.
Map DataCards SourceField
The field name to map with the related object. The default value is the email address of the Contact object.
To upsert data, you need to map the Map DataCards SourceField in the field mapping.
The field that you map must be a child object field.
Map DataCards CaseSensitive Match
Performs a case-sensitive search when you map custom object records to a contact.
Success File Directory
Directory for the success file. Specify a directory path that is available on each Secure Agent machine in the runtime environment. By default, Data Integration writes the success file to the following directory:
<Secure Agent installation directory>/apps/Data_Integration_Server/data/success
Error File Directory
Directory for the error rows file. Specify a directory path that is available on each Secure Agent machine in the runtime environment. By default, Data Integration writes the error rows file to the following directory:
<Secure Agent installation directory>/apps/Data_Integration_Server/data/error
You can use Contact as a related object to a custom object. When you use Contact as a related object, specify the following target connection properties:
Note: When you upsert data in the Account, Contact, and custom objects, the Secure Agent upserts data depending on the value of the Batch Size field that you specify in the target properties. For example, if you specify the value of the Batch Size field as 50, the Secure Agent upserts 50 rows in each batch.