Overview
This integration transfers customer records from the Prophet 21 Contact entity to the iPaaS Customer entity. The integration uses an API-based sync that triggers whenever a contact record is created or updated in Prophet 21. The purpose of this mapping is to ensure that customer data remains consistent and up to date across both systems.
Mapping Collection Status
Mapping Status: Enabled.
Trigger Events: Create, Update.
ID Format
When manually syncing, the correct Prophet 21 Contact ID must be entered (e.g., Contact with ID 12345 must be entered as 12345). The contact ID serves as the external ID in iPaaS.com
Duplicate and Conflicting Mappings
This mapping applies only to Customers. Ensure no other mappings target the same iPaaS entity to prevent data from being overwritten.
System Caveats
Prophet 21 Caveats
Ensure basic contact fields (FirstName, LastName, Email) are properly maintained to avoid sync failures.
iPaaS Caveats
The CustomerNumber must be unique across all customer records.
The Company Name is optional but recommended for business customers.
Setup Requirements
Prophet 21 Configuration
EmailAddress must be populated for each Customer intended for syncing.
iPaaS Configuration
CustomerNumber, FirstName, LastName, and EmailAddress are required fields.
Authentication & Security
Epicor Prophet 21 uses username and password authentication to access the iPaaS API. These credentials authorize all Prophet 21 API requests during transfer operations
Integration Flow
Retrieve Data: Contact records are fetched from Prophet 21.
Email Check: If the Contact does not contain an EmailAddress, the transfer is skipped.
Apply Mapping Logic: Contact fields such as CustomerNumber, FirstName, LastName, Email, and Company are mapped.
Send to iPaaS: Create or update the Customer in iPaaS.
Process Child Addresses: Contact address entries are mapped and created under the parent Contact.
Mappings
Add/Update Customer To iPaaS.com(Parent)
Description
This mapping collection transfers contact data from Prophet 21 to iPaaS as Customer records. The transfer only proceeds if the Contact has a valid EmailAddress.
Mapping Type | Source Field (Prophet 21) | Destination Field (iPaaS.com) | Description |
Field | Id | CustomerNumber | Maps the Prophet 21 Contact Id to the iPaaS CustomerNumber. This is a required field. |
Field | FirstName | FirstName | Maps the Prophet 21 FirstName to the iPaaS FirstName. |
Field | LastName | LastName | Maps the Prophet 21 LastName to the iPaaS LastName. |
Field | EmailAddress | Maps the Prophet 21 Email to the iPaaS EmailAddress. This is a required field. | |
Field | AddressName | Company | Maps the Prophet 21 AddressName to the iPaaS Company. |
Add/Update Customer Address To iPaaS.com
Description
This mapping collection transfers address data from Prophet 21 contacts to iPaaS Customer Address records.
Mapping Type | Source Field (Prophet 21) | Destination Field (iPaaS.com) | Description |
Static | true | PreventDuplicate | Sets the iPaaS PreventDuplicate to true to avoid duplicate address entries. |
Field | MailAddress1 | Address1 | Maps the Prophet 21 MailAddress1 to the iPaaS Address1. |
Field | MailAddress2 | Address2 | Maps the Prophet 21 MailAddress2 to the iPaaS Address2. |
Field | MailAddress3 | Address3 | Maps the Prophet 21 MailAddress3 to the iPaaS Address3. |
Field | MailCity | City | Maps the Prophet 21 MailCity to the iPaaS City. |
Field | MailState | Region | Maps the Prophet 21 MailState to the iPaaS Region. |
Field | MailCountry | Country | Maps the Prophet 21 MailCountry to the iPaaS Country. |
Field | MailPostalCode | PostalCode | Maps the Prophet 21 MailPostalCode to the iPaaS PostalCode. |
Field | IsPrimaryBilling | IsPrimaryBilling | Maps the Prophet 21 IsPrimaryBilling to the iPaaS IsPrimaryBilling. |
Field | IsPrimaryShipping | IsPrimaryShipping | Maps the Prophet 21 IsPrimaryShipping to the iPaaS IsPrimaryShipping. |
Error Handling
Missing EmailAddress
Contact record in Prophet 21 has no EmailAddress.
Description: The mapping filter requires EmailAddress to be present for the transfer to proceed.
Resolution: Populate EmailAddress in Prophet 21; sync will proceed automatically in the next cycle.
Validation Rules & Testing
Before deploying this integration, verify the following configuration items and run the test scenarios to confirm proper operation.
Validation Checklist
Contact has a valid EmailAddress.
CustomerNumber (Contact Id) is numeric and unique.
FirstName or LastName is populated.
Address fields are complete (if syncing addresses).
The IsPrimaryBilling and the IsPrimaryShipping flags are set correctly.
Test Scenarios
Scenario 1: New Contact with Email
Create a new Contact in Prophet 21 with FirstName, LastName, and EmailAddress populated. Verify the Customer is created in iPaaS with correct data.
Scenario 2: Contact without Email (Failure Case)
Create a Contact in Prophet 21 without an EmailAddress. Verify the mapping filter blocks the transfer.
Scenario 3: Update Email Address
Update the EmailAddress for an existing Contact in Prophet 21. Verify the corresponding Customer is updated in iPaaS.
Scenario 4: Add New Address
Add a new address to an existing Contact in Prophet 21. Verify the Address child record is created in iPaaS under the parent Customer.
Scenario 5: Update Existing Address
Modify address fields for an existing Contact. Verify the Address is updated in iPaaS.
Additional Notes
The Company field is optional but helpful for business classification in iPaaS.