---
schema_version: "1"
id: b086cb88d50d3398b09e9508e0786a83f24f8ce8fa428067caa44b3e79037326
title: Using Anypoint Studio to Configure Microsoft Dynamics 365 Business Central 1.0
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/microsoft-dynamics-365-business-central-connector/latest/microsoft-dynamics-365-business-central-connector-studio.md
canonical_url: https://docs.mulesoft.com/microsoft-dynamics-365-business-central-connector/latest/microsoft-dynamics-365-business-central-connector-studio
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 905fe2bc27ae7b64e975d4c82b19f673d82c1f4d1d0e1a4b3f883b21f8f4acce
description: MuleSoft Documentation Site
release: "1.0"
latest: true
---
---
product: Microsoft Dynamics 365 Business Central Connector
version: 1.0
is-latest-version: true
---

# Using Anypoint Studio to Configure Microsoft Dynamics 365 Business Central 1.0

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and
configuration files.

To add and configure a connector in Studio:

1.  [Create a Mule project](#create-mule-project).

2.  [Add the connector to your Mule project](#add-connector-to-project).

3.  [Configure a source for the connector’s flow](#configure-input-source).

4.  [Add a connector operation to the flow](#add-connector-operation).

5.  [Configure a global element for the connector](#configure-global-element).

6.  [Configure the other connector fields](#configure-other-fields).

When you run the connector, you can view the app log to check for problems in real time, as
described in [View the App Log](#view-app-log).

If you are new to configuring connectors in Studio, see
[Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio).
If, after reading this topic, you need additional information about the connector fields, refer to
the
[Microsoft Dynamics 365 Business Central Connector Reference](https://docs.mulesoft.com/microsoft-dynamics-365-business-central-connector/latest/microsoft-dynamics-365-business-central-connector-reference).

## Create a Mule Project

In Studio, create a new Mule project in which to add and configure the connector:

1.  In Studio, select **File > New > Mule Project**.

2.  Enter a name for your Mule project and click **Finish**.

## Add the Connector to Your Mule Project

Add Anypoint Connector for Microsoft Dynamics 365 Business Central (Microsoft Dynamics 365 Business
Central Connector) to your Mule project to automatically populate the XML code with the connector’s
namespace and schema location and add the required dependencies to the project’s `pom.xml` file:

1.  In the **Mule Palette** view, click **(X) Search in Exchange**.

2.  In the **Add Dependencies to Project** window, type `microsoft dynamics 365 business central` in
    the search field.

3.  Click **Microsoft Dynamics 365 Business Central Connector** in **Available modules**.

4.  Click **Add**.

5.  Click **Finish**.

Adding a connector to a Mule project in Studio does not make that connector available to other
projects in your Studio workspace.

## Configure a Source

A source initiates a flow when a specified condition is met. You can configure one of these sources
to use with Microsoft Dynamics 365 Business Central:

- HTTP Listener  
  Initiates a flow each time it receives a request on the configured host and port

- Scheduler  
  Initiates a flow when a time-based condition is met

For example, to configure an HTTP Listener source, follow these steps:

1.  In the **Mule Palette** view, select **HTTP > Listener**.

2.  Drag **Listener** to the Studio canvas.

3.  On the **Listener** configuration screen, optionally change the value of the **Display Name**
    field.

4.  Specify a value for the **Path** field.

5.  Click the plus sign (**+**) next to the **Connector configuration** field to configure a global
    element that can be used by all instances of the HTTP Listener source in the app.

6.  On the **General** tab, specify the connection information for the connector.

7.  On the **TLS** tab, optionally specify the TLS information for the connector.

8.  On the **Advanced** tab, optionally specify reconnection information, including a reconnection
    strategy.

9.  Click **Test Connection** to confirm that Mule can connect with the specified server.

10. Click **OK**.

## Add a Connector Operation to the Flow

When you add a connector operation to your flow, you are specifying an action for that connector to
perform.

To add an operation for Microsoft Dynamics 365 Business Central Connector, follow these steps:

1.  In the **Mule Palette** view, select **Microsoft Dynamics 365 Business Central** and then select
    the desired operation.

2.  Drag the operation onto the Studio canvas to the right of the source.

## Configure a Global Element for the Connector

When you configure a connector, configure a global element that all instances of that connector in
the app can use. Configuring a global element requires you to provide the authentication credentials
that the connector requires to access the target Microsoft Dynamics 365 Business Central system.
Microsoft Dynamics 365 Business Central Connector supports Basic Auth and OAuth2.

To configure the global element for Microsoft Dynamics 365 Business Central Connector, follow these
steps:

1.  Select the operation in the Studio canvas.

2.  In the configuration screen for the operation, click the plus sign (**+**) next to the
    **Connector configuration** field to access the global element configuration fields.

3.  On the **General** tab, in **Connection**, select the authentication method to configure.

    - Select [Basic Auth](#basic-auth) to configure Basic Auth.

    - Select [OAuth2](#oauth2) to configure OAuth2.

    You can reference a configuration file that contains ANT-style property placeholders
    (recommended), or you can enter your authorization credentials in the global configuration
    properties. For information about the benefits of using property placeholders and how to
    configure them, refer to
    [Anypoint Connector Configuration](https://docs.mulesoft.com/connectors/introduction/intro-connector-configuration-overview).

4.  On the **Advanced** tab, optionally specify reconnection information, including a reconnection
    strategy.

5.  Click **Test Connection** to confirm that Mule can connect with the specified server.

6.  Click **OK**.

### Basic Auth

Enter the following information on the **General** tab of the **Global Element Properties** screen
to configure Basic Auth:

<table><colgroup><col> <col></colgroup><thead><tr><th>Field</th><th>User Action</th></tr></thead><tbody><tr><td><p><strong>Name</strong></p></td><td><div><div><p>Configuration name</p></div></div></td></tr><tr><td><p><strong>Username</strong></p></td><td><div><div><p>Username used to authenticate the requests</p></div></div></td></tr></tbody></table>

### OAuth2

Use OAuth 2.0 to delegate user authentication to the service hosting the user account. For more
information, refer to
[Configuring OAuth 2.0 for Connectors](https://docs.mulesoft.com/connectors/introduction/intro-config-oauth2),
[Configuring OAuth 2.0 for Connectors on CloudHub](https://docs.mulesoft.com/connectors/introduction/intro-config-oauth2-cloudhub),
or [OAuth Support in the SDK](https://docs.mulesoft.com/mule-sdk/latest/oauth).

Enter the following information on the **General** tab of the **Global Element Properties** screen
to configure OAuth2:

<table><colgroup><col> <col></colgroup><thead><tr><th>Field</th><th>User Action</th></tr></thead><tbody><tr><td><p><strong>Name</strong></p></td><td><div><div><p>Configuration name</p></div></div></td></tr><tr><td><p><strong>Consumer Key</strong></p></td><td><div><div><p>OAuth consumer key, as registered with the service provider</p></div></div></td></tr><tr><td><p><strong>Consumer Secret</strong></p></td><td><div><div><p>OAuth consumer secret, as registered with the service provider</p></div></div></td></tr><tr><td><p><strong>Listener Config</strong></p></td><td><div><div><p>Configuration for the HTTP listener that listens for requests on the access token callback endpoint</p></div></div></td></tr><tr><td><p><strong>Callback Path</strong></p></td><td><div><div><p>Path of the access token callback endpoint</p></div></div></td></tr><tr><td><p><strong>Authorize Path</strong></p></td><td><div><div><p>Path of the local HTTP endpoint that triggers the OAuth dance</p></div></div></td></tr></tbody></table>

## Configure Additional Connector Fields

After you configure a global element for Microsoft Dynamics 365 Business Central Connector,
configure the other required fields for the connector. The required fields vary depending on which
connector operation you use.

## View the App Log

To check for problems, you can view the app log as follows:

- If you’re running the app from Anypoint Platform, the app log output is visible in the Anypoint
  Studio console window.

- If you’re running the app using Mule from the command line, the app log output is visible in your
  OS console.

Unless the log file path is customized in the app’s log file (`log4j2.xml`), you can also view the
app log in the default location `MULE_HOME/logs/<app-name>.log`.

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio)

- [Microsoft Dynamics 365 Business Central Reference](https://docs.mulesoft.com/microsoft-dynamics-365-business-central-connector/latest/microsoft-dynamics-365-business-central-connector-reference)

- [Salesforce Help](https://help.salesforce.com)