So yeah. A few days ago Microsoft decided to post on their official blog the development guidelines that they use for the development of Microsoft Dynamics NAV, and also they take the opportunity to solve some of the questions a lot of us had.
That’s right! In the official NAV team blog they’ve announced a new developers center on which you can easily and quickly find all the materials related to NAV2013R2 and NAV2015.
On this center they intend to keep the information updated and introduce new materials regularly. So it would not be a bad idea to follow their advice and add this website to the “visit regularly” list
As all of you might be aware of, Microsoft published the cmdlets that were destined to speed up the merging of objects. But if you have tried them you will agree that they can be definetly not user-friendly.
Due to this, it fills me with pride to be able to publish this utility with user interface based on these tools, and also adding some other features that allow for greated speed and to create a hub for all the tasks in a single application.
This is Merging!, TIM from now on, offers several options to speed up our merges.
Info and downloads here: http://msnav.es/merging-information-download/
Up to NAV2009 we had at our disposal the option of closing sessions from the same form we could see the sessions on. But unfortunately this option disappeared in NAV2013.
The page where we can see the same info is now the debugger, and does not have a “Kill session” option we are looking for.
What can we do in this version then?
A new function was introduced called “STOPSESSION”. It enables us to do the same thing we could do before.
So yeah. The Microsoft NAV Team has finally confirmed the compatibility of SQL Server 2014 with:
- Microsoft Dynamics NAV 2013 R2
- Microsoft Dynamics NAV 2013
- Microsoft Dynamics NAV 2009 R2
They have also announced that the only compatible products are SQL Standard Edition and the SQL Enterprise Edition.
For more information regarding the product you can check out this link.
Receintly I had to create a communication with a company that would return an image after having received certain info.
Now, in order to store the image (wether in the disk or a BLOB field) we cannot just use the “save as” feature
What the web service did was generate the image file, code it into base64 and send the “translated” info. What does this mean? Well, it means receiving a string of text 4.000 characters long. Not as visual as expected…
But let us not lose hope! This rang a bell in my head. I could have sworn I had seen something similar previously in my collection. So after searching through the personal box of code and the internet (a line from here, a line from there…) what I discovered was this:
After having had time to play with the new merge cmdlets and having understood the way they work I must say I am quite happy with them.
The issue I’ve had with the new tools is the “feel” when using them. They are not “user-friendly” and I know that it is meant for developers and devs should be used to the powershell environment. Regardless of that I have built a completely free NAV module you can download here that gives that NAV feel we are all used to Let me know if you like it.
My opinion is that using these tools is really fast for the tasks they do, and they do them surprisingly well (I’ll confess, I was quite sceptical at first).
First of all I want to clarify that I have learned from this pattern from the big NAV specialist Waldo. All credit go to him.
So, in this post I want to get myself acquainted with this way of developing. It allows you to save a lot of time in the upgrading process and version changes. The name of this method is “Hooks Pattern”.
This system or methodology enables, when doing the merge (either manual or automatic) to decrease by a lot (over 50%) the invested time in merging the objects from the old version with the newer one keeping the customizations in them.
Today the official NAV team has published in their official blog the new Cumulative Update 9 for NAV2013R2.
In this CU9 we can find new cmdlets for Powershell and speed up the merge between versions or products. These utilities are prepared for different versions and not just NAV2013R2 but it is not compatible with dataports, forms oR section-based reports.
At this point I think it is known to all of us that the users have a tendency to leave Microsoft Dynamics NAV open even if they are not in need of using it. This might be due to a distraction and they start doing something else, or just because it’s coffee time
But the licenses have the user number very well defined and not all the companies can afford to have more sessions open than needed. This is specially true when external applications interact with the ERP in order for the system to run the company business logic.
But what can we do?