Would be good to include support for using javascript to get the guid from the client and return it with the post. See Eloqua's documentation at:

http://eloqua.blogspot.com/2010/03/using-form-reposts-for-advanced-form.... and
http://topliners.eloqua.com/community/do_it/blog/2012/04/17/how-to-repos...

Also see eloqua module for inspiration, which appears to implement the above (although the module only supports webforms):

http://drupal.org/project/eloqua

CommentFileSizeAuthor
#10 1905500-attached-10.patch568 bytesAlbert Volkman
#9 eloqua_api-handle_customer_guid-1905500-9.patch2.42 KBdrupalninja99
#5 eloqua_api-handle_customer_guid-1905500-5.patch4.56 KBiamEAP
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

iamEAP’s picture

iamEAP CreditAttribution: iamEAP commented

We have some of this in our repo and just haven't contributed it back up. If I remember correctly, it was mostly lifted from that Eloqua module anyway.

dwightaspinwall’s picture

dwightaspinwall CreditAttribution: dwightaspinwall commented

That's cool, or if you don't have time for it, we'll probably be tackling it in the next few weeks and can submit a patch (to D6).

iamEAP’s picture

iamEAP CreditAttribution: iamEAP commented

Great! Either way.

iamEAP’s picture

iamEAP CreditAttribution: iamEAP commented
Title: Add Eloqua tracking code support » Add support for passing customer GUID

Looks like we're tracking the actual tracking code addition here: #1984680: Add Eloqua tracking. Since that has more activity and a patch, I'll repurpose this for the latter half of initial post (using JS to append the Eloqua GUID to the form when re-posting), which could easily be done generically, I think.

iamEAP’s picture

iamEAP CreditAttribution: iamEAP commented
Version: 7.x-1.x-dev » 6.x-1.x-dev
Status: Active » Patch (to be ported)
FileSize
eloqua_api-handle_customer_guid-1905500-5.patch4.56 KB

Commited the attached patch to dev (see: edb7f82)

Setting to 6.x and marking patch to be ported, since 6.x users could easily benefit.

iamEAP’s picture

iamEAP CreditAttribution: iamEAP commented

For a D6 backport, note this commit as well: f28dcc1

aziznana786’s picture

aziznana786 CreditAttribution: aziznana786 commented

Has anyone managed to get this to work i.e. get the API to send over Eloqua GUID information while sending a form submission. I am trying to configure our new module and need some assistance in setting it up.

Any help would be much appreciated

iamEAP’s picture

iamEAP CreditAttribution: iamEAP commented

@aziznana786 Would you mind opening up a new issue of category "support request?" I'd be happy to answer any questions there.

drupalninja99’s picture

drupalninja99 CreditAttribution: drupalninja99 commented
Issue summary: View changes
Status: Patch (to be ported) » Fixed
FileSize
eloqua_api-handle_customer_guid-1905500-9.patch2.42 KB

@iamEAP thank you for the work on this. I think that patch got lost in the whole D7 upgrade. I took the javascript we needed for the GUID detection and ported it back to the current D7 project (which has an eloqua_webform submodule). This looks like it's working now. When I test locally I see the GUID hidden field populated. I did not add the extra code for 'enabling' tracking bc I think most ppl will want it and it doesn't hurt anything.

Albert Volkman’s picture

Albert Volkman CreditAttribution: Albert Volkman commented
Status: Fixed » Needs review
FileSize
1905500-attached-10.patch568 bytes

One last small tweak.

iamEAP’s picture

iamEAP CreditAttribution: iamEAP commented

I'm a little confused; neither of these patches appear to be related to the Eloqua API module. GUID support already exists in Drupal 7 dev.

This issue is about backporting the D7 GUID work to D6.

iamEAP’s picture

iamEAP CreditAttribution: iamEAP commented
Status: Needs review » Patch (to be ported)
drupalninja99’s picture

drupalninja99 CreditAttribution: drupalninja99 commented
Version: 6.x-1.x-dev » 7.x-1.x-dev
Status: Patch (to be ported) » Fixed

Looks good, I have committed

iamEAP’s picture

iamEAP CreditAttribution: iamEAP commented
Version: 7.x-1.x-dev » 6.x-1.x-dev
Status: Fixed » Patch (to be ported)

I think you guys are in the wrong issue. Moving back to the original status.

drupalninja99’s picture

drupalninja99 CreditAttribution: drupalninja99 commented

I think you mean backporting it to d6? I should mention that I don't think the fix actually ever made it to D7 (must have fallen through the cracks during the port). So now that its fixed in d7 we have to decide whether its worth porting backwards for the 19 sites that use this module. I would vote no.

iamEAP’s picture

iamEAP CreditAttribution: iamEAP commented

There was no port. This module was originally written in D7 and a D6 backport was generously contributed some time ago. GUID support for Eloqua API-enabled forms was committed to the 7.x branch here, with a minor followup here.

drupalninja99’s picture

drupalninja99 CreditAttribution: drupalninja99 commented

Ah ok I know now why I was so thoroughly confused. We maintain the Eloqua module, but this is the 'Eloqua API' module. We should talk ab merging these modules at some point.

iamEAP’s picture

iamEAP CreditAttribution: iamEAP commented

Definitely.

iamEAP’s picture

iamEAP CreditAttribution: iamEAP commented
Version: 6.x-1.x-dev » 7.x-1.x-dev
Status: Patch (to be ported) » Closed (fixed)

Closing this out as 6.x is no longer supported and the fix is already in 7.x.