Skip to content

Commit 714dfde

Browse files
authored
cleanup
1 parent 9982d49 commit 714dfde

File tree

1 file changed

+2
-3
lines changed
  • src/connections/destinations/catalog/actions-salesforce

1 file changed

+2
-3
lines changed

src/connections/destinations/catalog/actions-salesforce/index.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -159,9 +159,8 @@ When using the `create` operation, it's possible for duplicate records to be cre
159159

160160
Please note this is only a concern when using the `create` operation. You can use the `upsert` operation instead to avoid duplicates if `upsert` meets your needs.
161161

162-
## Why do I see undefined traits error?
163-
164-
When using the `update` operation, this error will occur if no value is past in the field that is set as Record Matcher. Please check that you have provided a value in the field that is set as the Record Matcher.
162+
### Why do I see "undefined traits" error?
163+
This error happens when you use the `update` operation, but no value is provided for the field defined as the Record Matcher. To fix this, make sure your payload includes a value for the Record Matcher field.
165164

166165
### How does Salesforce Bulk API work?
167166
When **Use Salesforce Bulk API** is enabled for your mapping, events are sent to [Salesforce’s Bulk API 2.0](https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/asynch_api_intro.htm){:target="_blank"} rather than their streaming REST API. If enabled, Segment will collect events into batches of up to 5000 before sending to Salesforce. Bulk support can be used for the `upsert` or `update` operations only.

0 commit comments

Comments
 (0)