> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/6.12/development/flow-studio/connectors/communication/web-service/example/webservice-example-connector-to-microsoft-dynamics-ax.md).

# Webservice example: Connector to Microsoft Dynamics AX

This is an example of how the Web Service connector can be used to consume Microsoft Dynamics AX AIF services.

How to set up any AIF service, such as a document service, in Microsoft Dynamics AX is beyond the scope of this example, but once that has been done the Web Service connector can be used to consume it. From AX, get the URI to the WSDL of the service. 

![](https://3419513391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-p-Y6jMZstljnKL4S_%2F-M-p1_5m-BJ9g-tPihPe%2Fhelp_root_connectors_communication_webservice_AX_1.png?alt=media\&token=dd31ae98-9d93-4dc9-bb19-04a4dd18766a)

**Step 1**

Copy the URI from AX.

Create connector of type Web Service.

Provide a name for the connector and paste in the URI. Make sure server address is correct and press "Create/update"-button 

![](https://3419513391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-p-Y6jMZstljnKL4S_%2F-M-p1bql0SVssiRyAU8j%2Fhelp_root_connectors_communication_webservice_AX_2.png?alt=media\&token=7b8d78f4-05d1-43c2-a71a-8353eb8f064a)

**Step 2**

Wait for the connector to be created 

![](https://3419513391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-p-Y6jMZstljnKL4S_%2F-M-p20cwz7OaUlqWnLIs%2Fhelp_root_connectors_communication_webservice_AX_3.png?alt=media\&token=4ca2c6cd-7c74-4d97-a0b5-bde9f84213d0)

**Step 3**

Examine the configuration. Might be a good idea to increase maxRecievedMessageSize. 

![](https://3419513391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-p-Y6jMZstljnKL4S_%2F-M-p23es_OnDiq-a5Ahh%2Fhelp_root_connectors_communication_webservice_AX_4.png?alt=media\&token=936e2c4e-a350-4bb5-bdcf-0d4e983962d2)

**Step 4**

Setup Client credentials by expanding Client credentials -> Windows and enter UserName and Password and, if required, domain and impersonation level. 

![](https://3419513391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-p-Y6jMZstljnKL4S_%2F-M-p28AUk21yLgWzR3Kc%2Fhelp_root_connectors_communication_webservice_AX_5.png?alt=media\&token=5eae9754-f20c-4a27-95fe-3f34359d35cf)

**Step 5**

Save the configuration

The connector should now be available to be used in a Machine Step.

 \
Last update 2019-11-15 15:16:02Version: 6.10.8.37269

![](https://3419513391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-p-Y6jMZstljnKL4S_%2F-M-p2CVPpikMhkxGNfL2%2Fhelp_root_connectors_communication_webservice_AX_6.png?alt=media\&token=e94e13e1-e934-427e-84fb-4e1ee3456e91)

![](https://3419513391-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LtPTgZOYmpJka4jqs1v%2F-M-p-Y6jMZstljnKL4S_%2F-M-p2Ffp_SZEXH1hbX1W%2Fhelp_root_connectors_communication_webservice_AX_7.png?alt=media\&token=7a066585-58b1-4f24-90b2-9f9cf279f76b)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.novacuraflow.com/6.12/development/flow-studio/connectors/communication/web-service/example/webservice-example-connector-to-microsoft-dynamics-ax.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.