Jet Express for Word - Some Notes
2014-11-27 17:38

Those who have been working with the Word layout Reporting feature might have heard of the Word add-in called Jet Express for Word. The essence of this add-in is that "... your fields appear in clear text and the search feature makes it quick to add the fields you need", as Jet puts it on their website.

As it's freely available (so at no cost) download it and be happy with it. However I find myself using both Jet Express for Word and the Word XML Mapping pane as the have both their pros and cons. Let me list what I think as pros and cons.


XML Mapping pane

  • When you have inserted a Content Control the focus will (still) be on the layout document, so when you use the arrows it will allows you to move inside the layout and not in the XML Mapping pane Idea
  • If your layout already contains content controls you can easily assign an item in the mapping pane by using the Map to Selected Content Control; love it Right Hug

Jet Express for Word pane

  • Adding a content control of an item in the mapping list to the layout can easily be done by double clicking on the item in the list; this is really great Yes


XML Mapping pane

  • Adding a content control of an item in the mapping list is a bit more laborious as you need to right click it and select on the context menu Insert Content Control > Plain Text; this a quite a pain in the ... Super Angry

Jet Express for Word pane

  • When you have inserted a Content Control the focus will not be on the layout document, so when you use the arrows it will move your 'cursor' to another entry in the Jet Express for Word pane; I find this very annoying Broken Heart
  • There is no Map to Selected Content Control feature here Storm
  • One major annoying thing about Jet Express for Word is that the pane will always show up when open a Word layout for editing in Word; there seems to be no way of hiding it initially Ick!

I guess it's clear there is no winner here. Hopefully either Jet or Microsoft provides us with some improvements here.

by Luc van Vugt | with no comments
Filed under: , ,
Why is the Repeater in my WORD Layout not Showing Data?
2014-11-27 15:47

Being a Word user from way back 1987 I felt immediately at home when the NAV Core Team did present us MVPs already months ago the Document Reporting feature. I think it's really a great feature. Indeed it has it's restrictions, but it's so easy to use, which is exactly the reason why it has landed in the product. Given a useful dataset definition you will have in no time created the layout. However you might run into the following as I did.

Preparing for a training on the new Document Reporting feature in NAV 2015 I was playing around with various layouts. Pimping built-in ones, using some templates from and starting from scratch. A couple of times I ran into the issue that the repeater placed on the detail lines of my layout did not show data.

And clearly I had placed a repeater on the table row following the header row of the details:

So why is the Repeater in my WORD Layout not Showing Data? To be honest I do not know. Even Reporting Torben could not tell me exactly. Nevertheless I found out how to fix it or prevent it from happening.

Make sure when inserting the repeater to have a table row above and below it (see the orange colored rows below):



Now it works and just remove the (orange colored) empty rows.

by Luc van Vugt | with no comments
Filed under: , , ,
Let's clean up NAV #5 - Torn Page Detection
2014-11-18 8:23

Join the Clean Team! Geeked

Welcome to my fellow MVP Alain Krikilion, aka Kriki, who also clearly wants to clean up as you can read below. Let's kriki up NAV!

In the database properties of NAV, on the Options tab, there is the toggle Torn Page Detection.

In SQL2000 this option was introduced to have some mechanism to detect if a page was 'torn'.

What is behind it?

A page in SQL is approx. 8KB. But the default disk-cluster in Windows is 4 KB. So when you write a SQL page to disk, you write it in 2 disk-clusters. If the first cluster is written well, but the second not because of some problem, you have a torn-page.

In a later version of SQL Server, the Checksum was introduced. SQL Server calculates this checksum, when a SQL-page is written to disk, and writes it together with the data in the page. Now when SQL server reads that page, it calculates the checksum and confronts it with the checksum found in the page. If they differ, SQL knows the page is corrupt.

In the beginning, it was feared that it could have a performance impact, but that proved to be wrong (luckily). So the default has become Checksum and you don't need the possibility in NAV to change that as there is no reason to do it!

So lets get rid of Torn Page Detection.

Let's clean up NAV #4 - SYSTEM Functions
2014-11-16 15:51

Once I start to clean up ... I can't stop I guess. So here's more that still resides in C/SIDE and has become totally obsolete (the following table is an excerpt from Changes in C/AL Behavior and Support from Earlier Versions of Microsoft Dynamics NAV):




Not supported in Microsoft Dynamics NAV 2015.


Not supported in Microsoft Dynamics NAV 2015.


Not supported in Microsoft Dynamics NAV 2015. Use the finsql.exe executable with the ExportObjects command instead. For more information, see ExportObjects.


Not supported in Microsoft Dynamics NAV 2015. Use the finsql.exe executable with the ImportObjects command instead. For more information, see ImportObjects.


Obsolete in Microsoft Dynamics NAV 2015, but still supported. This function always returns true.


Not supported in Microsoft Dynamics NAV 2015.


Not supported in Microsoft Dynamics NAV 2015.


Not supported in Microsoft Dynamics NAV 2015.


Not supported in Microsoft Dynamics NAV 2015.


Not supported on Microsoft Dynamics NAV Server.

So if it is not supported why still have it? Let's clean up the ... Geeked

Let's clean up NAV #3 - AltSearchField
2014-11-13 21:12

With RTC all of a sudden, so it seemed to many, AltSearchField was not working anymore. Complaints abundant as probably the same 'many' hadn't learned about the new dropdown list yet. You know that list defined by the FieldGroup property on a table.

Meanwhile this dropdown list has become a common feature that provides the user with even a more powerful way of searching the correct data than AltSearchField did provide. And still AltSearchField is to be found in C/SIDE as a table property including the data that it was populated with in the past. However, totally obsolete now and a next candidate to be cleaned out!

'Vedbaek, go ahead. Clean it out!'

The Word layout document is malformed - Misleading Message #2
2014-11-7 11:54

I guess this error message can make sense for sure, but not with what I was doing today.

I mean, working with the new document reporting feature in NAV 2015, this perfectly would made sense importing a Word layout, that has just been updated, but in such a way that is ended up to be malformed.

But this wasn't what I was doing. At least that's what I thought and also proved to be so.

What did I do to get here?

From C/SIDE I had exported the Word layout of REP1306. Opened it in Word and pimped it nicely, just to get some feeling of it. Saved the Word document. Returned to C/SIDE and imported it again. And ... ran into this message. Hmm

Long story short: I indeed had saved the Word layout, but had not closed the file. I.e. the file was still open in Word.

Document malformed?

Let's clean up NAV #2 - Form Designer
2014-11-7 11:48

Of course after my post How-to: Design a Form in NAV 2015 this one is obvious, ain't it? Just for the counter to increment: #2.

Need to say more?

by Luc van Vugt | with no comments
Filed under: , , ,
Let's clean up NAV #1 - URL and SAVEASHTML
2014-11-6 17:13

As Mark started to set the pace, I am following up on this with my list of small enhancements that could easily be picked up in the next release. Let's clean up NAV from obsolete remnants. I just call this post #1 even though I am totally unaware how many more will follow.

So here we go: 'Houston' ... uhhh ... 'Vedbeak' let's get rid of the obsolete report property URL and function SAVEASHTML.

For those who agree, give your vote here.

One or more projects in the solution were not loaded correctly
2014-11-5 13:02

Last week performing a NAV 2013 update training, I was confronted with the above message when opening the layout from C/SIDE in Visual Studio 2013. "Ouch", I thought, "apparently trusting too much on my installation to work well. Should have checked." Surely after my laptop re-install some weeks ago. Hmm

"OK, let's click OK and see," I said to myself, crossing fingers. Luckily Visual Studio opened up showing me the layout of the report and indeed a useful message in the output window:

Typically a case of my stringiness when installing Visual Studio (or in general any other software package): always trying to get away with a minimal install. I had unchecked all optional features.

Let's check the Web Developer Tools and update the installation.

How-to: Design a Form in NAV 2015
2014-10-30 13:54

Don't believe you can? Have a look at this picture story ... Cool

Finding NAV 2015 MSDN Help - Let's Hope It Improves
2014-10-26 12:39

For ages Help has been the laughingstock of NAV. Many where evading the creation of it, even more were mocking about the content. For various reasons.

With NAV 2009 MS has picked up this gauntlet in various ways: creating better and more valuable content, putting it online, providing us with easier to use tools, not in the least the help server that was released last year. Now with the release of NAV 2015 the next version of standard help has been put online. But it appears that it's still showing up in search queries as dominant as it used to be for previous versions.

If you now do a search for NAV ShowMandory the msdn topic on ShowMandatory will only show as last entry on the first page (and guess what's the top 3 shown?). But ... it is improving. The search results were even worse some weeks ago.

Searching for NAV AccessByPermission will not even yield an msdn result! Not even on msdn itself.

Informing myself on this with one of my former MS colleagues I found I surely was not the only one experiencing this and that the issue has been escalated to the msdn team.

Let's hope it improves the coming weeks.

Running Help Servers Side-By-Side
2014-10-24 11:24

Digging myself into the new features in NAV 2015 I was referencing the Help and found myself looking at default page. My first thought was: Isn't there any help for this field?

So I returned to the page and selected the upper left dropdown arrow (forgotten the term for it), Help, Microsoft Dynamkics NAV Help to see if there wasn't any help for the page. Nope. Same topic shown.

Now looking a bit more closely I saw I wasn't looking at 2015 help at all.

Didn't I install the NAV 2015 Help Server?

Well, apparently I had and it was running also.

But ... it was running on the same port as the NAV 2013 R2 Help Server: 49000. My recent installation of both NAV 2013 R2 and NAV 2015 came to mind. I had set different ports for the service tier, but had totally neglected the Help Server and thus had both set on the same port. (Note that there as a useful post on this by my fellow MVP Saurav Dhyani.)

Piece of cake to change the port, I thought. Well, now looking in retrospect, it is, but it took me some while before I got it running and even spammed one of my former MS colleagues with it. Once more my apology for that. Embarrassed

I guess you figured out that I knew the Help Server as an IIS service. But not being a regular user of the IIS Manager, it's like "wow, there is a lot to configure". Surely if you only look at the middle pane (Feature View) and start browsing around there. Don't, I can tell you now.

Have a look at the right pane and click on Bindings .... Now writing this I can't recall anymore how I got to click on that; nevertheless, that's where to go.

I added a binding for port 48000, deleted the one for 49000 (and left that to the Help Server for NAV 2013 R2) and (re)started the service.

Time to return to NAV 2015 and ... No, no, not yet. As the referencing of the help is handled by the service tier there another thing to do.

Stop service, change the Help Server Port to the right one, i.e. 48000 in our case, and restart the service.

Back to my NAV 2015 windows client and click F1 again.

.......... Shooot. Should have thought of this. At least should have better read Saurav's post.

There is a third part in this: the user settings the be found in ClientUserSettings.config which typically resides in C:\Users\<user>\AppData\Roaming\Microsoft\Microsoft Dynamics NAV\80.

Change 49000 to 48000, save, restart my NAV 2015 windows client, and click F1.

NAV 2015 Glance 4: New Functions are Local by Default?
2014-10-17 14:51

It is considered a general coding best practice to declare a function as being local. Over time you could see that the NAV Team was also adhering this, even though C/SIDE wasn't helping a lot on this a a new functions would by default be global, i.e. the property Local would be <No> (or you might say undefined). Now with NAV 2015 any new function will get Local=Yes.

Well, that's not always true I found out today by accident when writing my previous post. It appears to be depending on the Subtype of the codeunit.

If Subtype is ...

  • Normal (or undefined, i.e. <Normal>) functions will be local by default
  • Test functions by default be global test functions (i.e. FunctionType=Test)
  • TestRunner we get the same behavior as for Subtype Normal
  • Upgrade functions will default to local upgrade functions (i.e. FunctionType=Upgrade)
by Luc van Vugt | with no comments
Filed under: , ,
Did You Have a Look at the C/AL Editor Status Bar Today?
2014-10-17 14:50

Well, I did and noticed something that has been there apparently for some time ... Huh?

... a year or so, since NAV 2013 R2. I surely had noticed that since then the C/AL editor shows the attributes. A simple but valuable feature that makes my live a lot easier.

So, no, this is not what I wanted to address here - I recon you did read the title. Cool

Have a look:

Maybe a bit to much. And now?

The first part ... wasn't there before NAV 2013 R2. You can now easily see in what function you are, on what line and column.

Or ...

... did you notice and I am just wasting your time? Geeked

This license is not compatible with this version of Microsoft Dynamics NAV - Misleading Message #1
2014-10-3 14:00

So today I sat down to get things prepared for my session at Directions EMEA 2014, next week. Not in the least because this week I had to install a new laptop, hence having to let go of everything that was there and proofed working alright at Directions US. Indeed somewhat tricky. Hmm

Luckily everything got installed well and working, earlier on this week. Nothing really to worry about. NAV 2015 RTM NL was running and now I wanted to get a W1 database to put my things in. Having the W1 DVD at hand only a matter of restoring the Demo Database NAV (8-0).bak file, and renaming the database name and file names. This in order to discriminate between the various country versions (which MS be default always name Demo Database NAV (version)) and projects I am using c.q. working on. Therefor I decided to call my database: Demo Database NAV (8-0) - Directions EMEA, likewise I had done for Directions US.

Connected my NAV 2015 Development client and service tier to this database. And ... couldn't get the the windows client work. Quite fast I realised I had to get some things set on the account that is running my service tier: NT AUTHORITY\NETWORK SERVICE.

  • map it to this database and
  • mark the dd_datareader, db_datawriter and db_ddladmin roles

Restart the service and ...

... open the windows client again, I wanted to say.

Holy cow. My license not compatible? My mind started running, trying to unnerve myself.

  • Got one from MS before Directions US and was working right ... then ... two weeks ago
  • Did work last Tuesday when I had reinstalled everything on the new laptop
  • By all means, it worked this morning

Upload the license to the database? Nope, no use. Ask MS for a license update? Might, but will take too much time. Would it work with the other NAV 2015 databases on my SQL Server (see screen shot)? Yes, it does! With the same license!

Am I being fooled somehow? Well, it seems to be.

I recon that, when I named my database Demo Database NAV (8-0) - Directions EMEA, your mind was triggered. Mine was somehow, but I decided to disregard it. I shouldn't.

Once I had changed the name to Demo Database NAV (8-0) D-EMEA everything worked fine.

What the ****, "this license is not compatible with this version of Microsoft Dynamics NAV"?

A to-the-point message would have made it surely easier for me, mister MS.

BTW: Should the name be less than 30 characters? Is that the rule? No, time to figure that out now.

Added 2014-10-07

For those who would like NAV to be enhanced to get a meaningful message, please vote on msconnect: go here

More Posts Next page »

Recent Posts


Email Notifications

This Blog


Favorite BLOGS


Team Foundation Server BLOGS