DataRaptors are part of the architectural service management layer and is basically a mapping tool that enables data to be read, transformed and written to Salesforce.

In a typical process, we will extract the data, display the data, if data got modified we will post the update back.

Dataraptor data are normally displayed in UI views such as OmniScripts and FlexCards. There is a Integration Procedure acting as the middle man for the data and giving it to the UI to use and vice versa if data needs to be written back.

Apex vs DataRaptors

• Both can read, write and transform data. DataRaptor being more easier to create and maintain. No need for unit test.
• You can create JOIN or UNION with data from Salesforce objects.
• You can insert Parent-Child records in one DataRaptor.
• Transform API data or subset of it before it can be used in a UI
• Platform Cache support

Types of DataRaptors

Turbo Extract

Extract

Load

Transform

Use Cases

Summary

We will use different DataRaptor types depending on the job.

If we need data, we use Extract, depending on the type of object or objects being extracted we use different DataRaptor Turbo Extract or just plain DataRaptor Extract.

If we need to transform the data, we use Transform.

If we need to update data, we use Load.