---
id: 49d3de63-9123-4d3b-b45b-614927b6afe3
type: fix
title: "sf-ca.json mapping config: copy-paste bug in Contact required_platform_fields + missing CloudSQL fields"
tags: [esb-monorepo, sf-ca, object-handler, mapping, bug, fix]
importance: 0.7
confidence: 0.8
created: "2026-02-26T18:57:20.932938+00:00"
updated: "2026-02-26T18:58:17.935724+00:00"
relations:
  - target: ca8d0390-7ff9-4ca7-b033-3656d653c2be
    type: RELATED_TO
    direction: incoming
    strength: 0.8
    edge_id: 6d3dfef5-7a75-47e5-a812-ab7577b6d42b
  - target: 65cdb31b-e86f-4465-a321-378e1f704e6f
    type: CAUSES
    direction: outgoing
    strength: 0.85
    edge_id: bfe2c279-396c-4984-9867-a15f0d7895c8
  - target: 5ac9e4b8-d83f-4409-8f61-224027e1156b
    type: RELATED_TO
    direction: outgoing
    strength: 0.7
    edge_id: 49966d04-cbd2-496f-9530-6b91a50cc6ba
---

# sf-ca.json Mapping Config: Known Issues

## File Location
`packages/py-esb-integrations/src/esb_integration/mappings/sf-ca.json`

## Current State
Mapping already exists with:
- Account -> CommercialAquaticsAccount
- Contact -> ContactStaff

Both types are already registered in `VALID_OBJECT_TYPES` and `ObjectFactory`.

## Bug 1: Copy-Paste Error in Contact required_platform_fields
Contact's `required_platform_fields` includes Account-specific fields that are NOT present in Contact's `field_aliases`:
- `Account_Status__c`
- `Operating_Entity__c`
- `Primary_Email__c`

These are Account fields that were likely copied when the Contact block was scaffolded. Will cause validation failures at runtime.

## Bug 2: Missing CloudSQL Routing Fields
Both Account and Contact mappings are missing:
- `db_platform_code`
- `db_source_code`

These fields are required for CloudSQL silver layer routing. Will be addressed in ESB-51 after real Salesforce data confirms actual field names from the SF-CA instance.

## Resolution Plan
Defer fixes to ESB-51 — need real raw data from the Salesforce CA instance before finalizing field names.