Skip to main content

Dynamics 365 for Operation Web Service calls with POSTMAN

UPDATE: 28 June 2018 - Follow this post for using secret key rather than asking user to log in http://dynamicsnavax.blogspot.com/2018/06/testing-msdyn365fo-odata-with-postman.html

In this post I will explain using POSTMAN but it really doesn’t matter what tool you use (SOAPUI is another common tool). The main point I am trying to make is how to put the authentication piece together so you can start messaging to/from the web service.
Download POSTMAN from their site https://www.getpostman.com/
In Azure AD register the application. For more info see previous post I wrote http://dynamicsnavax.blogspot.com.au/2016/09/azure-ad-in-new-portal.html
For POSTMAN, you need to enter the redirect. POSTMAN would tell you this later when you try to get a token.
Redirect URL: https://www.getpostman.com/oauth2/callback
image
Open up POSTMAN and enter your URL you want to send a request to. Click on the bright orange button “Get New Access Token”
image
This dialog will pop up. It will ask for a bit of info:
  1. Auth URL – You can enter the following. Replace the tenant and the resource url https://login.windows.net/mytenant.onmicrosoft.com/oauth2/authorize?resource=https://notarealurl1adaos.cloudax.dynamics.com
  2. Access Token URL – same thing replace the tenant and the resource url https://login.windows.net/mytenant.onmicrosoft.com/oauth2/token?resource=https://notarealurl1adaos.cloudax.dynamics.com
  3. Client ID – Get the Application ID from Azure 2 screenshots above. Mine starts with b87bf*****
image
When you click on the request, it will pop up with the login window. If you supply a Client Secret key it won’t.
You should get a response and then you can click on “Use Token” button. It will insert it into the header of the message.
image
You can now enter your parameters if you wish. Nice interface to play with. It will build up your URL for you. Then click on Send button.
Result should show in the body.
image







Labels:

Popular posts from this blog

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.
Read more

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: ...
Read more

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...
Read more