clausl: Fixing Inventory Valuation report

[Blog bot]

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 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 fix after the rules in UX Guidelines. In the UX Guidelines it is outlined that cell padding should be:

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

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

Padding
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, 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 make  search and replace the following:

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

and

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

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, Abakion.com & Supplychainshop.com



Читать дальше