How to implement carryover in Wordlayout reports

Since Wordlayout has been introduced with NAV 2015, many have tried to implement Transheader/-footer functionality from classic report layout into Word and many have failed. For a long time, the only possible approach seemed to be that, with a fixed number of lines per page layout. But now, I found another, much simpler way for arbitrary layout, and I will show you, how this can be accomplished for a sample report, namely report 1306 “Mini Sales – Invoice” of NAV 2016…Read More »

Wordlayout+ and Rich Text Content Controls

As mentioned in my previous post, the full functionality of Rich Text Content Controls (RTCC) is now available with Wordlayout+. In standard Wordlayout, RTCC could also be used, in fact, but more or less only in the same way as plain text content controls. RTCC offer almost unlimited possibilities, because the content of a RTCC can be rather anything (except other RTCC), for example text lines, pictures, tables and whole Word documents. Indeed, the content of an RTCC is stored as a small Word document in Flat Open XML format (see for example

I will give you now an exciting example, about the possibilities of RTCC with Wordlayout+…Read More »


Sooner than expected, the next step in NAV reporting is available and I have called it Wordlayout+, because it extends the standard Wordlayout capabilities of NAV 2016. Especially the following features have been implemented:

  • Nested Groups (Customer -> SalesHeader -> SalesLines, e. g.)
  • Improved image handling (empty image is displayed as empyt, image size is retained)
  • Manual line breaks within plain text controls (“Allow multiple paragraphs” works now)
  • Repeating Sections around arbitrary paragraphs, table rows or even whole tables (standard NAV works only for one table row)
  • Formatted output for Rich Text Controls works now
  • Optionally blank zero values

How is it implemented?Read More »

Wordlayout revisited

I remember well, when Wordlayout was introduced in NAV 2015 and everyone got excited and hoped, that designing reports for NAV would now become more easy and efficient. But the excitement soon calmed down, when from the first experiments with the new functionality, it became evident, that there are quite many things, which won’t work as expected, like for example nested repeaters. Besides, there seemed to be some bugs, which still persist to version NAV 2016. For those reasons other third party report building solutions came into play, which offered quite intuitive report design capabilities for NAV. And so, today, a serious NAV report developer tends to wave aside, if someone suggests to use Wordlayout as an alternative to RDLC. But Wordlayout functionality is quite wrongly refused, as I will try to demonstrate in this article…Read More »