Pages

Showing posts with label NAV 2017. Show all posts
Showing posts with label NAV 2017. Show all posts

Friday, January 20, 2017

Import a File and Export it as a ZIP file in NAV 2017

Hi guys,

I did some R&D on the File Management codeunit (419) which is available in NAV and found out that it has pretty much all the functions related to files available in it.

For example: For zipping a file, we no longer need third party software to do the job for us in NAV.

Like this, there are many more functions available in this codeunit which we can use to our advantage and play with 'em. I have used some of the functions in an example which I will demonstrate below,

Before starting, I want you to know that this post is not limited to just importing and zipping a file. I want to show you the ability of codeunit 419 and the functions available in it. I have used a couple of them in my code.

Sunday, December 04, 2016

Common mistakes we make in C/AL - Vol. 3 - Tips, Tricks & Facts #8

In this post I will talk about Significance of Using CALCSUMS in C/AL coding. 

Before writing about this topic I would mention here that, if a tool (or function) is available then we must use it to our system's benefit. Tools or functions are available in AL (or any other development envo.) to reduce the time taken by transactions and faster output generation.

You can find the detailed definition of CALCSUMS on MSDN. This function must be used to calculate sums of a Decimal field. However, the scope of CALCSUMS has been widened to Integer, BigInteger and Duration type fields along with Decimal type fields from NAV 2016 and up.

Friday, November 04, 2016

Code changes - NAV 2016 to NAV 2017 - Tips, Tricks & Facts #5

Hi guys, I am gonna talk about the code changes that I liked in NAV 2017 and you must know about them too.

Coding in NAV 2017 is better, as expected.

Just to give an overview. I will cover some examples as follows,


1. Codeunit 80 - OnRun Trigger - This trigger used to be a home of like more than a thousand lines of code. Well now, it has been decreased to a hundred lines of code, give or take. Check the image below,


Tuesday, September 27, 2016

New Development Environment for NAV unleashing this Christmas! :D

Checkout this picture taken by Kauffmann in Directions US.


I will talk about this picture later. First things first.. So, I was scrolling through my twitter feed, seeing updates from people and companies about NAV Directions. And the picture below dropped my jaw. LITERALLY!

No, It is not about NAV 2017 or Dynamics 365. I am looking forward to these too but it is the 3rd thing mentioned in this picture, new development environment, which got me so excited, thrilled, delighted and what not!! Thank you Microsoft for exciting us every time we try to settle. Thank you, seriously!

Below is the stuff that Waldo and Kauffmann have shared in their blogs. Thank you both for sharing the knowledge with us.

So, as you all must have already got to know that in NAV 2017, we will be working with a new tool known as VS Code editor. The VS Code editor will become the preferred way of doing modifications in the future. Eventually, it will enable us to do any kind of modification that we can do today. 

Another picture taken by Kauffmann in Directions US. These pictures are interesting!!


The capabilities of Extensions have been immensely improved in NAV 2017. All object types are available now .. and more. (I so want to explore this “more” part, I know you guys will agree with me here!)

In short this will be the new stuff available to us,

-          Additional Object Types in Extensions:
o   Reports
o   XMLPorts
o   Queries
o   Custom report templates

-          Default and starting data

-          Multilanguage captions

-          Support for .Net Framework Add-Ins
o   .NET interop types executed on the server
o   Client-side JavaScript
o   WinForms extensibility control add-ins

-          Support for web services

-          Restore and backup data in extensions
o   NAVAPP.RESTOREARCHIVEDATA
o   NAVAPP.DELETEARCHIVEDATA

-          Updated PowerShell to publish Extensions
o   Publish to SQL db on Azure SQL

-          Installing Extensions
o   Users can install/uninstall from Extensions Mgt page.

There is a lot to deep dive into, check the full posts here and here. Do check these posts, they have a lot more interesting stuff, like a new datatype called "MediaSet" coming in NAV 2017. (I will say no more, check the posts :) go go!)

The “New developer Experience“ is not going to be released in the upcoming release. It’s only going to be there in preview at Christmas. There must be a lot of questions arising, I know, check these posts to get all the knowledge about what’s really new in NAV 2017.

Grateful because i am expecting that there will be so much to learn soon enough. Well, Let's see. Christmas will be so merry this time if we get what we all are expecting by that time.

#Excited #KeepLearning #KnowledgeForNAVTechies
Cheers!
Ishwar

Saturday, September 24, 2016

Implement Extensions in NAV

Below is the easiest way I found to implement extensions in NAV.

Let's Start!

The above diagram shows how extensions work and the idea behind bringing extensions into existence. Extensions can be installed independently on different tenants belonging to the same service and each tenant will have only the functionality of the extensions installed on it.

Extensions can co-exist in a tenant and independently as well. In the above diagram Extension 1 and 2 are installed on Tenant 1 and Tenant 2. While Extension 3 is only installed on Tenant 3 and likewise.

7 Easy steps to implement extensions in NAV are as follows:

SAP vs NAV

Hey Guys, Happy weekend!


I might be a little biased with this post. You know why!!

If the battle is SAP vs NAV, then Dynamics NAV is what you must go for. Why am I saying this so bluntly?