IntegrationIntermediaterestpatchpartial-update
Implement REST PATCH partial update semantics for integration efficiency
Real World Scenario
Integration sends full Account 80-field JSON on every address change wasting bandwidth and triggering unnecessary validation rules.
Expected Answer
• PATCH sObject only changed fields in request body
• Null explicit field clear if business requires
• PUT replaces entire record rarely appropriate integrations
• Composite PATCH batch multiple partial updates
• Field-level change detection middleware before Salesforce call
• Reduce trigger execution only changed fields fire relevant logic
• Document PATCH contract partner integration guide
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. PATCH sObject only changed fields in request body. Null explicit field clear if business requires. Pick based on your integration pattern and team capability. PATCH partial update reduces trigger noise and payload size—default integration pattern. Balance speed of delivery with maintainability.
Architect Perspective
PATCH partial update reduces trigger noise and payload size—default integration pattern.