The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I want to be able to save a single Drupal node and upsert multiple Salesforce objects.
It would be nice to be able to have a single Salesforce object map to multiple Drupal node types too.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | Allow_multiple_fieldmaps_for_the_same_entity-785286-9.patch | 30.22 KB | vasike |
| #4 | Allow_multiple_fieldmaps_for_the_same_entity-1056630-24.patch | 29.73 KB | aaronbauman |
Comments
Comment #1
EvanDonovan commentedThis would be especially cool for integration with Ubercart store purchases (a la Ubercart Salesforce module).
Subscribing.
Comment #2
EvanDonovan commentedPossibly resolving #993766: Add native support for mapping of "foreign keys" for already mapped objects would get us part of the way to this. I am thinking that full one-to-many fieldmap support would be broader than the aforementioned issue, though, since it would entail creating a more flexible UI for mappings, which not only would not have the "sea of dropdowns", but would allow for adding additional objects that would be mapped off a Drupal object, using the Salesforce ID of the initially mapped object as their "foreign key" (for lookup or master-detail relationships). This would require AHAH.
This would eliminate the need for the OpportunityContactRole node which Ubercart/Salesforce Integration's uc_sf_order.module currently uses.
Comment #3
aaronbaumanI'm going to consolidate this conversation with #1056630: Bug: sf_user allows creating many-to-many relationships between SF and Drupal objects, even as it assumes they're one-to-one
Comment #4
aaronbaumanRepurposing this issue as a task for D7.
I'm re-posting vasike's patch from #1056630: Bug: sf_user allows creating many-to-many relationships between SF and Drupal objects, even as it assumes they're one-to-one for review here, without changes.
Comment #5
EvanDonovan commentedThanks, Aaron, for re-opening this. Now, Vasike, we can give this the attention it deserves, although I will be out the rest of the weekend.
Comment #6
vasikeany feedback for the patch?
i know this solution won't affect what it's already built and linked, it just add the "multi fieldmapping"
Comment #7
EvanDonovan commentedSorry I haven't had any time to test yet. I've been having to get the 7.x Salesforce module production-ready for a client release shortly.
After that, I would like to investigate this. I am thinking possibly I may make a feature branch for these sort of things - or you could apply to your sandbox, and then I could pull...like a Github-like workflow.
Comment #8
vasikeso what should it be? a branch or a sandbox? what's the best solution for you?
do you need a new patch as there are some changes since the patch was built?
Comment #9
vasikehere is an updated patch, as the last one don't work anymore.
some testing would be nice
Comment #10
cellar door commentedI just needed this for a project - going to try and port to the latest 7.3.x-dev . I just tried it through separate fieldmaps and it created duplicate content.
The use case I have is opportunities and Contact Roles. Technically separate fields but on the same node in Drupal.
Comment #11
levelos commentedThis patch is for a different branch of the module, and they have diverged considerably. Please create a new ticket if you need/want something similar in 3.x.
Comment #12
kostajh commentedThank you for your efforts in working on this patch. We're not going to continue supporting 7.x-2.x however. See #2124817: 7.x-2.x and 6.x-2.x branches are no longer supported.