As probably most of you, I'm quite an enthusiast when it comes to the possibility of running NAV2015 on any device by using the new apps.
As you may have read in the what’s new blogs on the latest NAV version, everything is routed via the web client by using the tablet.aspx page. There was however one challenge.. I’m not an IIS expert! And how do you set up your webclient to work with SSL/HTTPS?
Thanks to MVP Arend-Jan Kauffmann (@ajkauffmann), I got this How-to: http://msdn.microsoft.com/en-us/library/hh167264%28v=nav.71%29.aspx
It brought me a long way, but when restarting the webclient website, I received the following error:
The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)
After some more advance google-ing, I found out that there was probably another process that was also using TCP port 443 on my machine. It turned out to be Skype that was preventing the correct starting of the website. After closing Skype, the website started as expected.
Again, just something to keep in mind when working with the NAV2015 apps.
This is probably one of those things all experienced RDLC report developers know since day one. But since I couldn't find it when "googleing" or "binging", it is still something that can make your live a bit easier.
When right-aligning a text on a report, (i.e. a header for a decimal column) you may have noticed that when using just the label that NAV provides through your dataset as value, the words in a tekst are not properly quite aligned.
The value of your control could be:
With this as a result:
This of course is because there is still al space in the text and the report puts that before the line break.
When simply adding a little code to you value expression:
This will be the result:
This code can also be found in several standard NAV reports, you just need to know where to look for it.
As some of you may have noticed, I've not been very active on my blog the last year. There were a couple of reasons for that, the main reason was a lack of time. Some big projects kept me from thinking of cool new subjects for my blog. But I will try to get to it on a regular basis in the near future.
My writers' block was interrupted by an e-mail I received last month.
'Some' time ago (13-June-2012) I posted a suggestion to Microsoft Connect. This was the main idea:
To speed up the process of setting up users, it would help if there was a page-part or link from page 9807 "User Card" to the corresponding "User Setup" record for this user (Table 91). If created an application administrator would have all user info available in one single view.
After a while I even forgot I ever posted it. That was until I received an e-mail from Microsoft that my suggestion "will be considered for future release".
That took a while just to 'consider'.... You can find the original suggestion here.
But in short: all suggestions on MS Connect are useful, sometimes it just takes a while for them to become reality. So keep those suggestions coming!
A couple of weeks ago I ran into a problem with Microsoft Dynamics NAV 2013 in combination with Remote Desktop Clients. I also found a blog describing the problem I found:
In short, when printing reports via an RDP session using a wide-screen resolution. All fonts got squished. We didn't see anything wrong while using the preview function, but when really printing the reports, everything looked distorted.
Well, as I said.. I found the blog post by Mark H I mentioned above, but I didn't quite like the possible solutions. Since one of our customers had a serious problem with this bug I contacted Microsoft.
To my surprise MS was fully aware of the problem but at the time they only had the following solutions:
It may be clear to all of you that the second option is nice for new customers but personally I can imagine the reaction of existing customers when you'll propose it. ("Who is going to pay for this update?") Server side printing on the other hand is not a complete solution, because this only works for batch printing via the job queue.
The problem for the issue as my MS contact stated was actually not in NAV, but in SQL server and/or Windows 2008. This seems logical since Windows 2012 does not have this problem. They told me that they would escalate the issue to the SQL department.
A couple of weeks passed, and I got a few updates that they were still working on the problem. Then, last Wednesday, I got an e-mail that they found a solution!! The complete description can be found in the following KB article: http://support.microsoft.com/kb/2768741
At the moment we are testing the update, and until now everything looks ok on our development environment. Next test will be on our customer environment. So this looks a bit early to be very cheerful, but I didn't want to keep this possible solution to myself.
Note: Much thanks to Lars Lohndorf-Larsen, Duilio Tacconi and the MS Development team for their support!
As most of you've noticed, Microsoft has (finally) decided to lengthen most of the text fields from 30 to 50 characters.
To my regret, I must say that the MS Dynamics NAV development team made at least a few mistakes here. When you open the global variables window in page 291 and 296 you will see what I mean.
Yep, your eyes are not deceiving you.. the "Description2" variable is still 30 characters. Off course this doesn't have to be a problem if the function that fills the variable is also using a 30 character parameter. But well, since a picture says more than a thousand words:
As you can see the parameter is 50 characters so here we've got a potential overflow error. We've already reported this issue at Microsoft and they've told us that it will be fixed in a future service pack. But for now as they told us:
"From the current release perspective, please go ahead and increase length of Description2 global variable (page 291 and 296) to 50 chars. This will make it consistent with the parameter that sets value here."
Just so you all know.. nobody's perfect.