Bug reports should adhere to Drupal standards.

Before creating a new issue, please:

Before reporting a bug to the Salesforce issue queue, follow the steps below.

Troubleshooting Connection Errors

General Suggestions

• Are you using the right WSDL? Generate a new one.
• Disable SOAP WSDL cache.
• If you’re switching from sandbox to production, make sure that you switched accounts when generating the WSDL
• Can you connect to the sandbox?
• Are you logging everything? Have you checked watchdog (admin/reports/dblog)?
• Re-enter the token, username and password
• Try to connect using another Salesforce user

In Salesforce:

• Regenerate the WSDL
• If you’re switching from sandbox to production, make sure you're in the right account
• Make sure the IP of your Drupal server is not blocked
• Go to: Your Name > Setup > Users. Check login attempts of the user with which you are connecting to Salesforce from Drupal.
• Reset the credentials associated with the user (password and security token)

In the Salesforce API module settings:

• Replace WSDL file with the one you want to use (admin/settings/salesforce/wsdl)

Using the Devel module:

• Enter the following on the "Execute PHP" page (devel/php):
  $somevariable = salesforce_api_connect();

In Drupal 6, support for mapping fields from commonly used modules like Location and CCK is provided by the Salesforce Contrib (sf_contrib) module. If you use node_location, user_location, cck_location, or any other CCK fields and you'd like them to be available for export, you need to enable this module.

In Drupal 7, there is no support currently for mapping Location fields. Standard FieldAPI fields should be mappable via the Salesforce Entity (sf_entity) module.

In addition to the out of the box support for various CCK fields, an extensible framework is available for developers to build or alter support for contrib modules. See sf_contrib for examples and best practices, as well as hooks.php for documentation of the available integration points.

Related modules

Webform

The Salesforce Suite package includes modules that integrate with Drupal core nodes and users (and other entities, in Drupal 7). For integration with Webform submissions, check out the Salesforce Webform Integration module.

Note that it is not currently compatible with the latest version of the Salesforce API for Drupal 6. For a compatible version, see .

Ubercart

If you do not upload a WSDL file, Salesforce module will use a default .wsdl file (salesforce_api/toolkit/soapclient/enterprise.wsdl.xml), which may not be compatible with your organization's Salesforce installation or the current Salesforce API. It is highly recommended that you supply your own Enterprise WSDL file via the WSDL administration panes at admin/settings/salesforce and admin/settings/salesforce/wsdl. These panes will walk you through creating a directory outside your webroot and uploading the WSDL file to that directory.

By default, all Salesforce credentials are stored in the variables table, unencrypted. If this is a problem for you, this module supports encryption via the AES module: http://drupal.org/project/aes.

You will need to create a directory outside your webroot wherein your encryption key will be stored. (You can use the same one you used for your WSDL.) Your credentials will then be encrypted as securely as AES allows.