In my post about Json and Rest web services I showed how to use the standard Codeunit no. 1297 for web service communication.
Today I was asked to do this in NAV 2015. I must admit, I forgot that this Codeunit was not available in NAV 2015.
So I made one.
This one has identical functionality to the one delivered with NAV 2016. To catch and handle the errors I use the NAV Web Request Add-in that I created and published here on my blog.
Now I can easily move that Json code down to NAV 2015.
Download here –> COD1297-NAV2015
I am now in the validation of my app. Unfortunately I don’t have enough time to make this go any faster so please be patient.
This process will take time. Here is an example of the expected time frame.
As you may have read in my previous post I created a few videos. These are the first comment from Microsoft about these videos.
The obvious information from here is that I can’t use Dynamics NAV anywhere in my Dynamics 365 for Financials extension.
I asked and this is the solution they gave me.
If you add &aid=fin to the end of your Web Client URL it will add the Dynamics 365 shell.
When I start my web client the normal Url is “http://tfw107131:8080/NAV2017DEV0000077/WebClient/”. By adding the suggested switch to the Url and starting the web client with “http://tfw107131:8080/NAV2017DEV0000077/WebClient/?aid=fin” I will get the Dynamics 365 shell.
The parameters that are added to the Url start with a question mark (?) and after that each parameter starts with the ampersand (&). As an example, I have opened the Customer List and the Url says: “http://tfw107131:8080/NAV2017DEV0000077/WebClient/?aid=fin&bookmark=27%3bEgAAAAJ7CDAAMQAxADIAMQAyADEAMg%3d%3d&page=22&company=CRONUS International Ltd.&dc=0”. The parameter order does not matter, the “aid=fin” can be placed anywhere in the parameter part of the Url.
Now I am back at creating screen shots, videos and documentation. All with the new Dynamics 365 for Financials look and feel.