Salesforce→Ordway: “Customer cannot be a descendant of itself” (Parent Mapping Fix)

Summary

Customer syncs were failing with HTTP 422 – Invalid Attributes and the message:

Customer cannot be a descendant of itself.

Root cause: the Parent Customer Id field in the Customers Mapping was pointed to Parent (Relationship) instead of the Parent Account ID. This caused the payload to sometimes set parent_customer equal to the same customer, creating a self‑parent loop rejected by Ordway.

After switching the mapping to Parent Account ID, syncs completed successfully. We will close the Zendesk case #19263 once the customer confirms.

Symptoms

• Salesforce→Ordway Customer sync fails.
• Application Log shows Status Code => 422 with details Customer cannot be a descendant of itself.
• Payload shows the same value for id and parent_customer.

Example (from logs):

Root Cause

In Integrations → Salesforce → To Ordway → Customers Mapping, the Ordway → Parent Customer Id was mapped to Salesforce → Parent (Relationship). That relationship field is not the ID and, in certain cases (e.g., when Parent is blank or improperly resolved), the integration produced a payload with the child’s own ID as parent_customer, resulting in a self‑reference.

Diagnosis Checklist

1. Open the Application Logs record for the failure and verify 422 with detail Customer cannot be a descendant of itself.
2. Inspect the payload and confirm parent_customer equals the same value as id.
3. Review Customers Mapping screen and check the Parent Customer Id mapping source.
   • Problematic: Parent (Relationship)
   • Correct: Parent Account ID

Resolution (Mapping Change)

1. Go to Ordway → Settings → Integrations → Salesforce → To Ordway tab.
2. Select Customers → locate Parent Customer Id.
3. Change Salesforce source from Parent (Relationship) to Parent Account ID.
4. Leave other related fields as‑is (e.g., Bill to Parent, CSM (From Parent)).
5. Save the mapping.
6. Re‑run the failed sync (or trigger a resync of the affected Account).

✅ Expected Result: Sync completes and no longer raises the self‑descendant error.