Gunnar's Blog

But first… Registration for NAV TechDays 2017 have been opened.  I will do a workshop on web services and json .  I will be using both C/AL and AL with VS Code in this workshop. Make sure to register for the conference and if possible go to one or two of the workshops. Now to the topic.  Yesterday I started to develop an integration solution for bokun.io .  Their API is RESTful and uses Json file formats.  It also requires authentication. In a project like this I usually start by...

This morning I got this email: Hi Gunnar, I just wanted to inform you that your extension passed validation on US, CA, and GB. We will now get your extension checked in and it will go into the June (Update 7) release. I am excited to see if users will start to install my app.  As more markets will open for Dynamics 365 for Financials (D365) I will need to support more languages to my App. If you can help me with your local language please ping me.  The App is available on my GitHub site;...

I had my Assisted Setup wizard up and running on NAV 2017.  Everything looked fine but when the extension was being validated nothing worked. So, there is a difference between NAV 2017 and Dynamics 365 for Financials. Remember the session on Design Patterns in NAV 2017 on NAV TechDays 2016 ?  Microsoft showed what they where planning in regards to assisted setup and manual setup.  This has been implemented in Dynamics 365 for Financials but has not been released for NAV 2017. One of the feedback...

Yes!  I have passed all validation steps and Microsoft will publish my app soon. These are my marketing validation results. Marketing Validation_Objects4NAV – GL Source Names, 3.2.2017 Remember to look for this image in AppSource and try out my Extension. As I promised, all the source code is now available on GitHub. https://github.com/gunnargestsson/nav2017/tree/GLSourceNames This concludes my blog series on “My first Dynamics 365 Extension”.  Stay tuned for more...

There are a few things to look out for – things not that obvious. Look at the extension settings in my Source Control. the “appName” must match the name in Azure Publishing. The “appPublisher” must match the publisher short name. The “appVersion” must be in this format and identical to the version of you app in Azure Publishing. Also make sure to only select Canada and US even if your app can support more.  Also make sure to only select...

Back in the end of 2014 I published a renumbering tool for NAV objects .  Using DotNet I was able to increase the renumbering speed for text object files dramatically. Since then I have been asked if I could upgrade it to work with IDs and Field Numbers. Now I have. What’s more, it is also on GitHub . The Process functions are the following; Read Object Lines – Creates renumbering lines base on the objects in the selected object file. Suggest IDs – Suggest new object...

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

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

Just to check in…

Now we have gotten to Step 4 in the guided path Microsoft offered us on PartnerSource . Step 4: Provide your offer information After you have built your app, you will need to define all the attributes that will determine how your app will be listed in Microsoft AppSource. For example, your company information, your offer & plans, marketing information, support contact, and Microsoft AppSource categories. To define the attributes, visit the Microsoft Azure Publishing Portal . Refer to...

Help and notification. To make one thing clear.  The help we are used to build for the help server is not yet available for Extensions. Therefore we must make sure that all the help we anticipate the user needs will be available from the product. Microsoft have added tool tips to most of the fields in the application.  To make sure you follow the requirements create tool tips and make sure to have the property for Application Area  populated. In the previous post about the installation process...

Assisted Setup and Permissions. But first lets look at the Extension Management Codeunit. I want to store the appId in my Extension.  This appId is used in several tables in my tenant.  This appId must always be the same for this solution even if the solution is updated.  In my last post you can see that I am also setting my appId parameter in the Git repository.  There are few easy ways to get your appId.  NAV has the function CREATEGUID.  Powershell has the function New-Guid.  But perhaps...

Developement and installation. For my development I use source control management.   Soren Klemmensen did a short demo of that setup in his session in NAV TechDays 2016 .  We are working on making that solution public in a few months.  In every branch we have a setup file in a json format. That file has all the parameters needed to build an extension.  Here is the one I use for the G/L Source Names project.  When I have this Extension completed I will publish it to my GitHub Account . { "navVersion"...

One of my most popular blog entry is the one about Json .  I have also had some questions outside this website about this topic. This week I got a task.  We need to communicate with a payment service that uses REST web services and Json file format. I got a document describing the service.  Some methods use GET and some use POST.  Here is how I did this. In the heart of it all I use Codeunit 1297, “Http Web Request Mgt.”. Every time we talk to this POS API we send an Access...

Now, ten days after a succesful NAV TechDays 2016, it is time to write a short recap. As usual I met with a lot of old friends and managed to gain new ones.  Had a great time.  I hosted a workshops on extending the Data Exchange Framework on Thuesday and Wednesday.  It looks like I am the only one in my MVP group to have dug deep into that functionality.  Huge thanks to the people who attended.  I always learn a lot from you guys. On Thursday morning I had my first NAV TechDays session.  I talked...