OmniStudioAdvanceddataraptorperformancehealth-insurance
Optimize DataRaptor Extract for large Account hierarchies in health insurance
Real World Scenario
Group health enrollment Extract DR queries Account with 15 related Contacts Policies Coverages; OmniScript prefill exceeds 8 seconds for 500-employee groups.
Expected Answer
• Extract DR query only fields OmniScript step needs not full object
• Separate Extract DRs per step lazy load not one mega Extract
• Filter related lists WHERE active policies only reduce volume
• Turbo DR only after profiling proves bottleneck
• Platform Cache group roster Extract TTL 15 minutes enrollment session
• Bulk Extract batch headless renewal not interactive prefill pattern
• Governor limit test Extract with max-size employer sandbox
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Extract DR query only fields OmniScript step needs not full object. Separate Extract DRs per step lazy load not one mega Extract. Pick based on your integration pattern and team capability. Mega Extract DR is OmniStudio LDV anti-pattern—step-scoped Extracts with minimal fields. Optimize for scale and operational observability.
Architect Perspective
Mega Extract DR is OmniStudio LDV anti-pattern—step-scoped Extracts with minimal fields.