For the managed package runtime, Data Mapper Extract examples demonstrate object relationships, paging with data values, paging with offsets, working with attributes, and relationship notation.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
For additional examples that show how you can improve Data Mapper performance for some use cases using relationship notation, see Relationship Notation versus Multiple Extract Steps (Managed Package).
- Create a Basic Omnistudio Data Mapper Extract Example (Managed Package)
For the managed package runtime, a Data Mapper extract accepts an account ID parameter and returns the account name. - Extract Data from Three Related Objects (Managed Package)
For the managed package runtime, create an Omnistudio Data Mapper Extract for use by a Case-handling Omniscript. The agents who handle Cases can look up an Account, list all the Cases for the Account, and find the Contact for each Case. - Page Through Sorted Data Using Data Values (Managed Package)
For the managed package runtime, if an Omnistudio Data Mapper Extract is expected to retrieve a lot of records, you can use paging to retrieve a few at a time based on field values. For example, you can page through Accounts by Id. - Page Through Sorted Data Using Offsets (Managed Package)
For the managed package runtime, if an Omnistudio Data Mapper Extract is expected to retrieve a lot of records, you can use paging to retrieve a few at a time based on OFFSET values. For example, you can page through Contacts by last name. - Extract Account Attribute Data (Managed Package)
For the managed package runtime, an Omnistudio Data Mapper accepts an Account Id and returns Profile Attribute values for that Account. - Extract Multiple Relationship Levels and Custom Field Values (Managed Package)
For the managed package runtime, suppose you want to retrieve Contract data that includes the Version (parent) and the name of the user (grandparent) who created the Contract. You can use relationship notation with custom fields. - Extract from Multiple Related Custom Objects (Managed Package)
For the managed package runtime, although relationship notation is different for standard and custom fields, it is exactly the same for standard and custom objects. This example extracts data from three custom fields of the vlocity_cmt__CatalogProductRelationship__c SObject.