Oracle Eloqua Release Notes

Release notes are displayed in descending order from the most recent release to the oldest. Known Issues are listed with the most recent release.

See TIBCO Scribe® Online Connector For Oracle Eloqua for more information.

Note: To access any changes to metadata support, such as new operations, entities, or fields, reset metadata for the Connection. See Resetting Metadata.

Version 2.2.0

Released May 24, 2017.

New And Noteworthy

The Connector for Oracle Eloqua supports the following:

Updated support for Query, Create, Update/Upsert, and Delete operations for Custom Objects via the Oracle Eloqua REST API instead of the SOAP API. The SOAP API is being deprecated as of April 1, 2017. (27177, 27179, 27180, 28656)

Updated the brand from Eloqua to Oracle Eloqua. (38976)

Note: Oracle Eloqua has implemented stricter validation rules for numeric fields in their API. If you have existing flows with numeric fields mapped to Oracle Eloqua as a target, you may need to add formulas to those fields to convert the data to the correct type. For example, if you have a DECIMAL value mapped to an INT field, you can use the TOINTEGER function in TIBCO Cloud™ Integration - Connect to convert the data before sending it to Oracle Eloqua. See Data Conversion.

Note: The Oracle Eloqua SOAP API is not supported by Oracle Eloqua as of April 1, 2017. The REST API behavior is slightly different. You should be aware of the changes to the Connector to accommodate working with the REST API. In some cases, TIBCO Scribe® has maintained some fields to accommodate existing Customer Organizations and flows, however those fields will be deprecated in a future release.

Custom Objects

Mapping a NULL value to a datetime field overwrites the value of that field. Previously, datetime fields were not overwritten by NULL values. (42513)

MappedEntityID and MappedEntityType Fields, used in Oracle Eloqua to link a Custom Object to a Contact record, only accept a value of 1 for the MappedEntityType field. Previously, this field could also be used to link a Custom Object to an Account record. This functionality is different in the Oracle Eloqua REST API.

In a future release of the Connector, the MappedEntityType field will be deprecated. Custom Objects can only be mapped to a Contact record via the REST API, making this field unnecessary. TIBCO Scribe® recommends modifying any flows that use this field and removing it altogether.

For existing flows that create or update a Custom Object record, note the following information for the MappedEntityType field:

Create —
- Using any value other than 1, NULL, or not mapped in the MappedEntityType field creates a Custom Object record without a link to the Contact record.
- Using a valid Contact ID in the MappedEntityID field and 1, NULL, or not mapped in the MappedEntityType field links the Custom Object record to the Contact record.
Update —
- Using any value other than 1, NULL, or not mapped in the MappedEntityType field generates a record error.
- Using a valid Contact ID in the MappedEntityID field and 1 or not mapped in the MappedEntityType field links the Custom Object record to the Contact record.
Create or Update -
- Using an invalid Contact ID in the MappedEntityID field generates a record error.
- MappedEntityType value is ignored if MappedEntityID is not mapped.

For new flows that create or update a Custom Object record, only the MappedEntityID field containing a Contact ID is required to link a Custom Object record to a Contact record.

DateTime Fields

Datetime fields visible in the Oracle Eloqua User Interface display in Eastern time, are stored by Oracle Eloqua in UTC, but are interpreted by TIBCO Cloud™ Integration - Connect as Eastern time for backwards compatibility with flows built against the Oracle Eloqua SOAP API. In a future release, TIBCO Cloud™ Integration - Connect will read these datetimes as UTC time.
For each Oracle Eloqua datetime field, TIBCO Cloud™ Integration - Connect has a corresponding virtual datetime field that stores and interprets time in UTC. The naming convention for these virtual fields is <OriginalFieldName>_UTC.
When using Oracle Eloqua as a target, if you insert a datetime that is a string and contains either kind or offset into one of the TIBCO Cloud™ Integration - Connect virtual date time fields ending in _UTC, the date is converted to UTC and the time difference is doubled.
If you have created any Custom Object datetime fields that end in _UTC, they are treated the same as the TIBCO Cloud™ Integration - Connect virtual fields ending in _UTC, where datetimes are stored and interpreted as UTC. If these fields should not treat datetimes as UTC, you may need to rename them before executing any TIBCO Cloud™ Integration - Connect apps.

Warning: In a future release of the Connector the virtual date fields will be deprecated, the original Oracle Eloqua datetime fields will be exposed in TIBCO Cloud™ Integration - Connect with the <OriginalFieldName>_UTC format, and those fields will be interpreted as UTC time.

Best practice is to update any flows that use the original datetime fields to use the new virtual fields ending in _UTC. Take into consideration that the _UTC fields store time in UTC time and modify your flows accordingly. If you have updated your flows, when the virtual fields are deprecated, the transition will be seamless because the original field names will have _UTC appended.

Closed Issues

There are no Closed Issues in this release.

Known Issues

SCELOQ-17

Summary: Inserting or updating records into a custom entity sometimes fails if the Connector cannot determine that a record already exists and attempts to create a new one. An error similar to the following is generated:

"BadRequest[{"type":"ObjectValidationError","container
{"type":"ObjectKey","objectType":"CustomObjectData"}
,"property":"fieldValue","requirement
{"type":"NoDuplicatesRequirement","duplicateProperty":"UniqueCodeField","duplicateValue":"<your value>"}

Workaround: Contact Support for hotfix SCELOQ-14.

SCELOQ-11

Summary: If you have a large number of optionlists in your Oracle Eloqua company, you may see metadata timeout errors when configuring an Oracle Eloqua Connection. (Case # 01862389)

Workaround: Reset metadata for the Connection and wait 10 to 15 minutes for the metadata to be returned.

39529

Summary: If you create a Custom Object in Oracle Eloqua with the same name as a standard Oracle Eloqua entity or you create two Custom Objects with the same name, TIBCO Cloud™ Integration - Connect cannot load metadata. The following error is returned when you open a map using an Oracle Eloqua Connection.

Unable to retrieve metadata
An item with the same key has already been added.

For example, Oracle Eloqua has a standard entity named Campaign, if you create Custom Objects named Campaign1 and Campaign2, an error is generated. (Case # 55583)

Workaround: Rename the Custom Object in Eloqua with a unique name.

42270

Summary: The Oracle Eloqua API stores datetime fields using Unix dates in seconds. The oldest datetime value supported is 12/13/1901 3:45:52 PM or -2147483648 seconds, which is the lower bound of an Int32 field. Dates older than 12/13/1901 3:45:52 PM are not supported and are converted to 12/13/1901 3:45:52 PM.

Workaround: None.

57624 / 58848

Summary: Oracle Eloqua Connections sometimes experience timeouts when querying from which they cannot recover. Errors similar to the following are generated: (Case # 60742, 67582, 68460, 69089, 69349, 01721077, 01727706, 01728580, 01729209, 01729469, 01733163, 01752706, 1819771, 1814403)

ExecuteQuery Unable to cast object of type 'RestSharp.JsonArray' to type 'System.Collections.Generic.IDictionary`2[System.String,System.Object]'.

Workaround: Contact Support for hotfix 57624 that enables additional retry logic.

67843 / 69284

Summary: Connecting to an Oracle Eloqua instance that has a large number of pick lists and pick list values, sometimes causes timeout errors similar to the following: (Case # 66035, 68314)

Object reference not sent to an instance of an object.

Workaround: Contact Support for a hotfix.

September 2015 Release

New And Noteworthy

Contact entity DateCreated and DateModified fields are interpreted incorrectly by the Oracle Eloqua SOAP API.

DateTime values for these fields are displayed on the Preview tab in Coordinated Universal Time (UTC), but are interpreted by the Eloqua API as Eastern Standard Time (EST). When using the Contact entity as a source, if one of these fields is used as a filter, match criteria, lookup, or to locate new and updated records, the resulting set of records is incomplete due to the time difference between UTC and EST.

For example, assume you are querying the Contact entity, with the Process only records created or updated option enabled. You are using the DateModified field to compare against the Most Recent Record Processed date to determine which records to include in the query results. If the value of the DateModified field for a given record is 8:00 AM (UTC), the Eloqua API interprets this as 8:00 AM (EST), or 13:00 (UTC). Records with a DateModified field between the 8:00 (UTC) and 13:00 (UTC) are not included in the results.

TIBCO Cloud™ Integration - Connect provides two virtual fields for the Contact entity, DateCreatedUTC and DateModifiedUTC, that can be used instead to filter Contact data. These fields are controlled by TIBCO Cloud™ Integration - Connect. The values contained in these fields are adjusted by the connector to always be interpreted as UTC datetime data.

If you have existing maps that use the Contact entity as a source with the DateModified or DateCreated fields as filters, you should take the following action:

Reset Metadata for the Connector.
Review your flows to determine if any use the DateCreated or DateModified fields in a filter, match criteria, lookup, or to process only new and updated records.
For flows that use the DateCreated or DateModified fields, replace those fields with the new virtual fields, DateCratedUTC and DateModifiedUTC.
For flows that use the Process only records created or updated since last run based on the value of the last modified field feature, follow these additional steps.
Open the Query block and write down the date in the " Most recent record processed" field.
Click the Reset button, add 4 hours to the time you recorded, and enter that time into the field. This ensures that any records missed the time discrepancy are picked up by the next run of the solution.

Closed Issues

There are no Closed Issues in this release.

July 2015 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

9978

Enhanced query for Campaigns to prevent time-outs in environments with large amounts of data.

March 2015 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

9666

The Oracle Eloqua Connector did not correctly perform Delete or Update target operations on Custom Objects. (Case # 69490 )

October 2014 Release

New And Noteworthy

The following entities are currently supported:

Contact
Contact Lists
Custom Contact Object
Campaign and Campaign Assets, such as Email, Form, and Landing Page
Activity and specific Activity Types

Closed Issues

There are no closed issues in this release.

Oracle Eloqua Release Notes

Version 2.2.0

New And Noteworthy

Custom Objects

DateTime Fields

Closed Issues

Known Issues

September 2015 Release

New And Noteworthy

Closed Issues

July 2015 Release

New And Noteworthy

Closed Issues

March 2015 Release

New And Noteworthy

Closed Issues

October 2014 Release

New And Noteworthy

Closed Issues

Related Topics