Summary:
This article details the Solver Cloud Business Central (BC) v2 Connector which supports both the QuickStart offering and manual creation of integrations. This article is for those interested in manually configuring an integration using the Business Central v2 connector.
Article Sections:
More Information:
Pre-Install Requirements and Technologies
The BCv2 Connector has the following requirements:
- You must be a Solver Cloud AND Business Central Cloud Customer.
- Users must be a fully licensed (non team member license user) within BC.
- You are allowing popups in your browser. This is required because during configuration of the BC integration, you must sign into your BC tenant via a Microsoft login popup.
- During the configuration in Solver Cloud, an active Azure AD account with access to your Business Central is required to login and connect Solver Cloud to your BC tenant.
- It is strongly recommended to install the Solver Extension in your BC environment. This extension "extends" the capabilities of the Microsoft (MS) BC APIv2 and provides well-formatted data to Solver Cloud.
There are a couple important items to be aware of with MS BC APIv2 compared to the MS OData offering:
- APIv2 is restricted, see the above link for the data that is available.
- Unlike the OData v4 offering, MS BC APIv2 does not provide a way to be easily customized.
- You may have to use a combination of the BC v2 and BC v1 connectors to get the exact data you need.
Prior to using the BCv2 connector, it is strongly recommend to install the Solver Extension found in the Microsoft Marketplace. To do so, follow these steps:
- From within your BC tenant and as a BC administrator, search Extension Management.
- In the popup that appears, click Manage > Extension Marketplace.
- Search for Solver and click the 'Get it now' button once it appears.
This completes the steps to install the extension.
Configuration
You are now ready to configure your BC integration. To do so, follow these steps:
- Log into Solver Cloud and navigate to Data Warehouse > Integrations > Add New > select the Microsoft Dynamics BCv2 Connector > Click "Create Manual".
- Click Authenticate.
In the popup that appears, type in your Microsoft credentials. If your organization has enabled Multi-factor authentication, you will be prompted to provide this code as well.
Note: If you are already logged in, you will be directed to the next screen - The next screen will show your logged in user and the options to choose your environment, Sandbox, Production or any other environment your organization has created, and the company.
- The BC v2 connector is a per-company configuration, meaning if you have 5 companies in your BC environment, you will configure this 5 times if you need to load data from all companies.
Should you want to change the logged in user, use the Switch User option.
- The BC v2 connector is a per-company configuration, meaning if you have 5 companies in your BC environment, you will configure this 5 times if you need to load data from all companies.
- Click Continue.
The application will load to the task creation screen where you will create various integration tasks to the data that you need to load into Solver Cloud.
Data Mapping
| Source Object Name | Typical Solver Cloud Field | Additional Notes | |
| Chart of Account | accounts | Account | |
| Department | Departments | Department | |
| Company | companyInformation | Entity | |
| Currency | currencies | Currency | |
| Opening Balance | openingBalances | General Ledger |
|
| General Ledger Entries | generalLedgerEntries | General Ledger Detail | Business Central does not provide a GL Summary data endpoint. Create GL summary using a Business Rule found in the attachments section. |
In addition to your Global Dimensions, your custom dimensions will also appear as Source objects for easy mapping.
Migrating from Business Central V1 to Business Central v2 Data Mapping
The below chart compares, at a high level, the Dimension and GL Detail mapping done in the BCv1 connector (OData) vs the updates you have to do to convert to the BCv2 connector for a GL integration.
The BCv1 connector typically requires the use of many business rules. Please review your integration prior to making these changes.
| Example |
Odatav4 Module TaskMapping |
Odatav4.Code | Odatav4.Description |
APIv2 Module TaskMapping |
APIv2.Code | APIv2.Descrition | |
| Account | chartOfAccounts.No | chartOfAccounts.Name | accounts.Code | accounts.displayName | |||
| CustomDims | Department | <customObject - dimensionSetRule> | Department.Code | Department.DisplayName | |||
| GL Detail | |||||||
| GLDetail.Account | Solver_GL.G_L_Account_No | generalLedgerEntries.accountNumber | |||||
| GlDetail.Category | HardCoded | HardCoded | |||||
| GLDetail.Scenario | HardCoded | HardCoded | |||||
| GLDetail.Currency | generalLedgerEntries.Currency | ||||||
| GLDetail.Entity | HardCoded | hardcoded | |||||
| GLDetail.TimePeriod | Solver_GL.PostingDate | generalLedgerEntries.postingPeriod | |||||
| Gdetail.Dimensions | Department | Solver_GL.Dimension_Set_ID | generalLedgerEntries.Department | ||||
| GL_Detail.Value1 | Solver_GL.[Debit_Amount]-SolverGL.[CreditAmount] | generalLedgerEntries.[debitAmount]-generalLedgerEntries.[creditAmount] | |||||
| GL_Detail.TrasnsactionId | Solver_GL.EntryNo | ||||||
| Opening Balance | |||||||
| GL.Account | Business rule or some process | openingBalances.accountNumber | |||||
| GL.Scenario | Hardcoded | ||||||
| GL.Entity | Hardcoded | ||||||
| GL.TimePeriod | openingBalances.periodStartDate | ||||||
| GL.Dimensions | NA | ||||||
| GL.Value1 | Opening Balance Amt | openingBalances.balanceAtDate | |||||
Frequently Asked Questions:
- Does the BCV2 connector account for every field in our BC environment?
- No, you can use the BCV1 connector if you cannot find the field. You may use the BCV1 and BCV2 in combination with each other as long as they are not updating the same record.
- If BCV1 is not in your environment, it is disabled and needs to be enabled by submitting a ticket to Solver Support
- Does the BCV1 connector cost money?
- There is no extra cost to add the BCV1 connector to your Solver Environment if you are currently paying for the BCV2 connector or QuickStart with BC.
Properties:
Cloud