Overview
This integration transfers Customer records from iPaaS to Prophet 21. The integration supports the creation of Customer data in Prophet 21 based on changes made within the iPaaS Customer entity. This ensures both platforms maintain consistent and accurate customer information.
Mapping Collection Status
Mapping Status: Enabled.
Trigger Events: Create, Update
ID Format
When manually transferring data from iPaaS to Prophet 21, enter the iPaaS Customer ID in the input field (for example, 10001). The iPaaS Customer ID is used directly without any suffix.
Duplicate and Conflicting Mappings
This mapping applies only to Customers from iPaaS. Ensure no other mappings target the same Prophet 21 Customer entity to prevent data from being overwritten.
External ID Format: The Prophet 21 Customer ID serves as the external ID. For example: 449543.
Supported Child Collections
This parent mapping collection supports the following child collection:
Prophet 21 Customer Address Add From iPaaS
System Caveats
iPaaS Caveats
iPaaS requires a unique CustomerNumber for each customer.
EmailAddress must be unique across customers to avoid sync failures.
Prophet 21 Caveats
Prophet 21 allows duplicate emails, but this may cause confusion during lookup.
The Name field in Prophet 21 may require a combined name, which is generated using a dynamic formula.
Setup Requirements
iPaaS Configuration
Ensure CustomerNumber, FirstName, LastName, and EmailAddress are present before syncing.
Comments should be stored in the standard Comment field to map correctly into Prophet 21 Notes.
Prophet 21 Configuration
API calls may fail if required fields are missing.
Authentication & Security
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
The integration is triggered when a Customer is created or updated in iPaaS, or manually initiated.
Customer data is fetched from iPaaS.
Field and dynamic formula mappings are applied to transform iPaaS data.
The Name field is generated by combining FirstName and LastName using a dynamic formula.
Child collections (Customer Address) are processed.
The Customer and Address records are created or updated in Prophet 21.
Mappings
Parent: Prophet 21 Add Customer FROM iPaaS.com(Parent)
Description
This mapping collection transfers customer data from iPaaS to Prophet 21.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Prophet 21) | Description |
Field | FirstName | FirstName | Maps the iPaaS FirstName to the Prophet 21 FirstName. |
Field | LastName | LastName | Maps the iPaaS LastName to the Prophet 21 LastName. |
Field | EmailAddress | EmailAddress | Maps the iPaaS EmailAddress to the Prophet 21 EmailAddress. |
Dynamic Formula |
| Name | Combines FirstName and LastName into a full name, adding a space only if LastName is not empty or whitespace. |
Child: Prophet21 Add Customer Address FROM iPaaS.com(Child)
Description
This mapping collection transfers address data from iPaaS customers to Prophet 21 Customer addresses.
Mapping Type | Source Field (iPaaS) | Destination Field (Prophet 21) | Description |
Field | Address1 | MailAddress1 | Maps the iPaaS Address1 to the Prophet 21 MailAddress1. |
Field | Address2 | MailAddress2 | Maps the iPaaS Address2 to the Prophet 21 MailAddress2. |
Field | Address3 | MailAddress3 | Maps the iPaaS Address3 to the Prophet 21 MailAddress3. |
Field | City | MailCity | Maps the iPaaS City to the Prophet 21 MailCity. |
Field | Region | MailState | Maps the iPaaS Region to the Prophet 21 MailState. |
Field | Country | MailCountry | Maps the iPaaS Country to the Prophet 21 MailCountry. |
Field | PostalCode | MailPostalCode | Maps the iPaaS PostalCode to the Prophet 21 MailPostalCode.Maps the iPaaS PhoneNumber to the Prophet 21 CentralPhoneNumber. |
Field | PhoneNumber | CentralPhoneNumber |
|
Dynamic Formula |
| Name | Selects the best available value for display name, prioritizing: Company, Parent.Company, full name (FirstName + LastName), first name only, last name only, then Address1 as fallback. |
Error Handling
Dynamic Formula Failure
Full name or address name cannot be generated.
Description: One or more dependent fields may be missing
Resolution: Verify FirstName, LastName, and Address fields exist.
Validation & Testing
Before deploying this integration, verify the following configuration items and run the test scenarios to confirm proper operation.
Validation Checklist
CustomerNumber is present and unique.
FirstName and/or LastName are populated for Name generation.
EmailAddress is present and unique.
Address fields are populated for the child collection.
Dynamic formulas generate correct Name values.
PhoneNumber is a valid format (if provided).
Test Scenarios
Scenario 1: New Customer Sync
Create a new customer in iPaaS with CustomerNumber, FirstName, LastName, and EmailAddress. Sync to Prophet 21 and verify the customer appears with the correct parent and child fields.
Scenario 2: Update Customer
Modify the email or name fields in iPaaS for an existing customer. Sync to Prophet 21 and verify changes are reflected without creating duplicates.
Scenario 3: Dynamic Formula Test
Modify FirstName and LastName in iPaaS. Sync to Prophet 21 and verify the Name field generates correctly with proper spacing.
Scenario 4: Address Sync
Create a customer with address fields in iPaaS. Sync to Prophet 21 and verify the address appears correctly with all fields mapped.
Scenario 5: Missing Name Fields
Attempt to sync a customer with only FirstName (no LastName) or only LastName (no FirstName). Verify the Name field handles gracefully without errors.
Scenario 6: Duplicate Email (Warning Case)
Sync a customer with an email that already exists in Prophet 21. Verify the sync completes, but note the duplicate email behavior for lookup purposes.
Additional Notes
While Prophet 21 allows duplicate emails, using unique email addresses is recommended to avoid lookup confusion.