Creating imports

Imports are data transactions from Salesforce into Oracle Eloqua. The Salesforce.com Integration app executes imports every 15 minutes. After an import has been scheduled, an import schedule does not display because imports are executed so often. If an import needs to be performed off schedule, it can be executed on demand. An import may fail due to various reasons such as connection or data related issues. Some of these issues will cause an entire import to fail. You can setup email notifications to alert you when import errors occur.

The following imports are recommended:

  • Leads
  • Contacts
  • Accounts
  • Opportunities

When viewing your imports, disabled imports are dimmed to indicate their status. There are several indicators in your list of imports to help you quickly get an overview of their status.

Prerequisites

Note: Campaign, opportunity, and user imports have additional prerequisites.

To create an import:

  1. In the Salesforce.com Integration app, click Imports.
  2. Click Add Import and select a connection for which you want to create a new import.
  3. Complete the import details:
    • Name: Enter a name for the import.
    • Object Mapping: To see available fields for mapping, select an Oracle Eloqua object and Salesforce object and click Fetch. The unique identifiers for field mappings will be determined once Fetch is clicked. Top-level objects from your Salesforce instance are available in the Salesforce Object drop-down.
    • Import Only Deleted Records: Select this option if you want to recognize only deleted Salesforce records in Eloqua by creating imports for deleted objects.
    • Filter Details: Enter a Salesforce Object Query Language (SOQL) WHERE clause filter to use on the CRM source field when querying contacts to import and then click Test to test the filter. For details about creating SOQL filters, refer to the SOQL developer documentation.
    • Update Eloqua Fields: Map your unique identifier to specify the object in Oracle Eloqua to update or create. For each set of fields, select the Oracle Eloqua field that will be mapped to Salesforce contacts. Add more mappings by clicking Add Import Field Mapping. Click the menu An image of the Edit Icon to delete the mapping or switch the field type to static text, static date, or dynamic date. If you map fields for related objects, you can select the Keep records updated option to trigger updates to all fields of a related object when only one of the fields is changed. For example, if your contact import has a related account object and you select this option, both objects will be updated if there is a change to only one of them.
    • Update Eloqua Fields: For each set of fields, specify the Eloqua field that will be mapped to Salesforce contacts. If you are creating contact records, the unique identifier is the first mapping shown in this list. Add more mappings by clicking Add Import Field Mapping. Click the menu An image of the Edit Icon to delete the mapping or switch a From Salesforce field type to static text, static date, or dynamic date.If you select Advanced Mode from the An image of the Edit Iconmenu, you can enter multiple objects to be sent to a single Salesforce field: Eloqua Object, Date, or Dynamic Date. You can also type static text into the box as needed. For contacts, you can use advanced mode to select contact and related account fields. For CDOs, advanced mode allows you to select a CDO and its related contact and account fields. You can also select Advanced Mode for Salesforce fields.

      An image of Advanced Mode's Insert Object options.

    • Import Rules: Specify data priority and deduplication rules.

      An image of the Import Rules window.

      • Data Priority: Select the priority of data to resolve conflicts on imports, such as Bulk API and CRM Integration. If leads and contacts are being imported to Oracle Eloqua contacts, there may be situations where a lead and contact with the same email address exist. Oracle Eloqua's data priority can be used to instruct Oracle Eloqua which source, lead or contact, is higher priority. If the contact import is set to have a higher priority than the lead import, the data imported from the contact will not be overwritten by the lower priority lead data. Higher priority sources are never overwritten by lower priority sources.
      • Deduplication type: Specify how to handle duplicate import records. For example, you can chose the most recently updated record or import all records. Deduplication runs per import execution. If multiple records with the same match field value are imported in a single execution, those records will be deduplicated based on the setting specified here.
    • Post Processing: Specify an action to be performed on a contact after import. You can specify a maximum of ten post processing items, including the following actions and any Salesforce feeder elements that you add to a canvas.

      An image of the Post Processing window.

      • Add to Shared List / Remove from Shared List: Specify whether after the import, contacts should be added to or removed from a shared list.
      • Subscribe to Email Group / Unsubscribe from Email Group: Specify whether after the import, contacts should be subscribed to or unsubscribed from an email group.
      • Global Subscribe: Specify whether after the import, contacts should be globally subscribed globally unsubscribed.
      • Add Action: Click to add another action to be performed after the import.
  4. Click Save.

Click the import's drop-down list to modify the import or view reports. You can edit and enable or disable an import. Once an import is disabled, you can delete it.

Clicking Disable temporarily stops the imports. If the import is currently running and has not yet started (it is in either the Retrieve from Salesforce or Deduplicating steps), the import is canceled and disabled. If the import has begun importing to Oracle Eloqua, the import will finish, then be disabled. Click Enable to enable your import.

Scheduling an import

Once you enable an import, it is scheduled to run automatically every 15 minutes by default 7 days per week.

You can alternatively specify a delay between when the previous run finishes and when the next run begins:

  • Time zone
  • 15, 20, 30, or 60 minutes
  • 1, 2, 3, 4, 6, 8, 12, or 24 hours
  • Monday through Sunday for a specific range of hours

An image of the scheduling options for an import

You can also run the import on demand clicking Run Now and then selecting one of the following:

  • A specific date range: When Run Now is used with a date and time filter, the current date and time is pre-populated. The date and time can be changed to a time in the past as desired. Selecting a specific date allows a partial import to be performed.
  • All Records: If no date is selected, the import retrieves all matching records from Salesforce and imports them to Oracle Eloqua.

Once you select a specific date range, click Run Import.

Note: The Last Import date indicates the last successful import.

Clicking Disable temporarily stops the imports. If the import is currently running and has not yet started (it is in either the Retrieve from Salesforce or Deduplicating steps), the import is canceled and disabled. If the import has begun importing to Oracle Eloqua, the import will finish, then be disabled. Click Enable to schedule your import to run every 15 minutes.

Related

Creating campaign imports

Creating opportunity imports

Creating user imports

Getting started with the app

Salesforce.com Integration app

Data import priority

standard imports, scheduling imports, Get Leads, Get Contacts, Get Accounts