Salesforce Subscriber
In this article
Overview
The Salesforce Subscriber Snap is a Read-type Snap that provides the functionality to subscribe to Salesforce Platform and CDC events for a given standard and custom Salesforce object.
Â
Refer to the Salesforce Platform Event Allocations and Subscribe to change events documents before configuring this Snap.
Supported Salesforce Events
Custom Platform events: User-defined read/write events. These events end with
"__e"
.CDC events: Read-only events created when the Salesforce objects (standard or custom) change. These events end with
"ChangeEvent"
or"__ChangeEvent"
.
There are two underscore characters in "__e"
and "__ChangeEvent"
Prerequisites
Ensure that Change Data Capture is enabled for the target entities. Log in to your Salesforce instance and navigate to Setup → App Setup → Develop → Change Data Capture.Â
Ensure that Field Tracking is enabled for the selected entities.
Account must have valid access permissions.
Limitations and Known Issues
For a Salesforce (Platform Events) Subscriber Snap, retry attempts are not logged, and currently, retries are attempted only for authentication errors.
Salesforce imposes a limit on the number of subscriptions. See Change Data Capture Allocations for details.
Supports only Platform and CDC events.
Behavior Change
From the 4.30 release onwards, the Snap stops and reports the error immediately when it encounters the daily limit exceeded
error. Earlier, the Snap reported an error and stopped only at the next resubscribe attempt when it encountered the daily limit exceeded
error.
Support for Ultra Pipelines
Works in Ultra Pipelines.
Snap Views
Type | Format | Number of Views | Examples of Upstream and Downstream Snaps | Description |
---|---|---|---|---|
Input | Document |
|
| This Snap at the most can have only one input document that contains data to be listened on a Salesforce object. |
Output | Document |
|
| A document with Map data that contain the individual records subscribed on the given Salesforce object and/or |
Snap Settings
Field | Field Type | Description |
---|---|---|
Label*
| String | Specify the name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline. Â |
Service Version*
| String/Expression | Specify the version number of the Salesforce service that you want to connect to. Salesforce platform event is supported in version 44.0 or later.  |
Events*
| String/Expression | Specify the Salesforce Platform event or CDC event. This is a suggestible field that lists the Platform Events and CDC events available to you.  You can select the name from the suggested list in the drop-down menu. The supported Salesforce events are:
|
Replay ID*
| Integer/Expression | Specify the position of an event in the event stream. The Snap supports the following IDs:
If you stop a Pipeline execution, the Replay ID is lost and the Snap restarts from the position you input here. |
Message Count*
| Integer/Expression | Specify the number of messages required to read and complete the Pipeline execution. Â |
Pass Through
| Checkbox | Select this checkbox to pass the input document the output view under the key 'original'. If you deselect this checkbox, the input document will not be passed and there is no " Â |
Advanced Properties | Use this fieldset to configure Http Long Polling. | |
Properties
| String | Specify the property or select from the suggestion list. Â |
Values Default Value: N/A | String | Specify the value for the property. Â |
Snap Execution
| Dropdown list | Select one of the following three modes in which the Snap executes:
|
Troubleshooting
Error | Reason | Resolution |
| Client is not authorized to access the server due to either a domain mismatch or authentication failure. | Configure the Enhanced Domain in the Instance URL property to ensure authentication for successful access to the server. |
Example
Process Platform Events in Salesforce
This example Pipeline demonstrates how the Salesforce Subscriber Snap processes platform events. The following Salesforce Subscriber Snap shows how the Snap is configured and how the Salesforce object's records are read.
You can see that the Replay ID is -2. So the Snaps reads messages from the beginning. And the Snap reads only 3 messages as the Message count is set to 3.The Snap processes the events and the output preview is as follows:
Downloads
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.