I remember having seen this a while ago somewhere inside NAV but a colleague reminded me of this recently and I thought it’d make for a good post
Let’s get to it.
So yes, there is a way to accomplish this.
As most of us know by now, there are some variables within an object that are predefined for us by the system. Some of this variables can be “CurrPage”, “Rec” or “xRec”.
Well, there is another one a lot of us don’t keep in mind all the time. This variable is named: CurrFieldNo
For the last few days I have been working more than usual with Dynamics NAV Webservices in order to make available the business logic to the outside world and allow for external connections. And to do so I needed a trustworthy testing tool.
In my case I have used Soap UI in the past and have had good experiences. So I wanted to create this entry detailing how to test a webservice with this tool
To demonstrate this I have decided to create a new codeunit that has one function alone named “PrintPDFInvoice”. This function prints a PDF of a specific invoice and leaves it in a specific folder.
Before I start, I must say I first read about this on the following Kauffmann’s blog entry. So all kudos to him When I read it I found it really interesting and used it on some of the tools we use internally. So this post will be pretty much my experience with what Kauffmann knowledge
Having said that, let’s get to it!
The RecordRef variables are, for many of the developers within the Dynamics NAV community, unknown.
The number of times on which this kind of variables is useful is very limited, and therefore it does not promote its usage or knowledge.
In this post I do not seek to describe them, or how they are used. I might save this for a future entry
Recently I found myself needing to execute a page whose ID was dynamic, and the table was dynamic as well.
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.
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/
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:
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?