Main steps
- Verify that a service with NavUserPassword authentication is active and that APIs are enabled.
- Install the apps.
- Complete the DocFinance setup within the app.
- Create the BC user for DocFinance integration and generate the web service access key.
- Configure the connection in DocFinance to the NavUserPassword service.
Should I publish web services?
No, the app to communicate with DocFinance uses API type pages, consequently they are automatically exposed by BC, there is no need to create the web service.
OnPrem installation
Credential Type: NavUserPassword
Enable API Services: true
Max Page Size: freely chosen (default: 20'000)
Port: freely chosen (default: 7048)
| Environment Name | Name of the environment. |
| API publisher/group/version | String that is used to dial the URL to be called (in case of change in the future, you can conveniently get the new URL) |
| Company ID | GUID of company on BC, you also get it by lookup on company list |
Setting up Oauth2 for OnPrem services
Using OData 2.0 with OnPrem services is supported.
Follow the Microsoft guide to prepare your Business Central environment to work with Entra ID by visiting the following link:
Configure Microsoft Entra authentication with OpenID Connect
Setup connection from DocFinance to BC
NOTE
It is strongly recommended to carry out this configuration with the support of the customer’s designated DocFinance consultant.
OnPrem Configuration
| Field | Description |
|---|---|
| Protocol | http or https, depending on whether SSL is enabled on the BC service. If the flag is at true, you need to enter https  |
| Host | The ip of the server on which BC is installed |
| Port | Specified within the configuration of the BC service  |
| Authentication | Basic (OAuth2 optional, for settings Username, Password, KeySecret, TenantID, ClientID follow SaaS configuration) |
| Timeout | Maximum waiting time in seconds for which DocFinance will wait for a response from BC |
| Username | BC user that we will use for the connection between DocFinance and BC |
| Password | WebService access key of the BC user that we will use for the connection between DocFinance and BC |
| EnvironmentName | Name of the BC service to which the connection will be made |
| API Publisher/Group/Version | Available on the DocFinance setup in the connection group |
| CompanyID | Available on the DocFinance setup in the connection group |
| TenantID | Not available |
| ClientID | Not available |
| Exchange backup path | Folder on which calls made by DocFinance to BC and their contents are saved, useful for debugging in case of problems |
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.
EOS Labs -