cal/claude-memory
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity
0d83ca6242
claude-memory/graph/problems/sf-ca-contact-required-platform-fields-bug-in-sf-cajson-d0ac99.md

1.6 KiB
Raw Blame History

id type title tags importance confidence created updated relations
d0ac9986-d5a7-4c38-acb2-5110abcbc870 problem SF-CA Contact required_platform_fields bug in sf-ca.json
esb
sf-ca
bug
object-handler
salesforce
commercial-aquatics
0.7 0.8 2026-03-04T17:05:56.120852+00:00 2026-03-04T17:05:57.723346+00:00
target type direction strength edge_id
d2a6c0e5-28b1-4c2a-a108-b8fcb7b8c0e1 SOLVES incoming 0.77 4511a8f3-b63c-4f74-a820-41e4bb9921cd
target type direction strength edge_id
39379120-896b-46cd-befa-b83d09d7556b RELATED_TO outgoing 0.69 4938021f-1da7-4e9d-9e81-935228cbf805
target type direction strength edge_id
62ee21e8-2b56-4d38-a73d-47e2724f08c6 SOLVES incoming 0.69 288b660f-704c-4cff-a560-1646a2c08434

Bug: Contact required_platform_fields references Account fields

In packages/py-esb-integrations/src/esb_integration/mappings/sf-ca.json, the Contact mapping has:

"required_platform_fields": ["Name__c", "Account_Status__c", "Operating_Entity__c", "Primary_Email__c"]

Account_Status__c, Operating_Entity__c, and Primary_Email__c are Account fields — they are NOT in Contact's field_aliases. This will cause validation failures when the Object Handler processes Contact records if it enforces required_platform_fields as a presence check.

Location

  • File: packages/py-esb-integrations/src/esb_integration/mappings/sf-ca.json line 42
  • Related story: ESB-51 (Object Handler configuration)

Action needed

  • Investigate whether these are intentional cross-object references or a copy-paste error
  • Fix during ESB-51 implementation