Persist Context (POST)
Context Query Tags Leaner (POST)
Context Attribute Input
IndustriesSettings
Industries Object Access by Community License
Access Industries Features Deployed Using Managed Packages
Previous Versions
Persist a context by passing the context ID.
1/connect/contexts/persist-records1https://{yourInstance}.salesforce.com/services/data/v68.0/connect/contexts/persist-records{yourInstance} is the domain name of your Salesforce instance.
59.0
No
POST
1{
2 "contextId": "384fdcef-36e2-4bbb-82ed-2e7bc4e670c7",
3 "targetMappingId": "11jxx0000004Q83AAE"
4}1{
2 "contextPersistInput": {
3 "contextId": "384fdcef-36e2-4bbb-82ed-2e7bc4e670c7",
4 "targetMappingId": "11jxx0000004Q83AAE"
5 }
6}| Name | Type | Description | Required or Optional | Available Version |
|---|---|---|---|---|
contextPersistInput | Object | Contains contextId and targetMappingId for persisting context. | Required | 59.0 |
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