Overview
This integration transfers Location records from Prophet 21 to iPaaS. The integration ensures that new Locations created or updated in Prophet 21 are automatically reflected in iPaaS. This supports consistent location-based segmentation, reporting, and operational mapping across both systems.
ID Format
When manually transferring a Location from a Prophet 21 to iPaaS, navigate to the Manual Sync page and enter the Prophet 21 Location ID in the iPaaS.com input field.
External ID Format: The Location ID serves as the External ID in iPaaS. For example: 2.
Mapping Collection Status
Mapping Status: Enabled.
Trigger Events: Create, Update.
Duplicate or Conflicting Mappings
This mapping applies only to Locations from Prophet 21. Ensure no other mappings target the same iPaaS Location entity to prevent data from being overwritten.
Supported Child Collections
This integration does not support any child collections.
System Caveats
Prophet 21 Caveats
Location Name must be unique to prevent overwriting an existing iPaaS Location record.
Missing or invalid names can lead to sync failures.
iPaaS Caveats
iPaaS requires a valid Name field for each Location.
Setup Requirements
Prophet 21 Configuration
Ensure all Locations in Epicor Prophet 21 include a proper LocationName, as this is a required mapped value.
iPaaS Configuration
iPaaS Locations must contain a valid Name value.
Authentication and 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 processes Prophet 21 locations as follows:
The integration is triggered when a Location is created or updated in Prophet 21.
Location data is fetched from Prophet 21 using the API.
Field mappings are applied to transform Prophet 21 data to iPaaS format.
The Name field is validated to ensure it is present and non-duplicate.
The Location is inserted or updated in iPaaS.
Upon successful transfer, the Prophet 21 Location ID is saved as the External ID in iPaaS.
Mappings
Prophet 21 Add Location TO iPaaS
Description
This mapping collection transfers location data from Prophet 21 to iPaaS. This is a simple single-field mapping.
Mapping Type | Source Field (Prophet 21) | Destination Field (iPaaS.com) | Description |
Field | Name | Name | Maps the Prophet 21 Location Name to the iPaaS Location Name. This is a required field. |
Error Handling
Missing Name
Name field is missing or empty.
Description: iPaaS requires a valid Name to create a Location entry. The sync cannot proceed without this field.
Resolution: Update the Prophet 21 Location record to include a valid Name before syncing.
Duplicate Name
A Location with the same Name already exists in iPaaS.
Description: Duplicate names cause update conflicts or payload rejection. iPaaS requires unique Location names.
Resolution: Ensure unique naming in Prophet 21, or modify the existing Location Name in iPaaS before re-syncing.
Validation & Testing
Before deploying this integration, verify the following configuration items and run the test scenarios to confirm proper operation.
Validation Checklist
Name is populated and not empty.
Location Name is unique across all synced locations.
External ID is saved after successful sync.
Test Scenarios
Scenario 1: New Location Sync
Create a new Location in Prophet 21 with a unique Name. Sync to iPaaS and verify the Location appears correctly with the Name field populated.
Scenario 2: Update Existing Location
Modify the Name of an existing Location in Prophet 21. Sync to iPaaS and verify the changes are reflected without creating a duplicate record.
Scenario 3: Empty Name Validation (Failure Case)
Attempt to sync a Location with an empty Name field. Verify the system returns an appropriate error message, and the sync is prevented.
Scenario 4: Duplicate Name Validation (Failure Case)
Attempt to sync a Location with a Name that already exists in iPaaS. Verify the system returns an appropriate error message indicating a duplicate name conflict.
Additional Notes
No child collections or additional attributes are part of this mapping.
Location names should be unique in both systems to prevent sync conflicts.