HubSpot to Microsoft Dynamic GP

With Dynamics GP, a business management solution for small and medium-sized organizations that goes beyond accounting software, you can have more control over your finances, inventory, and operations.

Overview

A company management tool called Dynamics GP provides a variety of functionalities to automate and streamline corporate activities. Take control of your projects, finances, HR, supply chain, and CRM. With the help of business intelligence capabilities, make better data-driven decisions.

Authentication

The first step in using the Microsoft Dynamics GP connector is to go to your middleware solution account page and choose the process you want to work on. Once inside the workflow builder, look for and drag the Microsoft Dynamics GP connector into your workflow from the connectors panel (on the left).

To add a new authentication, select "Add new authentication" from the list of options under the "Authentication" field in the properties panel on the right after selecting the new Microsoft Dynamics GP connector step.

A pop-up window for ‘middleware solution’ authentication will appear as a result. You will be prompted to give your authentication a name and indicate whether you want to create a "Personal" or "Organization" authentication on the first page.

You can see that the following page requests your "WSDL URL," "Username," and "Password." You may also enter "Domain" and "Workgroup" by scrolling down.

<span style=>

Depending on whether you are utilizing the Legacy endpoint or the Native endpoint, the WSDL URL you will enter here will be slightly different:

• Legacy endpoint: http://server_name:port/DynamicsGPWebServices?singleWsdl
• Native endpoint: http://server_name:port/Dynamics/GPService?singleWsdl

Replace "server name" and "port" in the aforementioned URLs with the server name and port that were chosen during installation.

http://server_name:port/DynamicsGPWebServices

http://server_name:port/Dynamics/GPService

The other fields' values will be those that were predetermined during the installation of "Web Services for Microsoft Dynamics GP."

Click the "Create authentication" button after adding these fields to the Tray.io authentication popup box. Return to the workflow builder properties panel's settings authentication field and choose the recently added authentication from the list of available dropdown selections.

Your connector authentication configuration ought to be finished at this point.

Available Operations

The examples that follow demonstrate the use of one or two of the available connector procedures.

For information on all of the actions this connector may do, please check the Full Operations Reference at the bottom of this page.

Note Regarding Operation's Use

List sales orders

Unlike previous List operations, this one uses the GetSalesOrderList method and, without a "Criteria" argument, may fail.

List sales orders fail in the absence of criteria.

'List sales orders' criteria workaround

As demonstrated in this example of a successful request, one potential workaround is to specify a filter such as Customer ID Not Equal Value empty string.

By entering a value, setting it by clicking outside the field, removing it, and then setting an empty string by clicking outside the field, you can transmit an empty string.

<Custom component span content type TBD>

All Web Service methods—with the exception of two—require a "Context". Setting the "Organization key" to the Company "Id" of 7, for instance

The GetCompanyList method (represented by the operation "List companies") and the GetWSEnabledCompanyList method (represented by the operation "List companies (Web services enabled)" respectively) are the exceptions. In the event that such a "Context" is provided, these two operations fail.

Example Usage

Here's an illustration of how you might use the Microsoft Dynamics GP connector to loop through a list of customers and return all of their data:

The actions are as follows:

1. Use a manual trigger to create a new process.
2. Set up the "List customers" operation and include a "Microsoft Dynamics GP" connecting step.
3. Set up the "Loop list" operation to iterate through the list of customers and include a "Loop Collection" connector step.
4. Set up the "Get customer" action to retrieve the whole set of data for each customer by adding a "Microsoft Dynamics GP" connector step.

The end result should resemble this:

1. Using a manual trigger, setup a new workflow

Choose the Manual trigger from the available trigger options after clicking "Create new workflow" on the main dashboard:

You will be taken to the workflow dashboard after clicking the "Create workflow" button.

Now is the time to start creating your workflow.

2. Setup the "List customers" operation.

Insert a "Microsoft Dynamics GP" connector into your second step from the connectors panel on the left. Decide on "List customers" as the operation.

There must be a "Context," which has been defined as previously stated.

To make things clearer for you and other users, feel free to rename your steps as you go.

Although this section is optional, this List operation has been given certain filter options to help it produce fewer results.

3. Set the "Loop list" operation.

Then, as the following step, look for the "Loop Collection" connector in your connector panel and drag it into your workflow. Choose "Loop list" as your operation type.

You can loop through a list of results using the "Loop Collection" connector. In this illustration, we'll utilize it to repeatedly loop over the information discovered via the earlier "Microsoft Dynamics GP" connector stage.

Start by utilizing the 'List' mapping icon (located next to the list input field, within the properties panel) to create the connector-snake in order to define the list you want to loop through.

[JsonPath and Connecter-Snake to be created]

4. Set up the "Get customer" procedure to retrieve all of the customer's information.

Drag a "Microsoft Dynamics GP" connector into the "Loop Collection" step itself as the final step. Select "Get customer" as the operation. As you can see, the "ID" field is necessary for the "Key" input.

Start by generating the connector-snake using the 'ID' mapping icon, which can be located in the properties panel next to the 'ID' input field, in order to define this ID. Choose the Id within Key from the list of output characteristics that appears while you are hovering over the "Loop Collection" connector. The 'ID' input field will automatically contain a jsonpath, and the type selector will now read jsonpath.

When the process is executed, a loop will be created over the results returned by the 'List customers' operation, retrieving all of the relevant data for each result.

All Operations

[To be created]