Closed (won't fix)
Project:
Salesforce Suite
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
29 Apr 2010 at 13:35 UTC
Updated:
10 Dec 2012 at 16:13 UTC
On import and export, sometimes the Drupal value should take precedence, and sometimes the Salesforce value should take precedence. It would be nice if, when creating fieldmaps, the admin could specify an actions for import / export. E.g. "always update," "never update," "update only if blank", etc.
Comments
Comment #1
EvanDonovan commentedWhat would the UI for this be?
Comment #2
aaronbaumanThe UI that Jackson River demonstrated at drupalcon SF was something like:
create only (never update),
update only (never create),
update only if blank,
etc.
Drupal,
Neither
In other words, for each field, the user selects under which circumstances data should be pushed or pulled; and which database should be considered the "master" for this field.
This UI made sense to me, but it would be good to hear some other ideas too.
Comment #3
emptyvoid commentedI'm confused, did this "Jackson River" person extend the SF module or create an additional custom module or did they just display wireframe mock-ups of what they'd like to see in some future module?
Comment #4
aaronbaumanJackson River (a company) demonstrated their custom fork of the SF module, which from what I understand is in production use elsewhere, but has not been contributed. I gathered that their fork diverged significantly enough as to make it difficult to merge.
Comment #5
EvanDonovan commented@aaronbauman: This UI sounds like it might be similar the FormAssembly UI for exports to Salesforce which you should probably check out if you haven't already, since I think it is a brilliantly done integration between a third-party form building system and Salesforce. Their mapping UI has a lot of power that we haven't yet brought into Drupal (conditional export rules, one-to-many and many-to-many mappings, etc.).
You can get FormAssembly trial from Salesforce AppExchange.
Comment #6
aaronbaumanEvan, I checked out the FormAssembly Salesforce trial, which exposes FormAssembly to the SF interface, but integrating forms with salesforce is still hidden.
If you can post screenshots or a more detailed explanation -- or point us to a better demo -- then hopefully we can come of a good way to implement something similar for this module.
Comment #7
EvanDonovan commentedWeird...for me, I had installed it in a dev sandbox first, and then I had a "Manage Web Forms" tab, and could create a form from Salesforce, or set a form to export to Salesforce on the Connectors tab.
I can try posting some screenshots, but I don't think it will describe it as well.
Comment #8
kostajh commentedIs anyone interested in working on this? This is important functionality for anyone who doesn't want to work with the pre/post import/export hooks - and even for those of us who do, I'd much rather configure my sync logic through a UI like the one in #2.
Comment #9
EvanDonovan commentedI think that this may prove to be necessary for the purposes for which I am working with brianV on the 7.x-2.x branch.
As a prerequisite, we are thinking it might be a good idea to decouple the fieldmapping UI from the core salesforce_api.module, since the current fieldmapping UI is a bit of a blunt instrument for some uses of the module.
Anyway, that to say I won't be working on this immediately, but we may end up working on this.
Comment #10
EvanDonovan commentedTo put on the 7.x roadmap (high priority).
Comment #11
EvanDonovan commentedTagging as a feature to pull from Springboard.
Comment #12
kostajh commented