Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Persist Context (POST)

Persist a context by passing the context ID.

Resource

1/connect/contexts/persist-records

Example for POST

1https://yourInstance.salesforce.com/services/data/v67.0/connect/contexts/persist-records

Available version

59.0

Requires Chatter

HTTP methods

POST

Request body for POST

JSON example

1{
2  "contextPersistInput": {
3    "contextId": "384fdcef-36e2-4bbb-82ed-2e7bc4e670c7",
4    "targetMappingId": "11jxx0000004Q83AAE"
5  }
6}

Properties

Name	Type	Description	Required or Optional	Available Version
`contextPersistInput`	Object	Contains contextId and targetMappingId for persisting context.	Required	59.0

JSON example

1{
2  "contextId": "384fdcef-36e2-4bbb-82ed-2e7bc4e670c7",
3  "targetMappingId": "11jxx0000004Q83AAE"
4}

Response body for POST

Persist Context Output

When updating reference fields within a context and attempting to persist the context, changes to the reference field itself may not be persisted. This is because reference fields point to related entities, and the persist operation primarily focuses on the attributes of the main entity within the context.

For example, if you have an Order context with a reference field to an Account, updating the Account reference within the Order context and then calling the persist API may not save the updated Account reference. Other attributes of the Order might be persisted, but the relationship to the Account might not be.

Note

Industries Common Resources Developer Guide

Persist Context (POST)