OmniStudioIntermediatedataraptoretlomnistudio
Explain DataRaptor Extract vs Load vs Transform vs Turbo design patterns
Real World Scenario
Developers debate whether to use one Turbo DataRaptor for entire policy object graph or separate Extract and Load DRs.
Expected Answer
• Extract DR: read Salesforce or external JSON into OmniScript-friendly JSON structure
• Load DR: map OmniScript JSON to Salesforce DML create/update with upsert keys
• Transform DR: reshape JSON without external query—middle tier mapping
• Turbo DR: combined extract-transform-load in one for simpler flows when debuggability less critical
• Prefer separate Extract/Load for testability and reuse across OmniScripts
• Bulk-safe Load DR handling lists not single record assumptions
• Document DR interfaces as contracts between OmniScript and IP
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Extract DR: read Salesforce or external JSON into OmniScript-friendly JSON structure. Load DR: map OmniScript JSON to Salesforce DML create/update with upsert keys. Pick based on your integration pattern and team capability. Turbo DR trades clarity for speed—architects default to explicit Extract/Load until performance proves otherwise. Balance speed of delivery with maintainability.
Architect Perspective
Turbo DR trades clarity for speed—architects default to explicit Extract/Load until performance proves otherwise.