Contents
Summary
Open sales orders can be sent from iPaaS.com to Microsoft Dynamics 365 Business Central, where each qualifying order is created or updated as a sales order in the target Business Central company. The parent collection writes the order header — the order number, order date, the customer the order sells to, the shipping agent and service code drawn from that customer, the discount, the order status, and the full bill-to and ship-to addresses. A companion child collection writes each qualifying order line. The order header is written first, then each line is added to that order in the same transfer.
This family processes open orders only — transactions still in a Pending status that are not invoices and that are associated with either a customer or a company. Posted invoices are handled by a separate collection and are deliberately excluded here, so a single transaction is never processed both as an open order and as a posted invoice. Whether an incoming order is created or updated in Business Central is decided by whether the order is already linked to a Business Central sales order, not by which event fired.
ID Format
Manual Sync ID Format
When transferring an order from the iPaaS.com Manual Sync page, enter the iPaaS.com transaction record ID of the order to transfer.
Example: 17542
This ID uniquely represents the order's transaction within iPaaS.com and ensures the correct order is transferred to Business Central.
External ID Format
After a successful transfer, iPaaS.com saves the Business Central sales order number as the external ID on a dedicated external-ID record. This external ID routes every later update to the same Business Central order rather than creating a duplicate. The order is identified in Business Central by its sales order number — the No. field on the sales order. An example value from Business Central is SO1001. As a fallback, when no external-ID record exists yet and the incoming order's number matches an existing Business Central sales order number, the records are linked automatically instead of creating a duplicate.
Deleted Record Support
Delete is not supported in this direction. These collections create and update sales orders and their lines in Business Central; they do not delete them. Delete mappings are not included in the default templates, and deleting an order in iPaaS.com does not remove the corresponding Business Central sales order. Subscribers who need to retire a Business Central sales order should manage that directly in Business Central.
Custom Field Support
Both the parent sales order collection and the child line collection support custom fields. To set a Business Central sales order or order-line field that is not already in the standard mapping list:
In Business Central, customize the relevant Web Service so it accepts the field on the sales order or sales order line request. Subscribers or their MiSP can contact iPaaS.com Support for assistance customizing Business Central Web Services.
In iPaaS.com, create a custom field whose name matches the Business Central field name you want to populate.
Map the new custom field to a static or dynamic value in the appropriate collection.
Each custom field's name and value is included in the order or line sent to Business Central as-is. The name must be a valid sales order or order-line field in your Business Central environment, or Business Central rejects the request.
Mapping Collection Status
Status: Enabled (both collections)
Trigger Events: Transaction Create, Transaction Update. These collections dispatch automatically once subscribers or their MiSP subscribe to the iPaaS.com transaction outbound triggers. Enable them in the subscription configuration's Outbound Data Flows section by subscribing to the transaction create and update events. There are no webhooks for this integration, so the transfer is driven by the iPaaS.com create and update events rather than by polling. Until those subscriptions are enabled, no automatic transfers occur, and a Manual Sync can be run at any time. Whether an incoming order is created or updated in Business Central is decided by whether the order is already linked to a Business Central sales order, not by which event fired.
A mapping filter on each collection restricts which transactions and which lines are processed — see the Mappings section for the filter on each collection.
Duplicate or Conflicting Mappings
Other collections also operate on the Business Central sales order:
Add/Update Dynamics 365 Business Central Sales Order TO iPaaS.com and its child collections write in the opposite direction, capturing sales orders from Business Central into iPaaS.com rather than creating them in Business Central.
The posted-invoice collection that writes from iPaaS.com into Business Central handles completed transactions and is mutually exclusive with this open-order family by status: this family processes only Pending transactions that are not invoices, while the posted-invoice collection processes Complete transactions. A single transaction is therefore never written by both.
Before enabling these collections together, review their filters and Add/Update settings and decide which system is the source of truth for order data, so the same order is not written in conflicting directions.
Collision Handling
This integration does not provide configurable collision-handling methods for the sales order collections. There is no subscriber-selectable conflict-resolution option on these collections. Orders are instead matched to their Business Central record by the saved external ID (the sales order number) — see Duplicate Matching.
Duplicate Matching
Before an order is created or updated, the integration checks whether the iPaaS.com order is already linked to a Business Central sales order. When it is not yet linked, the integration looks up Business Central for an order with the same number and, if a match is found, links the iPaaS.com order to that existing Business Central order instead of creating a duplicate. The same approach applies to the order's lines: each iPaaS.com order line is linked to a matching existing Business Central order line where one exists, rather than adding a duplicate line. Matching is performed on the order number and line detail, so keep the order number aligned with the intended Business Central sales order.
Supported Child Collections
The parent Add/Update Dynamics 365 Business Central Sales Order FROM iPaaS.com collection writes the order header. One child collection writes the rest of the order within the same transfer:
Child Collection | Purpose |
Update Dynamics 365 Business Central Sales Order Line FROM iPaaS.com | Writes each qualifying order line — the item number, quantity, quantity to ship, and description — onto the Business Central sales order created or updated by the parent. |
The child collection does not transfer on its own. It runs whenever the parent order is transferred, after the order header is written.
System Caveats
Microsoft Dynamics 365 Business Central Caveats
Customer must resolve in Business Central: the order's customer number is resolved from the iPaaS.com customer, falling back to the company. If neither resolves to a Business Central customer, the order cannot be written. The customer or company is transferred from iPaaS.com automatically when it is not yet in Business Central — see Prerequisite handling in the Integration Flow.
Customer Posting Group: the resolved Business Central customer must have a valid Customer Posting Group assigned in Business Central, or Business Central rejects the order.
Country/region codes: any country or region value on the bill-to or ship-to address must match an existing country/region code in your Business Central company, or Business Central rejects the order.
Line item SKUs must exist as items: each order line's SKU must exist as an item in Business Central. The integration transfers a missing product from iPaaS.com first where possible; if a product cannot be created, the order is not written.
Document type and line type are fixed: the order line is written with a fixed document type and item line type so Business Central writes it to a sales order as an item line. These are designed constants, not example values to replace.
Order date format: Business Central stores the order date as text; the integration converts the iPaaS.com transaction created date to the date format Business Central expects before writing it.
iPaaS.com Caveats
Primary billing and shipping addresses drive the address fields: the bill-to and ship-to address fields populate only when the iPaaS.com order has an address flagged as the primary billing or primary shipping address. Without one, those fields are left unset on the order.
Customer resolution fallback: the customer is resolved first from the order's iPaaS.com customer, then from the company if no customer link exists. If neither resolves, the order cannot be written.
Discount source: the order discount comes from the iPaaS.com order's discount amount.
Custom fields must be valid Business Central fields: a mapped custom field stores a value only when its name is a valid sales order or order-line field in your Business Central environment; otherwise Business Central rejects the request.
Setup Requirements
Microsoft Dynamics 365 Business Central Configuration
Enable Web Services for the sales order entities — Sales Order, Sales Orders, and Sales Order Lines — and for the customer and item entities the order depends on, including Customer, Customer Price Groups, Item, Item Card, Items, Item Categories, and Items By Location, so the integration can read and write orders and resolve their customers and items.
Ensure each customer that orders are written for has a valid Customer Posting Group assigned in Business Central.
Configure country/region codes so they match the country values coming from iPaaS.com.
If custom fields are mapped, customize the relevant Web Service to accept them.
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
Subscribe to the transaction create and update events in the Outbound Data Flows section to enable automatic transfers.
Ensure each order carries a customer or company, a unique transaction number, and a primary billing and primary shipping address for the address fields to populate.
Maintain the order status translation list so each iPaaS.com order status maps to the intended Business Central status before orders are written.
Configure the excluded-SKU preset if specific SKUs should be skipped entirely.
Create custom fields whose names match the Business Central field names for any custom-field mappings in use.
Subscribers or their MiSP can contact iPaaS.com Support for assistance configuring Business Central Web Services.
Business Central enforces sales order field requirements through your company configuration and does not publish them in a public API specification; validate them in a staging environment before relying on them in production.
Integration Flow
An order is created or updated in iPaaS.com.
Once the transaction outbound triggers are enabled, the create or update event dispatches the order to Business Central; alternatively, a subscriber triggers a Manual Sync using the iPaaS.com transaction record ID.
The parent mapping filter confirms the transaction is in a Pending status, is not an invoice, and is associated with either a customer or a company. Transactions that do not qualify are excluded.
iPaaS.com authenticates with Business Central.
Prerequisite handling
The integration checks whether the order is already linked to a Business Central sales order. When it is not yet linked, it looks up Business Central for an order with the same number and links to it if a match is found, instead of creating a duplicate.
The order's customer is resolved from the iPaaS.com customer, falling back to the company. If the customer or company is not yet linked to a Business Central customer, the integration transfers it from iPaaS.com into Business Central first; if that transfer fails, the order is not written.
For each order line, the integration links the line to a matching existing Business Central order line where one exists, and if the line's product does not yet exist in Business Central it transfers the product from iPaaS.com first. If a required product cannot be created, the order is not written. Any line whose SKU is listed in the order's excluded-SKU preset is skipped entirely before the lines are processed.
Writing the order
The parent collection writes the order header: the sales order number, order date, the resolved customer number, the shipping agent and service code drawn from that customer, the discount, the translated order status, and the bill-to and ship-to names and addresses.
The child line collection adds each qualifying line to the order — item number, quantity, quantity to ship, and description — with the fixed document type and item line type Business Central requires.
The sales order is created on the first transfer or updated on subsequent transfers, matched by the saved external ID (the sales order number). If a line cannot be written while creating a new order, the order that was just created is removed again so a partial order is not left in Business Central, and the transfer is reported as failed. When the order already exists but cannot be found for an update, the update is reported as failed.
The Business Central sales order number is saved as the external ID in iPaaS.com so later updates route to the same order.
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 Sales Order FROM iPaaS.com (Parent)
iPaaS.com data type: Transaction
Mapping Filter
Status == "Pending" && Type != "Invoice" && (CustomerId != null || CompanyId != null)
Filter Description. A transaction is processed by this collection only when its status is Pending, its type is not an invoice, and it is associated with either a customer or a company. Transactions in any other status, invoices, and transactions with no customer or company are excluded. The exclusion of invoices keeps this open-order collection separate from the collection that handles posted invoices, so the same transaction is not processed by both.
This collection writes the order header and is the parent of the line collection below.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Microsoft Dynamics 365 Business Central) | Description |
Field |
| No | Required. Sets the Business Central sales order number from the iPaaS.com transaction number. It is the key the integration uses to match, link, and later update the order: when no link exists yet, the integration looks up a Business Central order with this number and links to it instead of creating a duplicate. Keep the order number unique. |
Dynamic Formula | (customer resolution — see formula below) | SellToCustomerNo | Required. Resolves the Business Central customer the order sells to. The formula first looks for the Business Central link on the order's iPaaS.com customer; if there is none, it falls back to the order's company; then it uses that link to read the matching customer number from Business Central. If neither the customer nor the company resolves to a Business Central customer, the order cannot be written. The customer or company is transferred from iPaaS.com automatically when it is not yet in Business Central. |
Dynamic Formula | (order date — see formula below) | OrderDate | Recommended. Sets the Business Central order date from the iPaaS.com transaction's created date. Business Central stores the order date as text, so the integration converts the date to the format Business Central expects before writing it. |
Field |
| PaymentDiscountPercent | Optional. Sets the Business Central payment discount on the order from the iPaaS.com order's discount value. Confirm the discount value produced by your iPaaS.com orders is appropriate for this Business Central field, and validate the result in a staging environment before relying on it in production. |
Lookup Translation | (translation list: Dynamics Order Sales Status From iPaaS) | Status | Recommended. Sets the Business Central sales order status from the iPaaS.com order's status by looking the value up in a translation list. The list pairs each iPaaS.com status value with the Business Central status that should be written; when an incoming status has no matching entry, no translated status is set. The translation list entries are environment-specific — confirm the list pairs each of your iPaaS.com order statuses with the correct Business Central status, and add any status your orders use that is not yet listed. |
Dynamic Formula | (shipping agent code — see formula below) | Shipping_Agent_Code | Recommended. Sets the order's shipping agent from the resolved Business Central customer. The formula resolves the Business Central customer from the order's iPaaS.com customer, falling back to the company, then reads that customer's shipping agent code from Business Central. Left unset if no customer resolves or the customer has no shipping agent code. |
Dynamic Formula | (shipping agent service code — see formula below) | Shipping_Agent_Service_Code | Recommended. Sets the order's shipping agent service option (such as standard or express) from the resolved Business Central customer. The formula resolves the Business Central customer from the order's iPaaS.com customer, falling back to the company, then reads that customer's shipping agent service code from Business Central. Left unset if no customer resolves or the customer has no shipping agent service code. |
Static |
| BillToOptions | Required (designed constant). Sets the order's billing address mode so the individual bill-to address fields mapped below are used. To use the customer's own default billing address instead, change this to the default (sell-to) mode and leave the bill-to address fields unmapped so the customer's default address is applied automatically. |
Dynamic Formula | (bill-to name — see formula below) | BillToName | Recommended. Sets the order's billing name from the resolved Business Central customer. The formula resolves the Business Central customer from the order's iPaaS.com customer, falling back to the company, then reads that customer's name from Business Central. An alternative shown in the formula's commented lines builds the billing name from the first and last name on the order's primary billing address instead; if you use that alternative, the name must already exist as a customer in Business Central. |
Dynamic Formula |
| BillToAddress | Recommended. Sets the billing address line from the order's primary billing address in iPaaS.com — the first address flagged as primary billing. Left unset if the order has no primary billing address. |
Dynamic Formula |
| BillToAddress2 | Recommended. Sets the second billing address line from the order's primary billing address in iPaaS.com. Left unset if the order has no primary billing address. |
Dynamic Formula |
| BillToCity | Recommended. Sets the billing city from the order's primary billing address in iPaaS.com. Left unset if the order has no primary billing address. |
Dynamic Formula |
| BillToCounty | Recommended. Sets the billing county or state from the region on the order's primary billing address in iPaaS.com. Left unset if the order has no primary billing address. |
Dynamic Formula |
| BillToPostCode | Recommended. Sets the billing post code from the postal code on the order's primary billing address in iPaaS.com. Left unset if the order has no primary billing address. |
Dynamic Formula |
| BillToCountryRegionCode | Recommended. Sets the billing country/region code from the country on the order's primary billing address in iPaaS.com. The value must match an existing country/region code in your Business Central company, or Business Central rejects the order. Left unset if the order has no primary billing address. |
Static |
| ShippingOptions | Required (designed constant). Sets the order's shipping address mode so the individual ship-to address fields mapped below are used. To use the customer's own default shipping address instead, change this to the default (sell-to) mode and leave the ship-to address fields unmapped so the customer's default address is applied automatically. |
Dynamic Formula | (ship-to name — see formula below) | ShipToName | Recommended. Sets the order's shipping name by combining the first and last name on the order's primary shipping address in iPaaS.com; if only the first name is present, the first name is used on its own. Left unset if the order has no primary shipping address. |
Dynamic Formula |
| ShipToAddress | Recommended. Sets the shipping address line from the order's primary shipping address in iPaaS.com — the first address flagged as primary shipping. Left unset if the order has no primary shipping address. |
Dynamic Formula |
| ShipToAddress2 | Recommended. Sets the second shipping address line from the order's primary shipping address in iPaaS.com. Left unset if the order has no primary shipping address. |
Dynamic Formula |
| ShipToCity | Recommended. Sets the shipping city from the order's primary shipping address in iPaaS.com. Left unset if the order has no primary shipping address. |
Dynamic Formula |
| ShipToCounty | Recommended. Sets the shipping county or state from the region on the order's primary shipping address in iPaaS.com. Left unset if the order has no primary shipping address. |
Dynamic Formula |
| ShipToPostCode | Recommended. Sets the shipping post code from the postal code on the order's primary shipping address in iPaaS.com. Left unset if the order has no primary shipping address. |
Dynamic Formula | (ship-to country/region code — see formula below) | ShipToCountryRegionCode | Recommended. Sets the shipping country/region code from the country on the order's primary shipping address in iPaaS.com. The value must match an existing country/region code in your Business Central company, or Business Central rejects the order. Left unset if the order has no primary shipping address. An alternative shown in the formula's commented lines resolves a country code from a country name or falls back to a fixed code; adjust the formula if your orders need that behavior. |
The SellToCustomerNo formula:
var ExternlCustomerID = await GetExternalIdAsync(CustomerId, "Customer", SpaceportSystemId);
if(ExternlCustomerID == null || ExternlCustomerID == ""){
ExternlCustomerID = await GetExternalIdAsync(CompanyId, "Company", SpaceportSystemId);
}
if (ExternlCustomerID!=null){
return await GetCustomerNoById(ExternlCustomerID);
}The OrderDate formula:
if(TransactionCreatedDateTime != null){
return TransactionCreatedDateTime.ToString()
}The Shipping_Agent_Code formula:
var ExternlCustomerID = await GetExternalIdAsync(CustomerId, "Customer", SpaceportSystemId);
if(ExternlCustomerID == null || ExternlCustomerID == ""){
ExternlCustomerID = await GetExternalIdAsync(CompanyId, "Company", SpaceportSystemId);
}
if (ExternlCustomerID!=null){
return await GetCustomerShippingAgentCodeById(ExternlCustomerID);
}The Shipping_Agent_Service_Code formula:
var ExternlCustomerID = await GetExternalIdAsync(CustomerId, "Customer", SpaceportSystemId);
if(ExternlCustomerID == null || ExternlCustomerID == ""){
ExternlCustomerID = await GetExternalIdAsync(CompanyId, "Company", SpaceportSystemId);
}
if (ExternlCustomerID!=null){
return await GetCustomerShippingAgentServiceCodeById(ExternlCustomerID);
}The BillToName formula:
// var firstName = FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "FirstName");
// var lastName = FieldFromFirstMatch(Addresses, "IsPrimaryBilling == true", "LastName");
// return firstName != null ? firstName + (lastName != null ? " " + lastName : "") : null;
if (CustomerId != null || CompanyId != null)
{
var id = CustomerId ?? CompanyId;
var type = CustomerId != null ? "Customer" : "Company"; var externalId = await GetExternalIdAsync(id, type, SpaceportSystemId);
if (externalId != null)
{
return await GetCustomerNameById(externalId);
}
}The ShipToName formula:
var firstName = FieldFromFirstMatch(Addresses, "IsPrimaryShipping == true", "FirstName"); var lastName = FieldFromFirstMatch(Addresses, "IsPrimaryShipping == true", "LastName"); return firstName != null && lastName != null ? firstName + " " + lastName : firstName;
The ShipToCountryRegionCode formula:
FieldFromFirstMatch(Addresses, "IsPrimaryShipping == true", "Country");
//var CountryCode = await CountryCodeFromName("Germany");
//if(CountryCode!=null){
//return CountryCode;
//}
//return "DK";Update Dynamics 365 Business Central Sales Order Line FROM iPaaS.com (Child)
iPaaS.com data type: Transaction Line
This collection is a child of the sales order parent. It writes each qualifying order line onto the Business Central sales order created or updated by the parent, and supports custom fields.
Mapping Filter
Sku != "Simple Item"
Filter Description. An order line is processed only when its SKU is not Simple Item. Lines whose SKU is Simple Item are excluded. Confirm this exclusion matches your data before relying on it in production; if it does not apply to your items, adjust or remove the filter. Separately, the parent order collection also skips any line whose SKU is listed in the order's excluded-SKU preset, before this collection is evaluated.
Mapping Type | Source Field (iPaaS.com) | Destination Field (Microsoft Dynamics 365 Business Central) | Description |
Static |
| DocumentType | Required (designed constant). Sets the document type for the line so Business Central writes it to a sales order. This must be the order document type, or the line cannot be written. |
Static |
| Type | Required (designed constant). Sets the line type so Business Central treats the line as a product line. This must be the item line type, or the line cannot be written. |
Field |
| No | Required. Sets the Business Central item number on the line from the iPaaS.com line's SKU. The SKU must exist as an item in Business Central; when it does not, the parent order collection transfers the product from iPaaS.com first where possible, and if the product cannot be created the order is not written. |
Field |
| Quantity | Required. Sets the ordered quantity on the line from the iPaaS.com line quantity. |
Field |
| QtyToShip | Recommended. Sets the quantity to ship on the line from the iPaaS.com line's shipped quantity. Left unset if the iPaaS.com line has no shipped quantity. |
Field |
| Description | Recommended. Sets the line description from the iPaaS.com line description. |
Error Handling
For the complete catalog of error messages this integration can produce, see the Error Messages article. The conditions most relevant to the open sales order transfer are:
Customer or company cannot be resolved: The order's customer number is resolved from the iPaaS.com customer, falling back to the company. If neither resolves to a Business Central customer, the order cannot be written. Resolution: ensure the order's customer or company exists in Business Central or can be transferred from iPaaS.com, and that it carries a valid external link to its Business Central customer.
Missing Customer Posting Group: The resolved Business Central customer does not have a valid Customer Posting Group assigned, and Business Central rejects the order. Resolution: assign a valid Customer Posting Group to the customer in Business Central before transferring the order.
Invalid country/region code: A country or region value on the bill-to or ship-to address does not match a valid code in Business Central, and Business Central rejects the order. Resolution: use a country/region code that exists in your Business Central company.
Product cannot be created: An order line's SKU does not exist as an item in Business Central and could not be transferred from iPaaS.com, so the order is not written. Resolution: ensure the product exists in Business Central or can be transferred from iPaaS.com, or exclude the SKU using the excluded-SKU preset.
Line could not be written: If a line cannot be written while a new order is being created, the order just created is removed again so a partial order is not left in Business Central, and the transfer is reported as failed. Resolution: correct the line data and re-transfer the order.
Order not found on update: When the order already exists in Business Central but cannot be found for an update, the update is reported as failed. Resolution: confirm the order still exists in Business Central under the expected order number.
Errors and transfer status for every order transfer are recorded in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.
Validation Rules
Order qualification: only transactions with a Pending status that are not invoices and that carry a customer or company are processed; other transactions are excluded by the parent filter.
Customer resolution: the order's customer must resolve to a Business Central customer through the order's customer or company, or the order is not written.
Customer Posting Group: the resolved Business Central customer must have a valid Customer Posting Group.
Unique order number: the order number is saved as the external ID and routes later updates; keep it unique so repeated transfers update the same order rather than creating a duplicate.
Line qualification: each order line's SKU must exist as a Business Central item (or be transferable from iPaaS.com), and lines whose SKU is Simple Item or is listed in the excluded-SKU preset are not written.
Testing and Validation
Test Scenarios
Valid order creation. Send a qualifying transaction (Pending status, a valid customer, a primary billing and shipping address, and line items) from iPaaS.com. Confirm the sales order is created in Business Central with the correct header, addresses, status, and lines.
Customer resolution. Send an order whose customer is linked to a Business Central customer, and a second order that relies on the company fallback. Confirm both resolve to the correct Business Central customer number.
Customer or company auto-transfer. Send an order whose customer or company is not yet in Business Central. Confirm the customer or company is transferred from iPaaS.com first and the order is then written, and that a failed customer transfer prevents the order from being written.
Missing Customer Posting Group. Send an order for a customer without a valid Customer Posting Group. Confirm the transfer fails and that assigning the posting group, then re-transferring, succeeds.
Status translation. Send orders in different iPaaS.com statuses. Confirm each is written with the Business Central status paired in the translation list, and that a status with no matching entry leaves the Business Central status unset.
Line rollback. Send an order whose line cannot be written (for example, a product that cannot be created). Confirm the order just created is removed so no partial order remains, and the transfer is reported as failed.
Excluded SKUs. Send an order containing line items with SKUs in the excluded-SKU preset, and a line whose SKU is Simple Item. Confirm those lines are skipped and all other lines are written.
Repeat transfer / external ID. Transfer the same order twice. Confirm the second transfer updates the existing Business Central order (matched by order number) rather than creating a duplicate.
Manual Sync. From the Manual Sync page, transfer a specific order using its iPaaS.com transaction record ID and confirm the correct order is written.
Validation Checklist
The transaction is in a Pending status, is not an invoice, and carries a customer or company.
The order's customer or company has a valid link to its Business Central customer, or can be transferred from iPaaS.com.
The resolved Business Central customer has a valid Customer Posting Group.
Country/region codes on the order's addresses are valid in Business Central.
Line item SKUs exist as items in Business Central, or can be transferred from iPaaS.com.
The order status translation list pairs each iPaaS.com order status with the intended Business Central status.
The excluded-SKU preset is configured if specific SKUs need to be skipped.
Custom fields exist on the iPaaS.com subscription for every custom-field mapping in use, matching the Business Central field names.
All required Web Services are enabled in Business Central.
Additional Notes
At the time this documentation was written, both the billing and shipping addresses are written using the custom-address mode and are drawn from the order's primary billing and primary shipping addresses in iPaaS.com. To use the customer's own default address instead, change the billing or shipping mode to the default (sell-to) mode and leave the matching address fields unmapped.
At the time this documentation was written, an order line whose SKU is Simple Item is excluded by the child collection's filter, and any line whose SKU is listed in the order's excluded-SKU preset is skipped by the parent collection before the child collection runs.
The shipping agent code and service code, the bill-to name, and the customer number are all read from the resolved Business Central customer rather than from the order's own data, so they depend on the customer or company resolving correctly in Business Central.
Delete is not supported in this direction; deleting an order in iPaaS.com does not remove the corresponding Business Central sales order.
Related Documents
Connections and Settings (pending publication)
Known Limitations (pending publication)