Microsoft Dynamics 365 Business Central warehouse and inventory locations can be transferred to iPaaS.com as location records through the integration's polling schedule or through Manual Sync. Each Business Central location is captured as a single iPaaS.com location, with its code recorded as the iPaaS.com location name, its name recorded as the description, and its address and contact details captured into the location's dedicated fields. Transferring locations keeps the warehouse and inventory locations aligned across the subscriber's connected systems.

This family is a single collection — Add/Update Dynamics 365 Business Central Location TO iPaaS.com — with no child collections. It supports a bulk initialization run so that an existing set of Business Central locations can be brought into iPaaS.com in one pass when the integration is first configured. The location records this collection captures are also used as a prerequisite by the product and product-inventory transfers, which transfer a location into iPaaS.com on demand if a product or inventory record references a location that does not yet exist there.

When transferring a Business Central location from the iPaaS.com Manual Sync page, enter the location identifier. Either of two values can be used:

After a successful transfer, iPaaS.com saves the Business Central location internal ID as the external ID on a dedicated external-ID record. This external ID links every subsequent transfer of the same location to the same iPaaS.com location rather than creating a duplicate. The location's address and contact detail are read separately and merged onto the same record during the transfer, so the captured location reflects the full Business Central location data.

Outbound delete is not supported for the location record. This collection captures and updates Business Central locations into iPaaS.com; it does not remove iPaaS.com records. Delete mappings are not included in the default templates, and deleting a location in Business Central does not remove the corresponding iPaaS.com location. Subscribers who need to retire an iPaaS.com location should manage that on the iPaaS.com side.

The address and contact detail for a location is captured into a set of dedicated location fields that ship with this integration's template — Dynamics Location AddressLine1, Dynamics Location AddressLine2, Dynamics Location Contact, Dynamics Location City, Dynamics Location State, Dynamics Location PostalCode, Dynamics Location Country, Dynamics Location PhoneNumber, Dynamics Location Email, and Dynamics Location Website. Each of these fields must exist on the iPaaS.com location for its mapping to store a value; a field that does not exist is left unset. These fields are listed in the field mapping table below.

Beyond these template fields, the integration does not provide a general subscriber-defined custom-field mechanism for the location collection. Subscribers or their MiSP should confirm that the listed location fields exist on the iPaaS.com side before relying on the captured address and contact detail, and can contact iPaaS.com Support for assistance.

No mapping filter is applied to this collection, so every Business Central location it processes is captured.

No other collection in this integration writes the same Business Central location into iPaaS.com, so there is no conflicting collection to coordinate with.

This integration does not provide configurable collision-handling methods for the location collection. There is no subscriber-selectable conflict-resolution option (such as Error, Remap and Link, or Update and No Link) on this collection. Locations are instead matched to their iPaaS.com record by the saved external ID and by name — see Duplicate Matching below.

To avoid creating duplicate locations in iPaaS.com, the integration matches an incoming Business Central location to an existing iPaaS.com location before recording a new one. When a location has no saved external ID yet, the integration looks for an existing iPaaS.com location whose name matches the Business Central location code. If a match is found, the integration links the external ID to that existing record so the location is updated rather than duplicated. The name used for matching is the Business Central location code, so keep location codes consistent to ensure the match resolves to the intended record.

This collection does not auto-transfer any related record as a prerequisite of a location transfer; the location is a standalone record. (The location is itself transferred as a prerequisite by the product and product-inventory collections when they reference a location that does not yet exist in iPaaS.com — see those collections' documentation.)

None. This collection captures the location record only; it has no child collections.

For the full installation walkthrough, see the Installation Instructions.

Subscribers or their MiSP can contact iPaaS.com Support for assistance configuring Business Central Web Services or the iPaaS.com location fields.

A bulk initialization run follows the same per-location flow for every existing Business Central location in one pass when the integration is first configured.

iPaaS.com data type: Location

This collection captures the Business Central location as an iPaaS.com location. It has no mapping filter, so every location it processes is captured.

For the complete catalog of error messages this integration can produce, see the Error Messages article. The conditions most relevant to the location transfer are:

Errors and transfer status for every location transfer are recorded in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.