Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
To update from 8.x-3.x, you'll need to add new composer dependencies, run several module updates, and consider upgrading your authentication mechanism to the recommended JWT browser-less authentication.
Salesforce 8.x-4.x introduces a more flexible, pluggable authentication system.
This release deprecates salesforce_encrypt, and adds salesforce_jwt module to support OAuth JWT Bearer Token flow, improving security and auth configuration management.
Additionally, updates in 4.x improve stability, simplify some class structures, and address some long-standing bugs.
Salesforce Suite version 8.x-3.2 adds a new dependency on Typed Data API enhancements. Please install Typed Data before proceeding with this update.
Configuration changes may be required
If your endpoint is set to anything other than "www.salesforce.com" or "test.salesforce.com", you will need to change it to one of those. "cs-", "na-", vanity URL endpoints are no longer supported.
* Fixed bug in delete handler that was preventing delete-pulls
* Fixes up local actions and paths for mapped entities
* Linter / coding style updates project-wide
* Bug fixes with missing "use" statements
* Issue #2903071 by gcb, aaronbauman: Add ability to trigger push on entities without object mappings
* Issue #2908992 by bartlangelaan: Users that can only authorize can't view menu links
* Issue #2908147: mis-named variable in deletehandler
New features:
- per-queue settings and push-processor URL callbacks
- expose Guzzle HTTP client options to RestClient
- config dependency framework for mappings and mapping field plugins
- Injectable soql-where clause for pull query
- Update RestClient to accommodate Apex endpoints
- Per-mapping queue settings for push an dpull
- Global settings form
- Bug fixes in pull queue handler
IMPORTANT: Move Salesforce OAuth config into "authorize salesforce" permission.
Non-administrator users' permissions need to be granted the new permission in
order to access OAuth.
Beta release to allow for further testing of the new merge handling. See the API docs for how to make use of this new feature. You will need to be able to create a custom object in Salesforce, a trigger in Salesforce, and implement a hook in Drupal.
In our first official release for Drupal 8, we've achieved some major milestones. APIs and schema are firming up, but still flexible. Expect future 8.x releases to include upgrade paths for database schema, if applicable.
The /admin/config/salesforce/settings page where you can configure which version of the API you're using. You can also configure pulls via a webhook instead of cron.
Additionally, the mappings pages have been cleaned up by Issue #1980688: Push/pull UI improvements. This removes the temptation to try to sync or push an item if, say, you only have the Salesforce Pull module enabled.
Time flies. In this case, we can't believe it's been nearly a year since the last full point release for the Salesforce module. As evidenced by the 150+ commits seen below, development certainly hasn't been idle! In addition to countless performance enhancements and bug fixes, this release features an all new Drupal entity mapping system which shows a log of all synchronization activity, including any errors. Administrators can even manually create a connection between Drupal and Salesforce objects.
This is ThinkShout's first ever real time module release. We're all sitting around at the end of our monthly open source sprint, celebrating this long awaited stable release. Enjoy!
Major new improvements include:
Decoupling bundles from record types.
Numerous performance improvements.
Improvements to relations handling.
Mappings are not deleted when there are problems with the sync.
Sorry for the excessive releases the past couple weeks. We're sprinting on a stable release with lots of organizations pitching in and issues have a habit of arising after the releases come out. We're getting close.
This major milestone release features significant performance improvements and bug fixes. Special thanks to kostajh (Design Hammer) and ceardach (Jackson River) for their significant contributions.
This is the first release of a complete rewrite of this module using the REST API, OAuth 2.0, and custom Drupal entities. More details can be found on this blog post.
There is not an upgrade path from previous versions of this module and ThinkShout does not have plans of providing one. That would be a welcome addition from the community.