IntegrationIntermediatemappingtransformationetl
Implement field-level integration mapping with transformation rules
Real World Scenario
SAP customer number format differs from Salesforce Account external ID causing sync mismatches.
Expected Answer
• Central mapping spreadsheet or CMDT Integration_Field_Map__mdt
• Transformation functions pad trim uppercase standardize
• Validation rejects unmapped required fields to quarantine
• Version mapping metadata with deploy pipeline
• Unit test each transformation edge case
• Document source to target lineage per field
• Change impact analysis when SAP changes format
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Central mapping spreadsheet or CMDT Integration_Field_Map__mdt. Transformation functions pad trim uppercase standardize. Pick based on your integration pattern and team capability. Ad hoc field mapping in each integration becomes inconsistent—centralize transformation catalog. Balance speed of delivery with maintainability.
Architect Perspective
Ad hoc field mapping in each integration becomes inconsistent—centralize transformation catalog.