Hybrid connection - Web Api App for AX 2012 to Azure-part 4

This is the final post of this series.

Web Api App for AX 2012 to Azure–Intro

Deploy a Web Api App for AX 2012 to Azure–part 1

Application settings - Web Api App for AX 2012 to Azure-part 2

Authentication - Web Api App for AX 2012 to Azure-part 3

Hybrid connection - Web Api App for AX 2012 to Azure-part 4 (this one)

In this post we will set up a Hybrid Connection. This is basically a listener that sits on your on-premise server. It will expose internal port to Azure. More information on Hybrid connection on Microsoft’s site.

https://docs.microsoft.com/en-us/azure/biztalk-services/integration-hybrid-connection-overview

In your Api App, click on Networking. Then click on “Configure your hybrid connection endpoints”.

First download the connection manager. Install this on your on-premise server that you want to install the listener.

You don’t have to run the connection manager just yet. Set up the hybrid connection by clicking on the “Add hybrid connection”

Click on the “Create new hybrid connection”

Enter the required detail. Host is the AOS server name. The port is the net tcp port number.

If unsure what port to enter. Have a look at the net.tcp address in the wsdl or inside the web config file.

Now lets run the Hybrid connection Manager you installed a few steps earlier. Click on “Configure another Hybrid Connection”. It will ask you to log in. Once logged in, you can seelect an existing connection. This is what you created in the portal. Click on Save and you should see a green “Connected” status next to it. The web portal should show the same.

That is it. Give it a test by navigating to the swagger URL. The URL is just the Api App url suffixed with swagger. eg.

https://axaptaapi1.azurewebsites.net/swagger

Approve Workflow via email using template placeholders #Dyn365FO

Dynamics 365 for Finance and Operations has placeholders which can be inserted into the instructions. Normally you would want this to show up in the email that is sent. One of the most useful ones is the URL link to the exact record that you are approving. In the workflow configurations use the placeholder and build up your message. Towards the end it has workflow specific ones. The URL token is %Workflow.Link to web% . For the technical people the token is replaced in this class WorkflowDocumentField. This is what I inserted into my email template. <BODY> subject: %subject% <BR> message: %message% <BR> company: %company% <BR> for: %for% <BR> </BODY> Should look like this. The final result looks like this. If you debug these are the place holders that are put together.

Purchase requisition – Price

The price fields on the purchase requisition are non-editable for catalogue items. It is expected that a trade agreement be created. The price fields are only editable for these conditions: Form is opened view AP -> Periodic -> Purchase Requisition -> All purchase requisition, or Line type is “Non-catalogue item”, or User is task owner. Ie. The task is assigned to the user. In other words he/she maybe the purchaser that gets the price. User is approval owner. Ie. The approval is assigned to the user. In other words he/she maybe the manager that approves the final requisition. For catalogue items on the purchase requisition line can only select between the vendor directly associated with the item and the cheapest vendor as found through the purchase price trade agreements. If another vendor is requested the vendor can be blanked and the user can enter a “Proposed vendor” in the proposed vendor field on the general tab page for the purchase requisition line. NOTE: ...

Dynamics 365 Invoice Capture Feature

Microsoft recently released the new Invoice Capture for Dynamics 365 Finance. I ran through installing and configuring it. From that experience, below is my brain dump and hopefully it can help with things that are not so obvious. Three type of invoice captures There are three invoice type paths that can be captured. These drive the screen layout and what kind of information is mandatory. PO invoice Header-only Cost invoice When an invoice comes in, you can select one of the three invoice types. Below are the three screen layouts and differences. PO invoice – Invoices of this type are associated with purchase orders. The purchase order details must be determined on each invoice line. Both the header and the lines must be reviewed in Invoice capture. This will create a pending vendor invoice. Header-only – Invoices of this type are associated with purchase orders. The purchase order field on the invoice header is a mandatory field. If the Automatically create invoice lines featur...

Dynamics NAVAX

Search This Blog