With the introduction of the new Role Tailored Client a few years ago, we gained a lot of things and were able to include many new and exciting features. The RTC client has as an advantage that no matter what type of screen the page is being shown in, it will resize itself to present a usable user interface, among others.
However, with the changes the new client brought, some sacrifices had to be made. Among those sacrificies we lost the ability to define colors, sizes, positions, etc of the different elements that make a form/page.
Lately I’ve been asked to check issues regarding the relation between the license and the objects contained within the system where the license is installed.
This can happen for many reasons, let it be because the client has been working with a partner’s license while the client’s license was being prepared, or let it be because there is a mandatory update that needs to be applied and the client’s license has not been updated.
Be as it may, since I’ve been asked many times the last few weeks, I wanted to write about it.
I have faced this error testing some updates I’m preparing for the automatic merging tool I did and Dynamics NAV came up with this error when I was trying to upload a 120MB file. Too large for NAV apparently.
In my case I was using NAV2013R2 at the time.
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.
As all of you know, with the release of Microsoft Dynamics NAV 2015 some improvements and featuresd were introduced. Both technical and functional.
One of these improvements is the ability of having a tablet client, which unlike the webclient is very responsive and fast and is thought to be used on mobile devices of certain characteristics (minimum resolution, Windows based OS, etc).
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: