Transfooter and Transheader warning

Last week I did another RDCL Report Training class, this time in UK. In this class we stumbled over an issue, I had never seen before, while we where implementing Transfooter and Transheader functionality in a report. You might never encounter this issue, but to save you the headache I got solving this issue, here is the solution or bug you might call it.

You might remember the Transfooter and Transheader solution I blogged about a few years ago here: This solution also works perfectly in NAV 2013 and Visual Studio 2010. I have upgraded the report to NAV 2013 and made some layout changes to it. You can download the new version here from my SkyDrive:

But back to the problem. While we were adding Transfooter and Transheader functionality to the report, we also played around with the LeftIndent property on the textbox that feeds information to Transfooter Text box in the Page Footer. In the above demo report this would be Text Box “Customer__Debit_Amount_”.
When i.e. setting the LeftIndent property to 5pt to this specific Text box, we suddenly got and error in the Transfooter Text Box:


Why that is, I have no clue, but I have stopped using LeftIndent, since I no longer trust that property.

If you have an idea why the Transfooter Text box gives an error when using LeftIndent, I would love to hear. If not I will just park this as yet another bug in Visual Studio.

/Thanks, Claus Lundstrøm, &

Fixing Inventory Valuation report

When running Inventory Valuation report you might have experience that the data in this report is not visible in Print Preview like this:


Inventory Valuation is not the only standard report with this problem. I.e. you will also see this problem in the Account Schedule in the NA(North America) version.

Easy workaround is of course to click the “Print Layout” button, if this is visible of course, and the report looks like this:


But in this blog post I want to fix the report so the report also shows all the data in “Print Preview” and not just “Print Layout”

The fix is easy, and it is clear that this report was not completely fixed after the rules in UX Guidelines. In the UX Guidelines it is outlined that cell padding should be:

Left: 5pt
Right: 5pt
Top: 0pt
Bottom: 0pt

but the cell padding is the default values in this report:

Left: 2pt
Right: 2pt
Top: 2pt
Bottom: 2pt

I don’t want to mess with the report to much so the only thing I will change is the Top and Bottom padding in this report, and which is not needed in this report. 
So I will change both Top and Bottom padding to 0pt.

You have 2 options for making these changes:

Option 1. Export the report as txt and search and replace the following:

Replace <PaddingTop>2pt</PaddingTop> with <PaddingTop>0pt</PaddingTop>


Replace <PaddingBottom>2pt</PaddingBottom> with <PaddingBottom>0pt</PaddingBottom>

and then of course import the txt file again.

Option 2. Make the changes in Visual Studio by right clicking on the Report.rdlc in the Solution Explorer and select Open With / XML (Text) Editor, and do the same search and replace as above.

Save, compile and run you’re the report, and the report now looks like this in Print Preview with all data shown:


It would of course be nice if the NAV team would fix this. It only takes 2 minutes to fix Smile

Or request the SSRS team to fix the Report Viewer so it shows the data just like in Print Layout. This would of course not be a 2 min. fix, and this issue would not be on my top priority list for things the SSRS team should fix, If had the luxury of prioritizing what they should fix.

I dedicate this blog post to Kamil Sacek

/Thanks, Claus Lundstrøm, &