Automated testing #MSDyn365FO Odata with Postman

In the last post I did a quick run through on using Postman for testing Odata services.

This post I will give some tips on how you can write automated tests using Postman.

Tip 1 – Parameterise as much as you can

Parameterise using the environment settings. It will make your collection portable to other projects.

Below is an example where we have the environments settings parameterised.

You can see how I used it here. Now I can utilise the same thing across requests.

Tip 2 – Write test scripts

Test scripts are very easy to work with. This is for demonstration purpose only. I will explain how you can retrieve the values in the returned json.

Take the example here, where we use the “get customer” odata service. It returns a nested array with the values.

You can write a simple test script to retrieve values. In the below highlighted box you can see that I am logging it to the console. I am not really testing much here.

The console will return the below.

One bonus tip here. Just click on the snippet codes to get sample code from Postman. Really helpful.

Tip 3 – Automated testing

Usually you will have dependent requests. The first request in our example retrieved the OAuth token and saved it in the environment settings. For the second request to work, it must get a fresh token to authenticate.

To run the collection, click on Runner at the top left of the main window.

Once the runner window opens up. Select you collection or folder. Then click on Run button at the bottom.

Once complete, you get your result.

If you are new to all this. I would recommend taking a look at postman blog on automated testing.

http://blog.getpostman.com/2014/03/07/writing-automated-tests-for-apis-using-postman/

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