Ok, I *think* I'm following this right, but I could be wrong, I'm not seeing the Contact ID and Donation fields when I try to setup this mapping.

I'm also getting the error "uc_sf_account_export_purchaser: invalid fieldmap. Remember to choose which Ubercart fieldmaps to use in the main Salesforce settings tab." when I checkout a new order in ubercart.

I've setup the field mappings as logical as my choices will allow (see attachment), I'm not sure if this is a bug or I'm not doing something right, some direction here would be greatly appreciated

c) Opportunity Contact Role node -> OpportunityContactRole
i) This makes the link between an individual Contact and an Opportunity.
The OCR node only stores a field containing the Contact's Salesforce ID.
It is necessary since currently you can't do one-to-many mapping using
the Salesforce API module. Normally, in Salesforce,
Opportunities/Donations are linked with Accounts/Organizations, but the
Ubercart Salesforce Integration module, in its current state, links only
to individual Contacts. Linkage with Accounts will be added in a later
version as an optional add-on module.
ii) Fields:
1) Contact ID -> Order User's Salesforce UserID [for OCR]
2) Donation -> Order Salesforce ID [for OCR]

CommentFileSizeAuthor
Screenshot - 09132011 - 05:08:16 PM.png56.85 KBdgtlmoon
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dgtlmoon’s picture

http://drupal.org/node/1276686 explains the error message "uc_sf_account_export_purchaser: invalid fieldmap. Remember to choose which Ubercart fieldmaps to use in the main Salesforce settings tab."

EvanDonovan’s picture

Title: Documentation not adding up to what I'm seeing » Document use of uc_sf_account and other new modules in package
Assigned: Unassigned » EvanDonovan
Category: bug » task

The uc_sf_account module is not strictly required. It's for Account linkage; the other is for OpportunityContactRole.

Account linkage is probably more useful for most people though.

I am changing this to a documentation task.