A quick review of NAV 2017 reveals, that concerning Wordlayout reports nothing essential has been improved.
Still there seems to be no possibility to use repeating section content controls except for single table rows and they can’t be nested. Rich text controls for dynamic content, formatted text or images are still not supported.
But the empty image problem has been resolved: If images are printed within repeating table rows, an empty image is printed as blank and not with the picture of the last non empty image.
Finally, Wordlayout+ remains the state of the art for NAV 2017.
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 »
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 https://blogs.msdn.microsoft.com/ericwhite/2008/09/29/the-flat-opc-format/)
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 »
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 »
Recently, I was wondering about the order in which the three sections of a RDLC report, namely header, body and footer, are being rendered. Searching the net, I found this remarkable answer for the question about the rendering order, which is now about 5 years old, but seems still to be valid…
Read More »
As is well known, the Transheader-/Transfooter functionality of the classic client report generator in NAV versions 2009 or earlier is no more available for the RTC client. Furthermore there seems to be not a single carryover line in standard NAV report layouts, anymore.
Because some customers using Dynamics NAV RTC client still attach importance to carryover lines, especially in document type reports like invoices, I tried to find a most easy, general and elegant method of implementing this feature into RDLC report layouts of version NAV 2013 R2 or higher, …
Read More »
From the beginning I was not very satisfied with this Getdata-Setdata mechanism, which is proclaimed the standard way of displaying field values from the report body in the report header or footer of a NAV RDLC report layout. So I tried to find a more elegant way to accomplish this problem.
Read More »