Summary
You can automatically transfer Warehouse entity records from Acumatica to iPaaS.com using an API-based sync. This process is supported by the iPaaS.com Warehouse API endpoint.
Field Constraints
Name: Must be a unique string and cannot be null.
Description: An optional string.
Mapping Collection Status
Status: Enabled
Trigger Events: Warehouse Create, Update
Id Format
When manually transferring data to iPaaS.com for an Acumatica Warehouse, such as Main Warehouse with ID 10, you must enter the correct Warehouse ID (e.g., 10) into the iPaaS.com input field on the manual sync page.
System Caveats
Acumatica Caveats
Must be unique per branch if multi-branch enabled.
iPaaS.com Caveats
Duplicate Warehouse Names will cause conflicts.
Null or empty Name fields will reject the record.
Integration-Specific Caveats
Error handling required for duplicate detection.
Name truncation or validation logic needed if length exceeds limit.
Setup Requirements
Acumatica Configuration
Enable Warehouse entity in Acumatica API.
Ensure each warehouse has a valid Name.
iPaaS.com Configuration
Enable Warehouse mapping collection.
Configure duplicate detection rules.
Authentication & Security
OAuth 2.0 / API Key: Required for both Acumatica and iPaaS.com endpoints.
Integration Flow
A new or updated warehouse record is created in Acumatica.
An API event automatically triggers a sync to iPaaS.com.
The Name and Description fields are then transferred.
Validation checks (length and uniqueness) are applied.
Finally, the warehouse record is created or updated in iPaaS.com.
Mappings
Warehouse (Parent)
Mapping Type | Source Field (Acumatica) | Destination Field (iPaaS.com) | Description |
Field | Name | Name | Required: Warehouse identifier (max 50 chars). |
Field | Description | Description | Context or details about the warehouse. |
Error Handling
Collection: Location (Parent)
Missing WareHouseName
Description: Validate and reject null Name fields before sync.
Resolution: Ensure every warehouse record in Acumatica has a WarehouseName before syncing.
Testing & Validation
Test Scenarios
Valid Warehouse → Sync succeeds, record created in iPaaS.com.
Missing Name → Sync fails with validation error.
Duplicate Name → Conflict detected, error logged.
Name > 50 Characters → Truncation or failure depending on rules.
Validation Checklist
Name field populated.
No duplicate names.
Description synced correctly.
Validation Rules
Name must not be null.
Name must be unique.
Name must not exceed 50 characters.
Additional Notes
Multi-branch Acumatica setups may require branch-specific Warehouse handling.
Logs should capture all rejected or failed warehouse syncs for troubleshooting.