Closed (fixed)
Project:
Salesforce Suite
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
9 Sep 2009 at 11:28 UTC
Updated:
9 Mar 2010 at 21:00 UTC
Jump to comment: Most recent file
Comments
Comment #1
aaronbaumanYou also have a Drupal object and a SalesForce object, the pair of which is presumably unique.
Could you explain your use case a bit further?
Comment #2
keesje commentedHi,
Attached is a screenshot that says it all IMHO. The admin has to click them all to find the right fieldmap. If a project contains more fieldmaps of the same type's, its not workable this way.
Thanks,
Kees
Comment #3
aaronbaumanah, good point.
I've never used salesforce for a webform integration, so I did not know the interface looked like this.
patches welcome
Comment #4
keesje commentedOK, I will ask this client if there is some budget, if so, I will look into it. If not I might do that as well, but probably not this year ;-).
Thanks,
Kees
---------
Handdoek kopen bij de Handdoekenshop
Comment #5
aaronbaumanThe attached patch adds a varchar(255) description field to the fieldmap object, based on 6.x-2.x-dev
Reminder: Since we're still in dev versions, we're not writing hook_update_N's, but updating the hook_install.
Therefore, if nuking your entire database is not feasible, you'll have to disable/uninstall your existing salesforce module (and remove the salesforce_* tables manually if they're not dropped by hook_uninstall) before this patch will take effect.
Comment #6
aaronbaumancommitted http://drupal.org/cvs?commit=332886
Though I'm not entirely convinced this is necessary.
If the fieldmaps overview screen starts getting too cluttered, this may have to go.