LWCIntermediaterecord-formdmlui-api
Handle record edit forms with lightning-record-edit-form vs custom
Real World Scenario
Complex conditional field visibility requirements exceed lightning-record-edit-form capabilities.
Expected Answer
• lightning-record-edit-form for standard save with minimal code respecting FLS
• lightning-input-field auto layout and validation rule integration
• Custom form when dynamic sections, cross-field logic, or multi-object save needed
• uiRecordApi updateRecord for headless save from custom fields
• Handle submit success refresh notifyRecordUpdateAvailable for LDS siblings
• Mobile layout testing for long forms with sections
• Governor-safe bulk not applicable—single record UX focus
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. lightning-record-edit-form for standard save with minimal code respecting FLS. lightning-input-field auto layout and validation rule integration. Pick based on your integration pattern and team capability. Start with record-edit-form—custom forms inherit validation and FLS burden. Balance speed of delivery with maintainability.
Architect Perspective
Start with record-edit-form—custom forms inherit validation and FLS burden.