You are here:
Mapping Intent Types
Context mapping connects your context structure (a logical data model) with real data. Mapping Intent specifies what you intend to do with this context mapping.
Required Editions
| Available in: Lightning Experience |
| Available in: Developer, Enterprise, Professional, and Unlimited editions for Industries clouds where Context Service is enabled |
Choose one or more of these intents: Hydration, Persistence, Translation, and Association.
- To read data from a data source (Salesforce objects/data model objects) into the context, select the Hydration intent. For the Hydration intent, both one-to-one and many-to-one mappings are supported.
- To write data from the context back to Salesforce objects, select the Persistence intent. For the Persistence intent, both one-to-one and one-to-many mappings are supported.
- To translate context data into a different format, select the Translation intent. For the Translation intent, both one-to-one and one-to-many mappings are supported. Usually, a context definition can have more than one mapping. Through translation, data that is hydrated using one mapping can be transformed into data corresponding to a different mapping. For example, data that is hydrated from the Quote object can be transformed to an Order mapping.
- To use the mapping metadata for your custom business logic, select the Association intent. With the Association intent, all kinds of mappings such as one-to-one, one-to-many, many-to-one, and cross-attribute mappings are supported. However, a mapping with the Association intent cannot be hydrated or persisted using out-of-the-box context APIs.
When you select more than one mapping intent, only the common mappings between the selected intents are supported. For example, if you select both the Translation intent and Hydration intent, then only one-to-one mapping is supported.
Did this article solve your issue?
Let us know so we can improve!

