Contents
Summary
Microsoft Dynamics 365 Business Central customers can be captured into iPaaS.com so that customer detail is available to the subscriber's connected systems. A Business Central contact record that is classified as a customer is recorded in iPaaS.com as a Customer, populated with the customer number, email address, and first name, and its address is captured on the same record by a child collection within the same transfer.
Because Business Central holds both customers and companies in the same contact source, this family captures only the records that are classified as customers — records whose type is Person and whose record type is Customer. Person records classified as contacts and company records are skipped here and handled by the Add/Update Dynamics 365 Business Central Contact TO iPaaS.com and Add/Update Dynamics 365 Business Central Company TO iPaaS.com collections respectively. To keep a single iPaaS.com customer per Business Central customer, the integration matches an incoming customer to an existing iPaaS.com customer by email address before recording a new one.
ID Format
Manual Sync ID Format
When transferring a Business Central customer from the iPaaS.com Manual Sync page, enter the customer's identifier. The integration accepts either the customer's internal record ID or the Business Central customer number, and resolves the customer record from the value entered.
Example (internal record ID): 3f2504e0-4f89-11d3-9a0c-0305e82c3301
Example (customer number): 44552
External ID Format
After a successful transfer, iPaaS.com saves the Business Central customer number as the external ID on a dedicated external-ID record. This external ID links every subsequent transfer of the same customer to the same iPaaS.com customer rather than creating a duplicate. Keep the customer number unique so repeated transfers update the existing customer.
The customer's address is linked under its own external ID, formed from the customer number followed by an address marker — for example, 44552|CustomerAddress, where 44552 is the customer number. This links the captured address to the same customer on later transfers.
Deleted Record Support
Outbound delete is not supported for the customer record or for its address child record. This family captures and updates customers into iPaaS.com; it does not remove iPaaS.com records. Delete mappings are not included in the default templates, and deleting a customer or its address in Business Central does not remove the corresponding iPaaS.com customer or address. Subscribers or their MiSP who need to retire an iPaaS.com customer should manage that on the iPaaS.com side.
Custom Field Support
Custom fields are supported on the parent customer record. To capture a Business Central customer value that is not already in the standard mapping list:
In Business Central, customize the Customers or Customer Card Web Service so the value is exposed in the customer response. Subscribers or their MiSP can contact iPaaS.com Support for assistance customizing Business Central Web Services.
In iPaaS.com, create a custom field on the subscription that matches the field name and data type.
Map the new iPaaS.com custom field to the Business Central value on the parent customer collection.
A custom field must exist on the iPaaS.com subscription before its mapping can store a value; an unmatched custom field is left unset. The customer address child collection does not support custom fields.
Mapping Collection Status
Status: Enabled
Trigger Events: Customer Create, Customer Update, Customer Poll. These collections use the customer 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 customers — and a Manual Sync can be run at any time. Whether a detected customer creates a new iPaaS.com customer or updates an existing one depends on the external-ID link (the saved customer number) and the email match, not on the change type — see ID Format and Duplicate or Conflicting Mappings.
A mapping filter restricts which Business Central records the parent collection captures — see the parent Mappings section.
Duplicate or Conflicting Mappings
Other collections operate on the same customer or the same Business Central person source:
Add Dynamics 365 Business Central Customer FROM iPaaS.com and Update Dynamics 365 Business Central Customer FROM iPaaS.com write customers in the opposite direction (from iPaaS.com into Business Central) rather than capturing them.
Add/Update Dynamics 365 Business Central Contact TO iPaaS.com captures the same Business Central person source, filtered to records classified as contacts rather than customers.
Add/Update Dynamics 365 Business Central Company TO iPaaS.com captures Business Central records classified as companies from the same source.
Before enabling these collections together, review their filters and Add/Update settings and decide which system is the source of truth for customer data, so the same record is not written in conflicting directions.
Collision Handling
This integration does not provide configurable collision-handling methods for the customer collections. There is no subscriber-selectable conflict-resolution option (such as Error, Remap and Link, or Update and No Link) on these collections. Customers are instead matched to their iPaaS.com record by the saved external ID (the customer number) and by email address — see Duplicate Matching below.
Duplicate Matching
To avoid creating duplicate customers in iPaaS.com, the integration checks for an existing iPaaS.com customer before recording a new one. It first looks for the customer by the saved external ID (the customer number). When no external-ID link exists yet, it searches for an existing iPaaS.com customer by email address; if one is found, the integration links the Business Central customer to that existing iPaaS.com customer by creating the external-ID record, rather than adding a second customer. For this match to work, the customer's email address must be present and unique in iPaaS.com.
The customer address child collection links each captured address to the customer's existing address instead of adding a second copy when the same address is transferred again.
Supported Child Collections
The parent Add/Update Dynamics 365 Business Central Customer TO iPaaS.com collection captures the customer record. One child collection captures the rest of the customer within the same dispatch:
Child Collection | Purpose |
Add/Update Dynamics 365 Business Central Customer Address TO iPaaS.com | Captures the customer's address from the parent customer record. |
The child collection captures its record as part of the parent customer's transfer; it is not synced on its own.
System Caveats
Microsoft Dynamics 365 Business Central Caveats
Source classification: only Business Central person records classified as customers are captured here. A record's type (Person) and record-type classification (Customer) in Business Central determine whether it flows through this collection, the contact collection, or the company collection. Person records classified as contacts and company records are skipped.
Address is read from the customer record: the address values are read from the parent Business Central customer record and reflect the customer's address as held in Business Central. The child collection captures a single customer address per customer transfer.
iPaaS.com Caveats
Customer number is the routing key: the customer number must be present on the Business Central record for the transfer to link correctly. It is saved as the external ID that routes all subsequent transfers for that customer.
Email matching: before recording a new customer, iPaaS.com checks for an existing customer by email address to avoid duplicates, and links to that customer when a match is found.
Email uniqueness: customer email addresses must be unique in iPaaS.com; duplicate email addresses can cause sync failures or an inability to link the customer to its existing record.
Address recorded on the matched customer: the address is recorded on the iPaaS.com customer that the parent collection matched or created; it is not stored as an independent record.
Custom fields must exist first: a mapped custom field stores a value only when a custom field of the same name exists on the iPaaS.com subscription; otherwise the value is not stored.
Setup Requirements
Microsoft Dynamics 365 Business Central Configuration
Enable Web Services for Customers, Customer Card, Contact Card, and Customer Price Group so the integration can read customer records.
Ensure customer records carry valid name and email data; only records of type Person with record type Customer are captured through this collection.
If custom fields are mapped, customize the relevant Web Service to expose 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
Ensure customer email addresses are unique in iPaaS.com so duplicate matching and linking work correctly.
Create custom fields on the iPaaS.com subscription that match the Business Central field names and data types for any custom-field mappings in use.
Subscribers or their MiSP can contact iPaaS.com Support for assistance configuring Business Central Web Services.
Integration Flow
A customer is created or updated in Business Central as a record of type Person with record type Customer.
The integration detects the customer on its polling schedule, or a subscriber triggers a Manual Sync using the customer's internal record ID or customer number.
The parent mapping filter confirms the record is a customer (type Person and record type Customer); contact and company records are skipped.
iPaaS.com authenticates with Business Central using OAuth 2.0 and reads the customer.
iPaaS.com checks for an existing customer by the saved external ID (the customer number); if none exists, it checks by email address and links to a matching customer rather than creating a duplicate.
The parent collection records the customer: customer number, first name, email address, and any mapped custom fields.
The address child collection records the customer's address from the parent customer record, with duplicate prevention so an address is not added twice.
The iPaaS.com customer is created on the first transfer or updated on subsequent transfers, matched by the saved external ID (the customer number) or by email.
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 Customer TO iPaaS.com (Parent)
iPaaS.com data type: Customer
Mapping Filter
Type == "Person" && RecordType == "Customer"
Filter Description. Only Business Central records whose Type is Person and whose RecordType is Customer pass this filter and are captured as iPaaS.com customers. Person records classified as contacts, and company records, are skipped here and handled by the contact and company collections instead.
This collection captures the customer record and is the parent of the address child collection below. It supports custom fields.
Mapping Type | Source Field (Microsoft Dynamics 365 Business Central) | Destination Field (iPaaS.com) | Description |
Field |
| CustomerNumber | Required. The iPaaS.com customer number, taken from the Business Central customer number. It is saved as the external ID and is the key used to match the customer to its iPaaS.com record on every transfer. Keep the customer number unique. |
Field |
| FirstName | Required. Provides the customer's name on the iPaaS.com record, taken from the Business Central customer name. |
Field |
| EmailAddress | Required. The customer's email address. It must be present and unique, and it supports duplicate matching against existing iPaaS.com customers — see Duplicate Matching. |
To capture an additional Business Central customer value, add a custom field on the iPaaS.com subscription and map it to the Business Central value on this collection — see Custom Field Support.
Add/Update Dynamics 365 Business Central Customer Address TO iPaaS.com (Child)
iPaaS.com data type: Customer Address
This collection is a child of the customer parent. It captures the customer's address from the parent customer record and records it on the matching iPaaS.com customer. It does not transfer on its own; the address is captured as part of the parent customer transfer.
Mapping Filter
if(Parent != null && !string.IsNullOrEmpty(Parent.Address) && SourceTypeName == "ParentOnly")
return true;
return false;Filter Description. The address is captured only when the parent customer record exists, has a non-empty street address, and the source type is ParentOnly. A customer with no street address does not produce an address record, and the collection runs only as part of the parent customer transfer.
Mapping Type | Source Field (Microsoft Dynamics 365 Business Central) | Destination Field (iPaaS.com) | Description |
Static |
| PreventDuplicate | Required (designed constant). Prevents a duplicate address from being added to the iPaaS.com customer. When the same address is transferred again, the existing iPaaS.com address is reused instead of adding a second copy. This value should remain set to true. |
Dynamic Formula |
| Address1 | Recommended. The address line, taken from the parent Business Central customer's address. Left unset when the parent customer has no address line. |
Dynamic Formula |
| City | Recommended. The city, taken from the parent Business Central customer. Left unset when the parent customer has no city. |
Dynamic Formula |
| Region | Recommended. The region, taken from the parent Business Central customer's county. Left unset when the parent customer has no county. |
Dynamic Formula |
| Country | Recommended. The country, taken from the parent Business Central customer's country/region code. Where downstream systems expect a full country name rather than a code, confirm the value meets their needs. Left unset when there is no country/region code. |
Dynamic Formula |
| PostalCode | Recommended. The postal code, taken from the parent Business Central customer's post code. Left unset when the parent customer has no post code. |
Dynamic Formula |
| PhoneNumber | Recommended. The phone number, taken from the parent Business Central customer. Left unset when the parent customer has no phone number. |
The mappings read from the parent customer, so additional address collections can be built the same way to represent different customer addresses for a subscriber's use case.
Error Handling
For the complete catalog of error messages this integration can produce, see the Error Messages article. The conditions most relevant to the customer transfer are:
Missing email: The customer's email address is empty or absent. The email is required for duplicate matching and for a complete iPaaS.com customer record. Resolution: ensure the customer's email is present in Business Central before transferring.
Duplicate or non-unique email: Customer email addresses must be unique in iPaaS.com. A duplicate email can cause a sync failure or prevent the integration from linking the customer to its existing record. Resolution: ensure each customer has a unique email address. If the email cannot be linked to an existing iPaaS.com customer, the transfer reports that it was unable to link to the existing customer by email and that this may result in duplicate customer records.
Missing or duplicate customer number: The customer number is saved as the external ID and is the key that links each transfer to its iPaaS.com record. A customer with no number cannot be linked, and a non-unique customer number can cause a transfer to update an unintended record. Resolution: ensure each Business Central customer carries a unique customer number before transferring.
Errors and transfer status for every customer transfer are recorded in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.
Validation Rules
Customer qualification: only records of type Person with record type Customer are processed; contacts and companies are skipped by the parent filter.
Email presence and uniqueness: the customer email must be present and unique in iPaaS.com for duplicate matching and linking to work.
Customer number uniqueness: the customer number must be present and unique; it is saved as the external ID that links every transfer to the same iPaaS.com customer.
Address condition: an address record is captured only when the parent customer has a street address and the source type is
ParentOnly.
Testing and Validation
Test Scenarios
Valid customer transfer. Transfer a Business Central customer of type Person and record type Customer with a name, email, and address (by polling or Manual Sync). Confirm the iPaaS.com customer is created with the correct customer number, first name, email, and address.
Customer qualification. Transfer a Business Central person record classified as a contact and a record classified as a company. Confirm neither is captured by this collection.
Email duplicate matching. Transfer a Business Central customer whose email matches an existing iPaaS.com customer that has no external-ID link yet. Confirm the integration links to the existing customer rather than creating a duplicate.
Missing email (failure case). Transfer a customer with no email address. Confirm the transfer reports the missing email and the issue is logged.
ID format. From the Manual Sync page, transfer a specific customer using its internal record ID and again using its customer number, and confirm the correct customer is captured in each case.
Customer with address. Transfer a customer that has a street address. Confirm the address is captured on the same iPaaS.com customer within a single dispatch, and that transferring the same customer again reuses the existing address rather than adding a duplicate.
Repeat transfer / external ID. Transfer the same customer twice. Confirm the second transfer updates the existing iPaaS.com customer (matched by customer number) rather than creating a duplicate.
Validation Checklist
The Business Central customer is of type Person with record type Customer.
The customer carries a unique, non-empty customer number.
The customer's email is present, valid, and unique.
All required Web Services are enabled in Business Central.
Custom fields exist on the iPaaS.com subscription for every custom-field mapping in use, matching the Business Central field names and types.
Additional Notes
This family captures the customer number, name, and email in this direction, along with the customer's address through the child collection; additional customer detail can be captured by adding custom fields.
Email matching links a Business Central customer to an existing iPaaS.com customer found by email, so keeping email addresses unique is important to avoid both duplicate records and link failures.
Outbound delete is not supported for the customer record or its address; deletions in Business Central do not propagate to iPaaS.com.
Related Documents
Connections and Settings (pending publication)
Known Limitations (pending publication)