Add support for Salesforce API 7.x-3.x

Make sure you install 2.x release not 3.x release of the Salesforce module. It has a submodule called salesforce_api (http://drupalcode.org/project/salesforce.git/tree/refs/heads/7.x-2.x:/sa...)

The 2.x release is no longer supported, is there scope for you to upgrade this module to be compatible with the active 3.x release?
Thanks,

There are two possible solutions that I am considering. I've talked to some of the maintainers of the Salesforce module of either volunteering to support the 2.x of forking it.
There's also the possibility of creating a 2.x branch of this module that would rely on 3.x branch of the Salesforce module but I would need someone else to step up for it as my clients continue to use the SOAP API.

We needed the Webform Salesforce module to work with the Salesforce REST API (Salesforce 7.x-3.x module). I have done a fast upgrade including some fixes to the mapping UI, a new database table to store the returned Salesforce Record ID, and some changes to work with objectInsert (instead of objectUpsert) if WebformSID__c does not exists (I remove the field it via a hook from another module, because we are not using the field).

The code is available in https://github.com/beltofte/webform_salesforce if any body is interested. It is only tested agains Webform 7.x-3.x, so it might not work with 7.x-4.0. We have not done the final testing and released the code to the client, so their might be issues in it.

We have two (2) options:

1. Keep the existing 7.x-1.x branch as it is now, and add support for both versions of the API. The version that gets used will depend on a new configuration option.
2. Create a new 7.x-3.x branch with the above code from GitHub merged in as a started point. Any issues will have to either be forward-ported or back-ported.

How does everyone feel about #1? If that won't work, we can go with #2.

In either case, updating status as the above code is not in patch format.

Personally I'd prefer option #2 - the APIs are different enough so that maintaining both in one branch and dealing with issues that arise from it will be a significant effort. There should however be a path to get from 7.x-1.x to 7.x-3.x without loss of data.

Makes sense to me.

@nonsie: Would you be so kind as to create that branch? This way, we can get the above into patch format, and then folks can start testing it on the new branch. (We'll also be able to set the version here appropriately.)

There is now 7.x-3.x branch for development. I won't get around to creating a patch based on git repo mentioned in #4 until probably later this week. If anyone has time to get it into a patch form earlier, go for it.

I might have time tomorrow evening to create a patch.

Okay, it took a bit more than one day to get the patch made. It is made against the 7.x-3.x branch.

Notice: that it is for Webform 7.x-3.x not version 7.x-4.x. Not sure how many changes it will require to get it updated to version 4, and if we can support both version 3 and 4 in the same branch without too much hacking :-)

@Colan / @nonsie: if anyone of you want to discuss the future on this module with support for Salesforce API 7.x-3.x and Webform 7.x-4.x, then will I be in LA for the DrupalCon next week. If you are attending too, could be arrange a Salesforce BOF.

@beltofte: I'm no longer working with my clients on any projects involving Salesforce (so I'm out), but I'm sure that your BOF will be well attended if you create it! Build it and they will come.

I'll be in LA and might have time in my schedule for a BOF. There already is a Salesforce BOF - https://events.drupal.org/losangeles2015/bofs/integrating-drupal-salesforce

Cool. I will join "Integrating Drupal with Salesforce"-BOF :-)

Hi Everyone,

I just came across this and, while I attended the SalesForce BOF, I did not get to meet either of you. I was late to the BOF, so I may have missed discussion about this.

Did anyone meet and discuss plans to support Webform 7.x-4.x and SalesForce 7.x-3.x? Jason.

Unfortunately was the BOF in LA to big (to many participants) and ended focusing 100% on the Salesforce module and experience with that module. So we did not discuss the future of the Webform/Salesforce integration.