Posted by aaronbauman on April 29, 2010 at 1:50pm
3 followers
| Project: | Salesforce Suite |
| Version: | 7.x-2.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Issue Summary
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.
Comments
#1
This would be especially cool for integration with Ubercart store purchases (a la Ubercart Salesforce module).
Subscribing.
#2
Possibly 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.
#3
I'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
#4
Repurposing 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.
#5
Thanks, 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.
#6
any feedback for the patch?
i know this solution won't affect what it's already built and linked, it just add the "multi fieldmapping"
#7
Sorry 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.
#8
so 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?