Closed (won't fix)
Project:
Salesforce Suite
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
19 Jan 2012 at 17:33 UTC
Updated:
10 Dec 2012 at 15:46 UTC
Jump to comment: Most recent file
Comments
Comment #1
aaronbaumanYou can either use a fixed SFID value or a nodereference field to send an SFID to a lookup field.
Also, you are describing the behavior without explaining how it differs from your expectations.
When you submit a bug report, you should provide a description of the issue, steps to reproduce it, and how you would like to see the issue addressed.
Comment #2
Fixdit commentedThanks aaronbauman,
• Description: Field data mapped to Salesforce's 'lookup' fields won't export unless a pre-existing SFID referenced from another SF is submitted.
• Reproduce: Create a textfield attached to a content type and map it to your Salesforce field (lookup datatype on the SF side). Create a new node of that content type and enter a value into the field. On submit, the new node and the field's value should be exported and reproduced in Salesforce. However there nothing is saved on SF (blank).
• Possible fix: Lookup fields require a value referenced from another SF table in order to save data. We've created a work around using a custom autocomplete field in Drupal that queries SF to make sure the selection made by the user is an accepted SFID.
Hope this helps,
Comment #3
Ivan Ottinger commentedHi everyone,
we need to have lookup-field-mapping feature available in our organisation as soon as possible, so I have decided to work on that by myself creating custom module. I would like to use it as a temporary solution until this feature is available in Salesforce Suite. Hopefully someone can profit from this small module as well.
Basically, this module provides extra "Salesforce lookup" field, which can be added into any content type. User then specifies exact name of Salesforce object which we want field to be attached to, and exact record name which exists in Salesforce database. It's not the final solution, I am planning to design it more user friendly later.
How module works: Module executes a query (based on user input - SF object and SF record) to get Salesforce ID of specified record and saves it to the SF record field.
To make it clear, module isn't working yet. I have one problem which I am struggling to solve:
When I add this custom field into content type and input value in this field when editing a node, it's saved correctly. But, as soon as I set mapping for this field in Salesforce Suite settings and edit/save the node, value is transferred to Salesforce but doesn't stay in the field anymore.
I guess it might be some bug in my code, but I have problems finding it. I think that, when user saves a node with "Salesforce mapped" fields, some function in Salesforce Suite is triggered which erases content of the field. But as I said, it should be bug in my code because when mapping other standard fields like text field, everything works correctly.
Thanks a lot, I appreciate any help.
Ivan
Source code
Comment #4
kostajh commentedThis would need to be submitted as a patch (and working) to be considered.
Comment #4.0
kostajh commentedCopy reworded.