This patch goes against the salesforce_account module that eojthebrave wrote version 3.

I was getting errors when saving a node in Drupal and salesforce_account.module was attempting a PUT operation back to salesforce. There were a couple fields in my Account Object that I could not change from the API for security reasons on Salesforce. I wrote a patch to have another menu item under the Salesforce Account configuration menu where you can specify fields to "Exclude" from the update. When submitting the drupal form, the excluded fields will not be included when updating salesforce. Also, the excluded fields are shown as disabled on the node edit screen in Drupal.

Please test patch, and let me know how it works.

CommentFileSizeAuthor
bypass-field-on-update.patch10.53 KBtom friedhof

Comments

eojthebrave’s picture

eojthebrave
he/him
Primary language English
Location Minneapolis, MN
commented

After thinking about this a bit I think it would be better to have this functionality implemented in the common salesforce_sync_api.inc file, or something similar so that it can be more reusable for other modules. (salesforce_case.module) for example. I really like what it's doing though and one way or another think it's an important feature to include. Thoughts?

victorkane’s picture

victorkane commented

Yes, definitely.

The thing is, as per the discussion in http://groups.drupal.org/node/7065 we need a way to map arbitrary salesforce module user requirements in terms of Salesforce data to Drupal content types, profile persistence methods, etc.

For example, instead of using the core profile module for persistence of Salesforce lead data, one may want to use the bio module, the node_profile and/or usernode modules, etc., or map arbitrary data with Salesforce custom objects, or what have you.

This would generalize a way to configure precise arbitrary Drupal fields / Salesforce fields mapping.

This will form part of the complete rewrite of the Salesforce module for Drupal 6, based on the Salesforce PHP API.

That's where stuff like this and other feature requests (handling Salesforce case records, for example) should be catered to.

aaronbauman’s picture

aaronbauman
he/him
commented
Status: Needs review » Closed (fixed)

#702614: 5.x branch is no longer relevant. Let's drop it.