MicrosoftBusinessCentralV2 - Connector Settings
This document details the connector-specific settings for the Microsoft Business Central V2 connector. These settings influence how the connector integrates with Microsoft Business Central, affecting data synchronization, authentication, and various business processes. Application administrators and implementation consultants can configure these settings to tailor the connector's behavior to specific business requirements.
Connector settings are stored within the App4Sales platform's configuration, typically managed through a dedicated portal UI. They are applied at runtime to control the connector's operations, such as which data to sync, how to authenticate with Microsoft Business Central, and how certain business rules are applied during data exchange.
Authentication & Connection
Setting | Description | Values / Defaults | Dependencies / Effects |
Tenant Domain | The Azure Active Directory (AAD) GUID. This identifier is crucial for authenticating the connector with your Azure AD tenant. It can be found in the Azure Portal under Azure Active Directory > Settings > CatalogID. | String (GUID format). Required. | Essential for all authentication and communication with Microsoft Business Central. Incorrect value will prevent connection. |
Environment Name | Specifies the Microsoft Business Central environment to which the connector will connect. This can be 'Production', 'Sandbox', or any custom environment name configured in your Business Central instance. | String (e.g., "Production", "Sandbox"). Required. | Determines which Business Central environment the connector interacts with. Must precisely match the configured environment name. |
Client ID | The client ID of the Business Central application registration within your customer's Azure AD. This acts as a unique identifier for the App4Sales connector application when requesting access tokens. | String (GUID format). Required. Encrypted for security. | Part of the OAuth 2.0 client credentials flow. Must correspond to a valid application registration in Azure AD. |
Client Secret | The client secret generated for the Business Central application registration in your customer's Azure AD. This confidential key is used in conjunction with the Client ID to authenticate the connector. | String. Required. Encrypted for security. | Confidential component of the OAuth 2.0 client credentials. Should be treated as sensitive information and secured appropriately. |
Company Name | The name of the company within the Business Central environment that the connector will interact with. This name is used by the connector to identify and retrieve the correct internal Company ID. | String. Required. | Ensures the connector operates within the correct company context in Business Central. Must exactly match a company name configured in Business Central. |
Scope | Defines the permissions the App4Sales connector requests during the OAuth authorization flow. If left empty, the connector will request authorization with the default scope configured for the Business Central application registration. | String (e.g., "https://api.businesscentral.dynamics.com/.default"). Default: Empty, using default scope. | Controls the level of access the connector has to Business Central data and APIs. |
General Configuration
Setting | Description | Values / Defaults | Dependencies / Effects |
Core-Sales BC extension version | Specifies the version of the Core-Sales Business Central extension installed. This ensures compatibility and correct functionality with the installed extension. | Dropdown with "v2.0". Default: "v2.0". | Impacts behavior related to Core-Sales specific functionalities. Must match the installed extension version in Business Central. |
Use payment terms as payment conditions | When enabled, the payment terms defined in Business Central will be mapped and used as payment conditions within App4Sales. If disabled, payment conditions might be handled differently or default values may apply. | Boolean (True/False). Default: False. | Affects how payment information is synced and displayed in App4Sales orders. |
Microsoft Business Central base currency code | The base currency code used in Microsoft Business Central. This setting helps the connector correctly handle currency conversions and display financial data in App4Sales. | String (e.g., "EUR", "USD"). | Critical for accurate financial data synchronization, especially for multi-currency environments. |
Value of the type for companies for during the contact synchronization (default: Company) | Defines the value used for the 'type' field when synchronizing company contacts from Business Central to App4Sales. The default value is "Company". | String. Default: "Company". | Influences how company contacts are categorized within App4Sales after synchronization. |
Include archived orders in history | If enabled, the connector will synchronize archived sales orders from Business Central into the order history in App4Sales. | Boolean (True/False). Default: False. | Affects the completeness of order history visible in App4Sales. Enabling may increase sync duration. |
Delete orders which are not available at MBC from orders overview | When enabled, any orders present in App4Sales that are no longer found in Microsoft Business Central will be removed from the App4Sales orders overview. | Boolean (True/False). Default: False. | Ensures consistency between App4Sales and Business Central order lists by cleaning up outdated entries in App4Sales. |
Prefix for credit memo invoices | A custom prefix that will be applied to credit memo invoices synchronized from Business Central to App4Sales. This can help in identifying credit memos. | String. | Modifies the display name of credit memo invoices in App4Sales. |
Locations for stock (comma separated) | A comma-separated list of location codes from Business Central. The connector will use these specified locations when synchronizing stock information to App4Sales. | String (comma-separated list of codes). | Filters which stock locations' data is synced. If empty, all locations might be considered or a default behavior applies. |
Save item category code using item category levels | If enabled, the item category codes will be saved in App4Sales based on their hierarchical levels defined in Business Central, creating a structured category path. | Boolean (True/False). Default: False. | Affects the structure and granularity of item categories in App4Sales. |
Indicator field name to sync item categories | Specifies a custom field name in Business Central that acts as an indicator to determine which item categories should be synchronized to App4Sales. | String. | Allows for selective synchronization of item categories based on a custom Business Central field. |
Extra field name for purchase package size | Defines the name of an extra field in Business Central that holds information about the purchase package size of items. This data can then be synchronized to App4Sales. | String. | Enables synchronization of custom purchase package size data from Business Central. |
VAT Business posting group code for item VAT percent | Specifies the VAT Business Posting Group code from Business Central to determine the VAT percentage for items during synchronization. | String. | Influences how VAT percentages are calculated and applied for items in App4Sales. |
NL customer default Gen. Bus. Posting Group | The default General Business Posting Group for Dutch (NL) customers. This setting is used when synchronizing customers from Business Central to App4Sales if a specific posting group is not defined. | String. | Ensures correct financial postings for NL customers based on Business Central's general business posting groups. |
EU customer default Gen. Bus. Posting Group | The default General Business Posting Group for European Union (EU) customers. Similar to the NL setting, this is used during customer synchronization when a specific posting group is absent. | String. | Ensures correct financial postings for EU customers based on Business Central's general business posting groups. |
NL customer default Customer Posting Group | The default Customer Posting Group for Dutch (NL) customers. This setting is applied during customer synchronization if a specific customer posting group is not specified in Business Central. | String. | Determines the default customer posting group for NL customers, impacting their general ledger entries. |
EU customer default Customer Posting Group | The default Customer Posting Group for European Union (EU) customers. This setting is used for customer synchronization when a specific customer posting group is not defined in Business Central. | String. | Determines the default customer posting group for EU customers, impacting their general ledger entries. |
Execute next sync as full synchronization for all mbc data | When enabled, the next synchronization cycle will perform a full synchronization of all relevant Microsoft Business Central data, regardless of incremental changes. This is useful for refreshing all data. | Boolean (True/False). Default: False. | Forces a complete data refresh. Enabling this can significantly increase the duration of the next synchronization. |
Special Logic & Filters
There are no explicitly documented special logic or filters directly controlled by these settings beyond what is described in the individual setting explanations. The behavior of these settings is generally to enable or configure specific data synchronization and processing paths within the connector.
Domain Specifics
Authentication
The connector leverages Azure Active Directory for authentication with Microsoft Business Central. The Tenant Domain, Client ID, and Client Secret are critical for establishing a secure OAuth 2.0 connection. These credentials must be correctly configured in the Azure Portal for the connector's application registration.
Catalog & Item Data
Settings such as Locations for stock, Save item category code using item category levels, and Indicator field name to sync item categories allow administrators to control the granularity and scope of item and stock data synchronized from Business Central to App4Sales. The Extra field name for purchase package size enables the inclusion of custom item attributes.
Order Processing & Financials
Financial-related settings, including Use payment terms as payment conditions, Microsoft Business Central base currency code, and various General Business/Customer Posting Group settings (NL customer default Gen. Bus. Posting Group, EU customer default Gen. Bus. Posting Group, etc.), ensure that sales orders and customer financial data are accurately reflected and processed according to Business Central's accounting rules within App4Sales.
Synchronization Control
The Include archived orders in history and Delete orders which are not available at MBC from orders overview settings provide control over the completeness and accuracy of the order data presented in App4Sales. The Execute next sync as full synchronization for all mbc data setting offers a mechanism to force a complete data refresh, which can be useful for troubleshooting or initial setup.