I need Eloqua working with the core Contact module. Contact can have multiple forms and the forms are fieldable so it's like a Webform-lite. This sub module should work similar to the Webform submodule but can make use of Third Party Settings as Contact uses actual fields.

CommentFileSizeAuthor
#1 2475215--eloqua-entity-bridge.patch32.06 KBpaulmckibben
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

paulmckibben’s picture

Mediacurrent developed an eloqua_entity_bridge submodule that, for now, only works with the Contact Message entity type, but with a little more work, it can be extended to support other entity types. I thought this was already part of the project, but just discovered it was not (after fixing an issue with Eloqua field settings).

Attaching a patch to add the eloqua_entity_bridge submodule, including my recent fixes.

paulmckibben’s picture

Status: Active » Needs review
jasonawant’s picture

Status: Needs review » Needs work

@paulmckibben

Thanks for posting this patch. I have a few questions about what's going on here if you could help elaborate.

What does the following mean? Specifically, what does TPS mean?

@TODO: Figure out how to do TPS on base fields and remove all this.

Also, could you share a link to the Eloqua documentation used when decided which fields to add to the contact form settings? Fields such as Eloqua Form Name, Eloqua language field name, Username field name, Username request parameter key, Email field name, Email request parameter key, Subject field name, Subject request parameter key, Message field name, Message request parameter key.

This is a different approach than 7.x versions which a mapped webform components to Eloqua field names, and I'm trying to get grasp of the change. Thanks, Jason.