Contents
Summary
Microsoft Dynamics 365 Business Central customer companies can be transferred to iPaaS.com as companies through the integration's polling schedule or through Manual Sync. Each Business Central company is captured as an iPaaS.com company with its name, email address, phone number, and resolved customer category, and three child collections capture the company's addresses, its person relationships, and its parent-company link within the same transfer. Only Business Central records whose type is Company are processed here; person records — both customers and contacts — are handled by the Add/Update Dynamics 365 Business Central Customer TO iPaaS.com and Add/Update Dynamics 365 Business Central Contact TO iPaaS.com collections instead.
This company family captures both the company record and the structure around it. Company and relationship polling runs on the integration's schedule so that as companies are added or changed in Business Central — and as their parent-company links and person relationships change — those records and links are reliably captured in iPaaS.com rather than being missed between transfers. The parent-company link is recorded so the company hierarchy is preserved in iPaaS.com, and the company's related people are linked to their existing iPaaS.com customer records.
ID Format
Manual Sync ID Format
When transferring a Business Central company from the iPaaS.com Manual Sync page, enter the company identifier in this format:
{{company_no}}The {{company_no}} value is the Business Central company number — the No. field on the company's customer card. The company's internal record ID also resolves the record.
Example:
44552
External ID Format
After a successful transfer, iPaaS.com saves the Business Central company number as the external ID on a dedicated external-ID record. This external ID links every subsequent transfer of the same company to the same iPaaS.com company rather than creating a duplicate. Keep the company number unique so repeated transfers update the existing company.
The child collections save their own external IDs so their records stay linked across transfers: the address external ID is the company number followed by an address marker (for example, 44552|CompanyAddress), and the relationship and hierarchy external IDs combine the related record's ID with the company's ID (for example, C0012|BS013).
Deleted Record Support
Outbound delete is not supported for the company or for any of its child records (addresses, relationships, and the parent-company link). This family captures and updates companies into iPaaS.com; it does not remove iPaaS.com records. Delete mappings are not included in the default templates, and deleting a company or any of its child records in Business Central does not remove the corresponding iPaaS.com company, address, relationship, or parent link. Subscribers who need to retire an iPaaS.com company should manage that on the iPaaS.com side.
Custom Field Support
Custom fields are supported on the parent company collection and on the relationship and hierarchy collections. The parent company collection captures ten company values into custom fields, and the hierarchy collection captures the parent company's Business Central customer number into a custom field; these are listed in each collection's field mapping table below. The address collection does not capture values into custom fields.
To capture a Business Central company value that is not already in the standard mapping list:
In Business Central, customize the relevant Web Service so the value is exposed in the company 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 company (or company relationship) that matches the field name and data type.
Map the new iPaaS.com custom field to the Business Central value in the appropriate mapping collection.
A custom field must exist on the iPaaS.com company before its mapping can store a value; an unmatched custom field is left unset.
Mapping Collection Status
Status: Enabled
Trigger Events: Company Create, Company Update, Company Poll. These collections use the company 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 companies, and for changed company relationships when company-relationship polling is enabled — and a Manual Sync can be run at any time. Whether a detected company creates a new iPaaS.com company or updates an existing one depends on the external-ID link (the saved company number) and on name matching, not on the change type — see ID Format and Duplicate or Conflicting Mappings.
Duplicate or Conflicting Mappings
Other collections operate on Business Central company data and may write the same records:
Add Dynamics 365 Business Central Company FROM iPaaS.com and Update Dynamics 365 Business Central Company FROM iPaaS.com write companies in the opposite direction (from iPaaS.com into Business Central) rather than capturing them.
Add/Update Dynamics 365 Business Central Customer TO iPaaS.com and Add/Update Dynamics 365 Business Central Contact TO iPaaS.com capture Business Central person records. They do not overlap with this collection because the parent filter routes only Company type records here, but a related person captured as a customer by this family is the same record those collections manage.
Before enabling these collections together, review their filters and Add/Update settings and decide which system is the source of truth for company data, so the same company is not written in conflicting directions.
Collision Handling
This integration does not provide configurable collision-handling methods for the company collections. There is no subscriber-selectable conflict-resolution option (such as Error, Remap and Link, or Update and No Link) on these collections. Companies are instead matched to their iPaaS.com company by the saved external ID (the company number) and, for unlinked companies, by company name — see Duplicate Matching below. Keep the company number unique so repeated transfers update the same company rather than creating a duplicate.
Duplicate Matching
To avoid creating duplicate companies in iPaaS.com, when an incoming Business Central company is not already linked to an iPaaS.com company, the integration matches it to an existing iPaaS.com company by name before recording a new one. When a match is found, the Business Central company is linked to that existing iPaaS.com company through its external ID. Companies with the same name can therefore be linked to the same iPaaS.com record, so keep company names distinct where separate companies must remain separate in iPaaS.com.
Supported Child Collections
The parent Add/Update Dynamics 365 Business Central Company TO iPaaS.com collection captures the company record. Three child collections capture the rest of the company within the same dispatch:
Child Collection | Purpose |
Add/Update Dynamics 365 Business Central Company Address TO iPaaS.com | Captures the company's address (line, city, region, country, postal code, phone). |
Add/Update Dynamics 365 Business Central Company Relationship TO iPaaS.com | Captures the company's person relationships, linked to existing iPaaS.com customers. |
Add/Update Dynamics 365 Business Central Company Hierarchy TO iPaaS.com | Captures the company's parent-company link so the company hierarchy is preserved. |
Each child collection captures its records as part of the parent company's transfer; the children are not synced on their own.
System Caveats
Microsoft Dynamics 365 Business Central Caveats
Company qualification: only Business Central records whose type is Company are processed. A record's type in Business Central determines whether it flows through this collection or through the customer and contact collections. Person records are skipped here.
Customer price group for category: the company's customer category is resolved from its Business Central customer price group. For the category to resolve, the customer price group must exist on the company and be linked to a matching iPaaS.com customer category; otherwise no category is set.
Parent customer must be assigned for hierarchy: the parent-company link is captured only when the Business Central company has a parent customer number assigned. A company with no parent customer produces no hierarchy link.
Relationship and hierarchy capture depend on the company: the company's addresses, person relationships, and parent link are captured only when the company itself is transferred; they are not independent records in this direction. Person relationships and the parent link are captured only when the corresponding company-relationship and company-hierarchy options are enabled for the integration.
iPaaS.com Caveats
Company number is the routing key: the company 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 company.
Name matching before create: before recording a new company, iPaaS.com checks for an existing company by name to avoid duplicates. A match links the Business Central company to that existing iPaaS.com company.
Related customers must exist for person relationships: a person relationship is recorded only when the related person already exists as a customer in iPaaS.com, or can be created during the transfer when the company-creation option is enabled — see Setup Requirements and Error Handling.
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 company or company relationship; otherwise the value is not stored.
Integration-Specific Caveats
Reliable company and relationship polling: company and company-relationship polling runs on the integration's schedule so that new and changed companies, and changes to their parent-company and person relationships, are captured in iPaaS.com without being missed between transfers.
Parent and related-record auto-transfer: when the company-creation option is enabled, the company transfer can bring a missing related person into iPaaS.com as a customer and a missing parent company into iPaaS.com as a company before recording the relationship or parent link, so the links resolve in a single dispatch. When that option is not enabled and a required related record is absent, a person relationship is rejected with an error and a missing parent link is not recorded — see Prerequisite Handling and Error Handling.
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 company records, addresses, relationships, and the data used for category resolution.
To capture company relationships, customize the Contacts (Contact Card) Web Service to expose the Company No. field; the integration uses Company No. to link each person to its company, and relationship capture fails if that field is not exposed.
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
Create the custom fields on the iPaaS.com company that match the Business Central field names and data types for any custom-field mappings in use, including B2B Company Status, E_Mail_2, E_Mail_2_Role, E_Mail_2_Fname, E_Mail_2_Contact_lname, Erp_Company_Id, Company Number, FPP_Code, FPP_Amount, and FPP_US_Only on the company, and Parent Customer Number on the company relationship.
Create the iPaaS.com customer categories that the company's customer price groups resolve to, so the category mapping resolves.
Enable the company-relationship option in the subscription configuration to capture person relationships, and the company-hierarchy option to capture the parent-company link.
Ensure related persons exist as customers in iPaaS.com, or enable the company-creation option so the integration can transfer missing related records during the company transfer.
Subscribers or their MiSP can contact iPaaS.com Support for assistance configuring Business Central Web Services and the company options described above.
Integration Flow
A company is created or updated in Business Central, or its parent-company or person relationships change.
The integration detects the company on its polling schedule, or a subscriber triggers a Manual Sync using the
{{company_no}}format. Company-relationship polling, when enabled, also detects changed relationships so the company structure is kept current.The parent mapping filter confirms the record's type is Company; person records are skipped.
iPaaS.com authenticates with Business Central using OAuth 2.0 and reads the company.
For an unlinked company, iPaaS.com matches it to an existing iPaaS.com company by name; a match links the company by external ID, and otherwise a new iPaaS.com company is prepared.
The parent collection records the company: name, email address, phone number, the customer category resolved from the customer price group, and the company detail captured into custom fields.
The address child collection records the company's address.
The relationship child collection records each person relationship, linking it to the related person's existing iPaaS.com customer record. When the company-creation option is enabled and the related person is not yet in iPaaS.com, the person is transferred in as a customer first.
The hierarchy child collection records the parent-company link. When the company-creation option is enabled and the parent company is not yet in iPaaS.com, the parent company is transferred in as a company first so the link resolves.
The iPaaS.com company is created on the first transfer or updated on subsequent transfers, matched by the saved external ID (the company number) or by name.
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 Company TO iPaaS.com (Parent)
iPaaS.com data type: Company
Mapping Filter
Type == "Company"
Filter Description. Only Business Central records whose type is Company pass this filter. Person records — both customers and contacts — are skipped here and are handled by the Add/Update Dynamics 365 Business Central Customer TO iPaaS.com and Add/Update Dynamics 365 Business Central Contact TO iPaaS.com collections instead.
This collection captures the company record and is the parent of the three child collections below.
Mapping Type | Source Field (Microsoft Dynamics 365 Business Central) | Destination Field (iPaaS.com) | Description |
Field |
| Name | Required. The iPaaS.com company name, taken from the Business Central company name. The name is also used to match the incoming company to an existing iPaaS.com company before a new one is created. |
Field |
| EmailAddress | Required. The company's primary email address. |
Field |
| PhoneNumber | Recommended. The company's phone number. Left unset when the company has no phone number. |
Dynamic Formula | (customer price group resolution — see formula below) | Categories | Recommended. Resolves the company's customer price group to an iPaaS.com customer category and records it on the company. When the company has a price group linked to a matching iPaaS.com category, the category is added; when there is no price group or no matching category, no category is set. The matching customer category must already exist in iPaaS.com. The formula references an environment-specific system id ( |
Static |
| B2B Company Status (Custom Field) | Recommended. Marks every captured company with a B2B company status, stored on the iPaaS.com B2B Company Status custom field. The shipped value |
Field |
| E_Mail_2 (Custom Field) | Recommended. A secondary email address, stored on the iPaaS.com E_Mail_2 custom field. Left unset when the company has no secondary email. The custom field must exist on the company. |
Field |
| E_Mail_2_Role (Custom Field) | Recommended. The role for the secondary email contact, stored on the iPaaS.com E_Mail_2_Role custom field. Left unset when the company has no secondary email role. The custom field must exist on the company. |
Dynamic Formula | (secondary contact first name — see formula below) | E_Mail_2_Fname (Custom Field) | Recommended. The first name of the secondary email contact, taken as the first word of the Business Central secondary email contact value, stored on the iPaaS.com E_Mail_2_Fname custom field. Left unset when the company has no secondary email contact value. The custom field must exist on the company. |
Dynamic Formula | (secondary contact last name — see formula below) | E_Mail_2_Contact_lname (Custom Field) | Recommended. The last name of the secondary email contact, taken as the second word of the Business Central secondary email contact value after removing a trailing comma, stored on the iPaaS.com E_Mail_2_Contact_lname custom field. Left unset when the value has only one word or is absent. The custom field must exist on the company. |
Field |
| Erp_Company_Id (Custom Field) | Recommended. The Business Central company's internal record identifier, stored on the iPaaS.com Erp_Company_Id custom field for reference. The custom field must exist on the company. |
Field |
| Company Number (Custom Field) | Recommended. The Business Central company number, stored on the iPaaS.com Company Number custom field for reference. The company number is also saved as the external ID that links subsequent transfers to the same iPaaS.com company. The custom field must exist on the company. |
Dynamic Formula | (FPP code lookup — see formula below) | FPP_Code (Custom Field) | Recommended. The FPP code, taken from the matching value on the Business Central company, stored on the iPaaS.com FPP_Code custom field. Left unset when the company has no FPP code. The custom field must exist on the company. |
Dynamic Formula | (FPP amount lookup — see formula below) | FPP_Amount (Custom Field) | Recommended. The FPP amount, taken from the matching value on the Business Central company, stored on the iPaaS.com FPP_Amount custom field. Left unset when the company has no FPP amount. The custom field must exist on the company. |
Dynamic Formula | (FPP US-only lookup — see formula below) | FPP_US_Only (Custom Field) | Recommended. The FPP US-only indicator, taken from the matching value on the Business Central company, stored on the iPaaS.com FPP_US_Only custom field. Left unset when the company has no FPP US-only value. The custom field must exist on the company. |
The Categories formula:
if (CustomerPriceGroup != null)
{
var spaceportId = GetSpaceportId(CustomerPriceGroup, "Customer Category", 664);
if(spaceportId != null)
{
List<dynamic> dynamicList = new List<dynamic>();
dynamic obj = new System.Dynamic.ExpandoObject();
obj.Id = spaceportId;
dynamicList.Add(obj);
return dynamicList;
}
}
return null;The E_Mail_2_Fname formula:
string nameVal = GetValueFromCustomField(AdditionalProperties, "E_Mail_2_Contact");
if (nameVal != null && nameVal != "") {
string[] name = nameVal.Split(" ");
if (name.Length > 0) {
return name[0];
}
}
return null;The E_Mail_2_Contact_lname formula:
string contact = GetValueFromCustomField(AdditionalProperties, "E_Mail_2_Contact");
if (contact != null && contact != "") { int lastCommaIndex = contact.LastIndexOf(',');
if (lastCommaIndex != -1) {
contact = contact.Remove(lastCommaIndex, 1);
}
string[] name = contact.Split(" ");
if (name.Length > 1) {
return name[1];
}}
return null;The FPP_Code formula:
var name = GetValueFromCustomField(AdditionalProperties, "FPP_Code");
if (!string.IsNullOrEmpty(name)) {
return name;
}
return null;The FPP_Amount formula:
var FPP_Amount = GetValueFromCustomField(AdditionalProperties, "FPP_Amount"); return FPP_Amount;
The FPP_US_Only formula:
var FPP_US_Only = GetValueFromCustomField(AdditionalProperties, "FPP_US_Only"); return FPP_US_Only;
Add/Update Dynamics 365 Business Central Company Address TO iPaaS.com (Child)
iPaaS.com data type: Company Address
This collection is a child of the Company parent. It has no mapping filter, so the company's address is captured whenever the parent company is captured. It records the company's address on the iPaaS.com company.
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 company. 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 |
Field |
| Address1 | Recommended. The street address line. Left unset when the company has no address line. |
Field |
| City | Recommended. The city. Left unset when the company has no city. |
Field |
| Region | Recommended. The county, mapped to the iPaaS.com region. Left unset when the company has no county. |
Field |
| Country | Recommended. The country, taken from the Business Central 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. |
Field |
| PostalCode | Recommended. The postal code. Left unset when the company has no post code. |
Field |
| PhoneNumber | Recommended. The phone number on the address. Left unset when the company has no phone number. |
Add/Update Dynamics 365 Business Central Company Relationship TO iPaaS.com (Child)
iPaaS.com data type: Company Relationship
This collection is a child of the Company parent. It captures the company's person relationships and links each one to the related person's existing iPaaS.com customer record.
Mapping Filter
if(RelationshipType != null && RelationshipType == "Person"){
var customerId = await GetSpaceportIdAsync(Id.Split("|")[0], "Customer", SpaceportSystemId);
if(customerId != null && !string.IsNullOrWhiteSpace(customerId.ToString()))
return true;
throw new Exception($"Customer record not found. Please create the customer manually in iPaaS using the following id of BC-365: {Id.Split("|")[0]}");
}
return false;Filter Description. Only relationships whose relationship type is Person are processed. For each one, the filter confirms that the related person already exists as a customer in iPaaS.com. When the related customer exists, the relationship passes and is recorded. When the relationship type is not Person, the relationship is skipped here. When the relationship type is Person but the related customer does not exist in iPaaS.com, the transfer stops with the error "Customer record not found. Please create the customer manually in iPaaS using the following id of BC-365: ", where <id> is the Business Central record ID — unless the company-creation option is enabled, in which case the related person is transferred in as a customer first so the relationship resolves.
Mapping Type | Source Field (Microsoft Dynamics 365 Business Central) | Destination Field (iPaaS.com) | Description |
Static |
| Type | Required. The relationship type recorded on the iPaaS.com company relationship. The shipped value |
Dynamic Formula |
| RelatedToId | Required. Resolves the related Business Central person to its iPaaS.com customer record and points the relationship at that customer. The related person must already exist as a customer in iPaaS.com (or be created during the transfer when the company-creation option is enabled); otherwise the relationship is rejected and an error names the Business Central record ID to create the customer for. |
Add/Update Dynamics 365 Business Central Company Hierarchy TO iPaaS.com (Child)
iPaaS.com data type: Company Relationship
This collection is a child of the Company parent. It captures the parent-company link of a Business Central company and records it on the iPaaS.com company as a relationship of type Parent, so the company hierarchy is preserved in iPaaS.com.
Mapping Filter
var companyId = await GetSpaceportIdAsync(Id.Split("|")[0], "Company", SpaceportSystemId);
if(companyId != null && !string.IsNullOrWhiteSpace(companyId.ToString()))
return true;
return false;Filter Description. A parent link is processed only when the Business Central parent company already exists as a company in iPaaS.com. The filter resolves the parent company to its iPaaS.com record; when an iPaaS.com company is found for the parent, the link passes and is recorded. When no iPaaS.com company is found for the parent, the link is not processed for that record — unless the company-creation option is enabled, in which case the parent company is brought into iPaaS.com ahead of the link so it resolves.
Mapping Type | Source Field (Microsoft Dynamics 365 Business Central) | Destination Field (iPaaS.com) | Description |
Static |
| Type | Required (designed constant). Sets the relationship type to a fixed |
Dynamic Formula |
| RelatedToId | Required. Resolves the Business Central parent company to its iPaaS.com company record and points the relationship at that parent. The parent company must already exist as a company in iPaaS.com; when the company-creation option is enabled, a missing parent company is transferred in first so the link resolves, otherwise the link is not recorded for that company. |
Field |
| Parent Customer Number (Custom Field) | Recommended. The Business Central customer number of the parent company, stored on the iPaaS.com Parent Customer Number custom field for reference. Left unset when the company has no parent customer assigned. The custom field must exist on the company relationship. |
Error Handling
For the complete catalog of error messages this integration can produce, see the Error Messages article. The errors most relevant to the company transfer are:
"Customer record not found. Please create the customer manually in iPaaS using the following id of BC-365: ": The relationship collection's filter found a Person relationship whose related customer does not exist in iPaaS.com, and the company-creation option was not enabled to transfer it automatically. Resolution: subscribers or their MiSP should create the customer in iPaaS.com using the Business Central record ID named in the error, or enable the company-creation option so missing related customers are transferred during the company transfer, then re-transfer the company. The error message includes the specific Business Central record ID to create.
Unable to link to an existing iPaaS.com company by name: During name matching, the integration found an existing iPaaS.com company with the same name but could not link the Business Central company to it, which can result in duplicate company records. Resolution: confirm the company name is correct and unique where separate companies must remain separate in iPaaS.com.
Missing or duplicate company number: The company number is saved as the external ID and is the key that links each transfer to its iPaaS.com company. A company with no number cannot be linked, and a non-unique company number can cause a transfer to update an unintended company. Resolution: ensure each Business Central company carries a unique company number before transferring.
Invalid email format: The company email address is not in a valid format. Resolution: ensure the email follows a standard address format before transferring.
Errors and transfer status for every company transfer are recorded in the iPaaS.com Dashboard under Integration Monitoring and the Error Logs.
Validation Rules
Company qualification: only Business Central records whose type is Company are processed; person records are skipped by the parent filter.
Person relationship validation: a relationship is captured only when its type is Person and the related customer exists in iPaaS.com (or is created during the transfer when the company-creation option is enabled).
Hierarchy validation: a parent link is captured only when the Business Central company has a parent customer assigned and the parent company exists in iPaaS.com (or is created during the transfer when the company-creation option is enabled).
Category resolution: a customer category is set only when the company's customer price group is linked to a matching iPaaS.com customer category, resolved against the environment system id in the Categories formula.
Custom fields: a custom-field value is stored only when a custom field of the same name exists on the iPaaS.com company or company relationship.
Testing and Validation
Test Scenarios
Valid company transfer. Transfer a Business Central company with name, email, phone, an address, and a customer price group. Confirm the iPaaS.com company is created with the correct name, email, phone, address, resolved category, and custom-field values.
Missing email (failure case). Attempt to transfer a company with no email address. Confirm the transfer fails and the error is logged.
Name matching. Transfer a Business Central company whose name matches an existing, unlinked iPaaS.com company. Confirm the Business Central company is linked to the existing iPaaS.com company rather than creating a duplicate.
Person relationship with existing customer. Transfer a company that has a Person relationship whose related customer already exists in iPaaS.com. Confirm the relationship is recorded against the existing customer.
Person relationship without existing customer. Transfer a company with a Person relationship whose related customer does not exist in iPaaS.com. With the company-creation option disabled, confirm the transfer stops with the customer-not-found error naming the Business Central record ID; with the option enabled, confirm the related customer is transferred in first and the relationship resolves.
Company hierarchy. Transfer a company that has a parent customer assigned. With the company-creation option enabled, confirm the parent company is captured into iPaaS.com and the parent link is recorded with type Parent.
Category resolution. Transfer a company whose customer price group is linked to a matching iPaaS.com customer category, using the correct environment system id in the Categories formula. Confirm the category is set on the iPaaS.com company.
Repeat transfer / external ID. Transfer the same company twice. Confirm the second transfer updates the existing iPaaS.com company (matched by company number) rather than creating a duplicate.
Polling reliability. Add and change several companies and their relationships in Business Central, then allow polling to run. Confirm each new and changed company and relationship is captured in iPaaS.com.
Validation Checklist
The Business Central company carries a unique, non-empty company number and a valid email address.
All required Web Services are enabled in Business Central (Customers, Customer Card, Contact Card, Customer Price Group), and the Contacts (Contact Card) Web Service exposes the Company No. field when company relationships are captured.
Custom fields exist on the iPaaS.com company and company relationship for every custom-field mapping in use, matching the Business Central field names and types.
The customer categories that the company's customer price groups resolve to exist in iPaaS.com, and the Categories formula references the correct environment system id.
Related persons exist as customers in iPaaS.com, or the company-creation option is enabled to transfer them during the company transfer.
The company-relationship and company-hierarchy options are enabled if person relationships and the parent link should be captured.
Additional Notes
The company family captures the company record together with its address, person relationships, and parent-company link in a single dispatch; the child records are not synced on their own.
Company and company-relationship polling runs on the integration's schedule so that new and changed companies and their relationships are captured reliably rather than missed between transfers.
The Categories formula references an environment-specific system id (
664) that must be replaced with the system id for the subscriber's own environment, or the category will not resolve.Outbound delete is not supported for the company or any child record; deletions in Business Central do not propagate to iPaaS.com.
Related Documents
Connections and Settings (pending publication)
Known Limitations (pending publication)
iPaaS.com to Microsoft Dynamics 365 Business Central Company Mapping Documentation (pending publication)