Summary
ID Format
Deleted Record Support
Custom Field Support
Mapping Collection Status
Duplicate or Conflicting Mappings
Supported Child Collections
System Caveats
Setup Requirements
Integration Flow
Mappings
Error Handling
Validation Rules
Testing and Validation
Additional Notes
Related Documents

Summary

The per-location inventory of a Microsoft Dynamics 365 Business Central item can be transferred to iPaaS.com and recorded as inventory on the matching iPaaS.com product. This standalone collection captures inventory on its own schedule, separate from a product transfer: for each Business Central location that holds the item, the integration resolves the parent product and the location to their iPaaS.com records and records the remaining quantity as both the available quantity and the on-hand quantity.

This standalone inventory collection exists so that inventory levels can be kept current in iPaaS.com without re-transferring the full product. It is distinct from the inventory collection that runs as a child of the product transfer; the standalone collection is dispatched as its own entity and has no parent collection. Transfers happen automatically on the integration's polling schedule, and a Manual Sync can be run at any time.

ID Format

Manual Sync ID Format

When transferring a Business Central item's inventory from the iPaaS.com Manual Sync page, enter the location code and the item's internal record ID in this combined format:

location_code|item_id

The location_code is the Business Central location code, and the item_id is the item's internal record ID (a GUID) from Business Central.

Example: MAIN|6fbc9163-0295-ef11-8a6d-6045bdc8dfe6

External ID Format

After a successful transfer, iPaaS.com saves the location code combined with the item's internal record ID as the external ID on a dedicated external-ID record. This external ID links every subsequent transfer of the same item-and-location inventory to the same iPaaS.com inventory record rather than creating a duplicate. Each combination of item and location is tracked as its own inventory record.

Deleted Record Support

Outbound delete is not supported for the product inventory record. This collection captures and updates inventory levels into iPaaS.com; it does not remove iPaaS.com inventory records. Removing an item or a location in Business Central does not delete the corresponding iPaaS.com inventory record. Subscribers who need to retire an iPaaS.com inventory record should manage that on the iPaaS.com side.

Custom Field Support

Custom fields are not supported for the product inventory collection. The collection maps a fixed set of inventory fields — the parent product, the location, the available quantity, and the on-hand quantity — and does not expose a custom-field mechanism.

Mapping Collection Status

Status: Enabled
Trigger Events: Product Inventory Create, Product Inventory Update. This collection uses the product inventory scope set. Transfers happen automatically on the integration's polling schedule — there are no webhooks for this integration, so the integration periodically checks Business Central for new and changed item inventory — and a Manual Sync can be run at any time. Whether a detected inventory record creates a new iPaaS.com inventory record or updates an existing one depends on the external-ID link (the saved location-and-item combination), not on the change type — see ID Format.

Duplicate or Conflicting Mappings

Another collection writes the same kind of inventory record to iPaaS.com:

Add/Update Dynamics 365 Business Central Product Inventory TO iPaaS.com captures the same per-location inventory but runs within the parent product transfer rather than on its own schedule.

Before enabling both collections together, decide which path should own inventory capture so the same inventory record is not written by both the standalone collection and the product-child collection. Both write to the inventory of the matching iPaaS.com product.

Collision Handling

This integration does not provide configurable collision-handling methods for the product inventory collection. There is no subscriber-selectable conflict-resolution option (such as Error, Remap and Link, or Update and No Link) on this collection. Inventory is instead matched to its iPaaS.com record by the combination of the parent product and the location — see Duplicate Matching. Keep each item-and-location combination consistent so repeated transfers update the same inventory record rather than creating a duplicate.

Duplicate Matching

Before recording inventory, the integration resolves the inventory record's parent product and location and then checks whether an inventory record for that product-and-location combination already exists in iPaaS.com. When a match is found, the existing iPaaS.com inventory record is linked by its external ID so the transfer updates it rather than creating a duplicate. This matching is performed automatically and is not configurable.

Supported Child Collections

This collection has no child collections and no parent collection. It captures inventory records only and is dispatched as a standalone entity.

System Caveats

Microsoft Dynamics 365 Business Central Caveats

Location code required: inventory is tracked by location. Inventory is captured only for Business Central locations that have a location code; remaining quantities at locations without a location code are skipped.
Quantity source: the available quantity and the on-hand quantity on the iPaaS.com inventory record are both set from the same Business Central remaining-quantity value at the location.

iPaaS.com Caveats

Product must exist or be captured first: the parent product must exist in iPaaS.com before its inventory can be recorded. When the product is not yet present in iPaaS.com, the integration captures the product into iPaaS.com first, then attaches the inventory.
Location must exist or be captured first: the Business Central location is resolved to its matching iPaaS.com location through a dedicated external-ID link. When a linked location is not found, the integration captures the location into iPaaS.com first, then records the inventory against it.
Inventory record routing: each item-and-location combination is saved as its own external ID, which routes all subsequent transfers for that inventory record.

Setup Requirements

Microsoft Dynamics 365 Business Central Configuration

Enable Web Services for Items By Location so the integration can read per-location inventory. The supporting product data is read through the Items, Item Card, Item Categories, and Customer Price Groups Web Services.
Configure each inventory location with a location code; inventory at locations without a code is not transferred.
Authentication uses OAuth 2.0; ensure credentials are stored securely in the iPaaS.com credential manager.

For the full installation walkthrough, see the Installation Instructions.

iPaaS.com Configuration

Ensure the parent product and its location exist in iPaaS.com, or are available for the integration to capture, before inventory is transferred. The integration will capture a missing product or location first, then attach the inventory.

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

Integration Flow

An item's inventory is created or changed at a Business Central location.
The integration detects the inventory on its polling schedule, or a subscriber triggers a Manual Sync using the location_code|item_id format.
iPaaS.com authenticates with Business Central using OAuth 2.0 and reads the item's per-location inventory.
The integration resolves the Business Central location code to its iPaaS.com location. When the location is not yet linked in iPaaS.com, it is captured into iPaaS.com first.
The integration resolves the Business Central item to its matching iPaaS.com product. When the product is not yet present in iPaaS.com, it is captured into iPaaS.com first.
The integration checks whether an inventory record already exists in iPaaS.com for that product-and-location combination, and links to it when found.
The remaining quantity at the location is recorded as both the available quantity and the on-hand quantity on the iPaaS.com inventory record.
The iPaaS.com inventory record is created on the first transfer or updated on subsequent transfers, matched by the saved external ID (the location-and-item combination).
Transfer status and any errors are recorded in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.

Mappings

Add/Update Dynamics 365 Business Central Product Inventory Standalone TO iPaaS.com

iPaaS.com data type: Product Inventory

This standalone collection has no mapping filter, so the inventory of every qualifying Business Central location is processed. Inventory at a location with no location code is not transferred. The collection captures four inventory fields and has no child or parent collections.

Mapping Type	Source Field (Microsoft Dynamics 365 Business Central)	Destination Field (iPaaS.com)	Description
Dynamic Formula	`return await GetSpaceportIdAsync(Id.Split("\\|")[1], "Product", SpaceportSystemId);`	ParentId	Required. Resolves the Business Central item to its matching iPaaS.com product so the inventory attaches to the correct product. The parent product must exist in iPaaS.com; when it is not yet present, the integration captures the product into iPaaS.com first. The value is resolved automatically by the platform.
Dynamic Formula	(location resolution — see formula below)	LocationId	Required. Resolves the Business Central location code to its Business Central location and then to the matching iPaaS.com location so the inventory is recorded against the correct location. The Business Central location must be linked to an iPaaS.com location; when no link exists yet, the integration captures the location into iPaaS.com first. Inventory at a location with no location code is not transferred.
Field	`RemainingQuantity`	QtyAvailable	Required. Sets the iPaaS.com available quantity from the Business Central remaining quantity at the location.
Field	`RemainingQuantity`	QtyOnHand	Required. Sets the iPaaS.com on-hand quantity from the Business Central remaining quantity at the location. The same Business Central remaining-quantity value is recorded as both the available quantity and the on-hand quantity.

The LocationId formula:

var externalId = await ConvertLocationCodeToLocationId(LocationCode);
if(!string.IsNullOrEmpty(externalId))
return await ConvertLocationIdToiPaaSId(externalId);

Error Handling

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

Parent product cannot be resolved or captured: the inventory record must attach to a matching iPaaS.com product. The integration attempts to capture the product into iPaaS.com first when it is not yet present; if that product capture fails, the inventory transfer stops. Resolution: confirm the Business Central item is valid and transferable, then re-transfer the inventory.
Location cannot be resolved or captured: the Business Central location code must resolve to a matching iPaaS.com location. The integration attempts to capture the location into iPaaS.com first when no link exists; if that location capture fails, the inventory transfer stops. Resolution: confirm the location has a valid location code and is transferable, then re-transfer the inventory.
Invalid Manual Sync ID format: the Manual Sync identifier must be in the location_code|item_id format. Resolution: confirm the location code and item internal record ID are combined in the correct format.

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

Validation Rules

Location code required: inventory is captured only for Business Central locations that have a location code; remaining quantities at locations without a code are skipped.
Parent product resolution: the inventory record must resolve to a matching iPaaS.com product, which is captured first when not yet present.
Location resolution: the inventory record must resolve to a matching iPaaS.com location, which is captured first when not yet linked.
Duplicate matching: existing iPaaS.com inventory is matched by the combination of the parent product and the location, so a repeat transfer updates the same record.

Testing and Validation

Test Scenarios

Valid inventory transfer. Transfer the inventory of a Business Central item at a location with a valid location code, where the product and location already exist in iPaaS.com. Confirm the iPaaS.com inventory record is created with the available quantity and on-hand quantity both set from the remaining quantity.
Product captured first. Transfer inventory for an item whose product is not yet present in iPaaS.com. Confirm the integration captures the product into iPaaS.com first and then attaches the inventory.
Location captured first. Transfer inventory at a location that is not yet linked in iPaaS.com. Confirm the integration captures the location into iPaaS.com first and then records the inventory against it.
Multiple locations. Transfer inventory for an item that is stocked at more than one location. Confirm a separate iPaaS.com inventory record is recorded per location.
ID format. From the Manual Sync page, transfer a specific inventory record using the location_code|item_id format and confirm the correct item-and-location inventory is captured.
Repeat transfer / external ID. Transfer the same item-and-location inventory twice. Confirm the second transfer updates the existing iPaaS.com inventory record (matched by the product-and-location combination) rather than creating a duplicate.

Validation Checklist

Every inventory location in Business Central is configured with a location code.
Web Services are enabled in Business Central for Items By Location and the supporting product data.
The parent product and its location exist in iPaaS.com, or are available for the integration to capture, before inventory is transferred.

Additional Notes

The available quantity and the on-hand quantity are both set from the same Business Central remaining-quantity value at the time this documentation was written.
This standalone collection and the inventory collection that runs within the product transfer can both write inventory to the same iPaaS.com product; decide which path owns inventory capture before enabling both.
Outbound delete is not supported; removing an item or location in Business Central does not remove the corresponding iPaaS.com inventory record.