top of page
  • Writer's pictureKhaled McGonnell

DataRaptors vs Integration Procedures

OmniStudio provides both DataRaptors and Integration Procedures for (basically) extract, transform, and load (ETL) functionality. The following guide is intended to help you decide which is best for a given use case.

DataRaptors are better than Integration Procedures in the following circumstances:

  1. Data transformation and mapping: DataRaptors excel at transforming and mapping data within Salesforce Industries. They allow you to define complex data mappings and transformations, enabling you to move and manipulate data more effectively between objects and external systems.

  2. Reusability: DataRaptors promote reusability as they can be used across different processes and workflows. This helps reduce the effort of creating multiple data mappings and transformations for similar tasks, making the development process more efficient.

  3. Performance: DataRaptors are designed for high-performance data extraction and loading, enabling the handling of large volumes of data more effectively than Integration Procedures. It's particularly satisfying to be able to say this in 2023 as it was only a few years ago that the terms "high-performance" and DataRaptor would never have been seen together.

  4. Easy-to-use interface: DataRaptors offer a user-friendly interface that allows developers to define complex data mappings and transformations without writing code.

Integration Procedures, on the other hand, are better suited for the following circumstances:

  1. Complex business logic: Integration Procedures can handle complex business logic and calculations beyond simple data mappings and transformations. If your requirements involve executing complex business rules and logic, Integration Procedures are a better choice.

  2. Workflow integration: Integration Procedures can be easily incorporated into Salesforce Industries' workflow engine, allowing for seamless execution of business processes that require data manipulation.

  3. Event-driven execution: Integration Procedures can be triggered by specific events or actions, making them more suitable for use cases where data manipulation should occur as a result of particular events.

In summary, DataRaptors are better suited for data transformation, mapping, and high-performance ETL tasks, while Integration Procedures are more appropriate for handling complex business logic, workflow integration, and event-driven execution. The choice between the two depends on your specific needs and requirements within the Salesforce Industries platform.



Post: Blog2_Post
bottom of page