Map Context Definitions

To map a context definition, select a node and an attribute, and then select the corresponding Salesforce object of input data source to begin the process of fetching data.

Important

• Map the nodes first and then map the attributes.
• If you delete a mapping for a node, the mappings of the attributes associated with the node are also deleted.

• Mapping Types
  Mapping types specify where to retrieve data for your context definitions. You can map all context definitions to a source object. The source object can be a standard object, data model object, context definition object, or any other input data source that you choose. Map your definition automatically or manually.
• 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.
• View and Edit Saved Context Mapping
  All your mappings are stored on the Map Data tab of your context definition.
• Add Context Mapping
  To make sure that your nodes and attributes are updated with the right input data, Salesforce objects, or context definition objects, create a mapping structure for your context definition.
• Object Field Data Types Mapping to Attribute Data Types
  When you map nodes and attributes in a context definition to their source data using a mapping structure, you can map the fields only when the data type of the attribute matches with the supported data type of the object's field.
• Clone a Context Mapping
  Save time and reduce manual effort by reusing existing mappings in context definition setup. Simplify the mapping by cloning context mappings for standard objects, context definition objects, data model objects, or any other input data source.
• Map to a Custom Data Space
  For extended context definitions, switch mapped Data Model Objects (DMOs) from the default Data Space to corresponding DMOs in a custom Data Space in your org.