Uploading multiple custom object records
You can use Oracle Eloqua's Custom Object Records Upload Wizard to add or update custom object records in a custom object.
Before you begin:
- Create your upload file as a delimited file (.txt, .csv), a Microsoft Excel file (.xls, .xlsx) or an XML file. The upload file should only contain the custom object records that you want to update.
- Separate fields in a delimited file using a comma (,), pipe (|), or semi-colon (;).
- The first line or row of the file must be the source fields. Use similar naming conventions for the custom object record fields in your import file, to those in Oracle Eloqua. This will make mapping easier.
- For updating existing custom object records, include the record's unique code. Oracle Eloqua will generate a unique code for any new custom object records with a blank code.
- The Unique Code field has a limit of 100 characters. Values with more than 100 characters will be cut off at 100 characters.
Note: This may result in values that are no longer unique within the upload. If this occurs, only one of the "duplicate" records will be uploaded. If there is an existing record with the shortened unique code, the new record may overwrite some values. Avoid this by keeping the unique code within the 100 character limit.
- Upload your completed upload file to the SFTP server if applicable.
Note: Uploads to Oracle Eloqua from an SFTP server cannot exceed 5 GB.
To upload multiple custom object records:
- Navigate to Audience , then click Custom Objects.
- Open the custom object you want to upload to, or create a new one.
- Click the Custom Object menu, then click Upload Custom Object Records.
Complete the Upload Details and select the Source of Custom Object Record data, then click Next.
Select the file in Step 2 Upload Data Source.If you selected to upload a file from your local machine
If you selected to upload your file via a remote file transfer over SFTP
- Click Choose File and browse to the upload file. Click Upload and Preview Data.
- Click Next when you're ready.
- Select the file format from the Choose file type drop-down list.
- Type the Host, File Path, and User Name.
- Select to use either a password or SSH key for authentication.
- Click Upload and Preview Data. Click Next when you're ready.
Map the fields from the source file to fields in Oracle Eloqua in Step 3 Field Mapping, then click Next.
- Select the contact field to use to uniquely identify a contact from the Uniquely Match On drop-down list.
- To have Oracle Eloqua attempt to match source fields to the best possible target fields, click Auto-Map Fields. You can manually fix any mistakes.
- To change when values are updated (for example, update the value if it is blank or not blank) or to set constant values, click Advanced Options.
Configure how the uploaded fields will be translated into custom object record fields in Step 4 Upload Actions.
- To validate that the email addresses exist and the format is correct, select the Validate Email Address check box. This option is selected by default.
- To set the status of uploaded custom object records, select an option from the Status of uploaded data cards drop-down list. The status of a custom object record options are: Registered, In Progress, or On Hold.
- To update the status of existing custom object records, select the Overwrite status of existing data cards check box.
- To make the custom object records read-only, select the Data Card ReadOnly check box.
- To map new custom object records to existing contact records, select the Map data cards check box.
- To determine the type of entities in the upload and determine what field identifies them, select the options from the Entity Type, Entity Field, and Source Field drop-down lists.
- To have Oracle Eloqua perform a case sensitive match when comparing to existing contacts, select the Case-sensitive match check box.
- To send your custom object records to a step in a Program Builder program, click the Program Step field.
Finalize your upload in Step 5 Summary and click Finish.
- Enter the email address to be notified when the upload completes. If you are using multiple email addresses, separate each with a comma.
- To use these upload settings in another upload, select Save these settings for re-use. Otherwise, select Run the upload once using these settings.
Note: An administrator can create new data sources. For more information, see this Knowledge Base article.
If custom object records didn't update
You might notice that some of the data from the upload file did not make it to the custom object record. There are a couple reasons why this may happen:
- If you're using a file transfer via SFTP, reach out to your IT team to make sure the SFTP IP address is whitelisted for your POD. For further information, see Setting up SSH keys.
- If a custom object record's unique code was greater than 100 characters, the shortened code may have become a duplicate of another custom object record. This may cause the duplicate not to upload. If this occurs, shorten the unique code to 100 characters or ensure the first 100 characters are unique.