Incorrect rendering

Question

HiI currently use RDLC reports in local mode in my solutions, and I'm having some rendering issues with the ReportViewer component in versions 16.1.0.37 and 16.2.0.41.Here are the problems in order of severity for me (highest to lowest):1) The Print option generates a report with incorrect dimensions, which are always smaller than what is displayed in the preview. This can be easily seen in the available demos (screenshot attached).* The above problem is the most serious and is preventing me from allowing the Print option for my users.2) Reports with two columns are rendered with only one column. (Eg Lables)3) Elements with CanGrow = true are not rendered correctly and sometimes overlap adjacent elements.4) Export to PDF generates a result with a font different from that used in the original report. (screenshot attached)Please help,Thanks & Regards,Sérgio Sant'AnnaAttachment: SyncfusionReportViewerRendering_Issues_6a1801cc.zip

Yuvaraj Devarajan · Answer

Hi Sergio Sant'Anna, 

Thanks for contacting Syncfusion support.  





1) The Print option generates a report with incorrect dimensions, which are always smaller than what is displayed in the preview. This can be easily seen in the available demos (screenshot attached). 

* The above problem is the most serious and is preventing me from allowing the Print option for my users. 


On further analysis of the shared screenshot, the mentioned problem occurs when you customized the page setup value for printing. Our ReportViewer printlayout size is rendered based on the “page setup” value specified in ReportViewer or RDL report. If you have to render the report in particular print layout size then specify the page setup value in ReportViewer or RDL file as shown in below shared screenshot. 

  

  




2) Reports with two columns are rendered with only one column. (Eg Lables) 

We have tested the mentioned problem with our latest Essential studio build and its working properly at our end. So can you please share the screenshot of the CanGrow property issue and two columns issue or RDL report file to validate the mentioned problem at our end. 

   


3) Elements with CanGrow = true are not rendered correctly and sometimes overlap adjacent elements. 


4) Export to PDF generates a result with a font different from that used in the original report. (screenshot attached) 

We have support to render the default system font in the exported PDF file. So can you please share the font name specified in the report and it would be helpful for us to validate the mentioned problem at our end. 


Regards, 
Yuvaraj D.

Sergio Sant'Anna · Answer

Hello Yuvaraj,Thanks for the quick response. I made new tests following your guidelines with version 16.2.41 and below the results of each case:1) The Print option generates a report with incorrect dimensions, which are always smaller than what is displayed in the preview [...]:I reviewed my margins and I do not have a customized page setup, and even then the print output is always smaller than the one shown in the preview. As I mentioned, exactly the same happens in the Syncfusion demos.Could you provide an example that prints a report equal to that displayed in Reportviewer Preview? Or if you prefer, an orientation of how can I achieve this using the local syncfusion demos.2) Reports with two columns are rendered with only one column. (Eg Lables):The problem continues in the last ES version. I am sending my RDLC file attached for analysis.3) Elements with CanGrow = true are not rendered correctly and sometimes overlap adjacent elements:There was partial fix of the problem in the latest version of ES, and now CanGrow is correctly rendered in ReportViewer preview, Print and Export. However, there is still a problem with rendering in the browser (window displayed after clicking the print button) (Screenshots attached).4) Export to PDF generates a result with a different font from that used in the original report:The font in RDLC is Arial.Regards,Sérgio Sant'AnnaAttachment: SyncfusionReportViewerCanGrowIssue_5b93bcfa.zip

Mahendran Shanmugam · Answer

Hi Sergio Sant'Anna, 





I reviewed my margins and I do not have a customized page setup, and even then the print output is always smaller than the one shown in the preview. As I mentioned, exactly the same happens in the Syncfusion demos. 
 
Could you provide an example that prints a report equal to that displayed in Reportviewer Preview? Or if you prefer, an orientation of how can I achieve this using the local syncfusion demos. 


We can achieve your requirement with the help of setting the page setup for the report in online demo location as shown in below snap. In the shared snap, we have provided the value to render the ReportViewer in print layout as like the normal layout. 

  

Online sample location: https://aspnetcore.syncfusion.com/reportviewer/invoice. 



2) Reports with two columns are rendered with only one column. (Eg Lables): 

We have checked the mentioned problem with your shared report and it is working properly at our end. So can you please share the issue reproducible screen shot or video to validate the mentioned problem at our end.  


3) Elements with CanGrow = true are not rendered correctly and sometimes overlap adjacent elements: 

We have checked the mentioned problem with your shared RDLC and it is working properly at our end as shown in below screenshot. For your reference, we have prepared a sample and can you please whether the sample is working properly at your end, which can be downloaded from below location, 
Sample: http://www.syncfusion.com/downloads/support/directtrac/general/ze/ReportSample_core1330823103. 

  


Export to PDF generates a result with a different font from that used in the original report: 

The mentioned Arial font used in the report is not the default system font, hence the mentioned problem occur at your end. In our ReportViewer, we have support to load the Unicode font (TTF) file only when exporting to PDF format. So we request load the Unicode font (TTF) in WebAPI controller as shown in below code example, 
 




public void OnReportLoaded(ReportViewerOptions reportOption) 
        { 
            Assembly assembly = typeof(HomeController).GetTypeInfo().Assembly; 
            var resourceName = "ReportSample_core.wwwroot.ReportRDL.ARIALUNI.TTF"; 
 
            if (reportOption.ReportModel.PDFOptions == null) 
            { 
                reportOption.ReportModel.PDFOptions = new Syncfusion.ReportWriter.PDFOptions(); 
            } 
 
            if (reportOption.ReportModel.PDFOptions.Fonts == null) 
            { 
                reportOption.ReportModel.PDFOptions.Fonts = new Dictionary<string, Stream>(StringComparer.OrdinalIgnoreCase); 
            } 
 
            reportOption.ReportModel.PDFOptions.Fonts.Add("Arial", Assembly.GetExecutingAssembly().GetManifestResourceStream(resourceName)); 
        } 

We have prepared a sample and it can be downloaded from below location, 
Sample: http://www.syncfusion.com/downloads/support/directtrac/general/ze/ReportSample_core1330823103. 



Regards, 
Mahendran S.

Sergio Sant'Anna · Answer

Hello Mahendran,Thanks for the info and examples. Below are my considerations for each case:1) The Print option generates a report with incorrect dimensions, which are always smaller than what is displayed in the preview [...]:     Syncfusion: We can meet your requirement with the help of setting the setup page for the demo report online as shown in below snap. In the shared snap, we have provided the value to render the ReportViewer in print layout as normal layout.Maybe I did not understand and I apologize if I'm wrong. But I do not see the proposed fit as an effective solution to the problem that can be applied in a production environment.It looks like you had to make a few attempts until you found a page size that had a slightly better result, and for that, you also had to modify a report originally in Portrait to Landscape.As expected, currently the preview and export deliver similar results without any adjustment in Page Setup, why is this necessary for printing?Could you please provide some guidance or example where Preview, Exports and especially Browser Print Preview show similar results?2) Reports with two columns are rendered with only one column. (Eg Lables):               Syncfusion: We have checked the mentioned problem with your shared report and it is working properly at our end. So you can share the issue reproducible screen shot or video to validate the mentioned problem at our end.In the example sent (ReportSample_core1330823103), you used my 2 columns Mailing Labels.RDLC, however it is also generating a single column when I run here, as screenshot below:Anyway, looking at your screenshot of Issue # 3, it also came out with a single column for you. Could you please send your example that ran the 2 columns (side by side) for me to compare with my project?3) Elements with CanGrow = true are not rendered correctly and sometimes overlap adjacent elements:          Syncfusion: We have checked the mentioned problem with your shared RDLC and it is working properly at our end as shown in below screenshot.In my case, the problem occurs when I use elements with CanGrow = true inside a Page Header or Page Footer and only (again) in Browser Print Preview and PDF Export. To facilitate its analysis, the same RDLC modified with this behavior is attached.4) Export to PDF generates a result with a different font from that used in the original report:          Syncfusion: We have support to render the default system font in the exported PDF file. So you can share the font name specified in the report and it would be useful for us to validate the mentioned problem at our end.This solved the problem. Thank you.Thanks & Regards,Sérgio Sant'AnnaAttachment: Mailing_Labels_CanGrow_Issue_8de11262.zip

Mahendran Shanmugam · Answer

Hi Sergio Sant'Anna,  





Maybe I did not understand and I apologize if I'm wrong. But I do not see the proposed fit as an effective solution to the problem that can be applied in a production environment. 

It looks like you had to make a few attempts until you found a page size that had a slightly better result, and for that, you also had to modify a report originally in Portrait to Landscape. 

As expected, currently the preview and export deliver similar results without any adjustment in Page Setup, why is this necessary for printing? 

Could you please provide some guidance or example where Preview, Exports and especially Browser Print Preview show similar results? 


In RDL standard, we have two type of layout rendering one is normal layout and another one is print layout. In Normal layout rendering, it doesn’t consider the page setup sizes and print layout is rendered based on the page setup value. Hence the normal layout is different from the print layout. As per RDL standard, we cannot able to render the normal layout size for the print layout in ReportViewer.  




In the example sent (ReportSample_core1330823103), you used my 2 columns Mailing Labels.RDLC, however it is also generating a single column when I run here, as screenshot below: 



Anyway, looking at your screenshot of Issue # 3, it also came out with a single column for you. Could you please send your example that ran the 2 columns (side by side) for me to compare with my project? 


As of now we don’t have support for multiple column. So we have logged this as a feature request and it will be included in any of our upcoming Essential Studio release. 


In my case, the problem occurs when I use elements with CanGrow = true inside a Page Header or Page Footer and only (again) in Browser Print Preview and PDF Export. To facilitate its analysis, the same RDLC modified with this behavior is attached. 




We were able to reproduce the mentioned problem with your shared RDL file at our end. We have confirmed that the issue is a defect and logged a defect report on this. The fix for the issue is estimated to be available on our upcoming essential studio release. 

Regards, 
Mahendran S.

Sergio Sant'Anna · Answer

Hi Mahendran,Thanks for the information and problems identified, we will wait for the fixes of issues #2 and #3.Regarding issue #1, I guess I did not express myself correctly. The problem does not relate to the differences between Print Layout and Normal Layout.The screenshot below shows more clearly the problem that also occurs in your demos, where the report output for printing has smaller dimensions (red rectangles).This is exactly the problem I'm reporting and occurs regardless of whether the rendering of the layout is Print or Normal.Is this a problem that we should wait to fix or is there any solution?Thanks & Regards,Sérgio Sant'Anna

Yuvaraj Devarajan · Answer

Hi Sergio Sant'Anna, 

We have checked the mentioned problem by directly printing our online demo sample and its working properly at our end as shown in shared screenshot. We suspect the mentioned problem might be occured when you have specified the customized margin setting at your end. So can you please ensure whether we have specified any custom value for the margin in print preview setting as shown in below screenshot, 
  

  
Working Screenshot: 
  

If the issue still persists, then share your browser culture and version detail to validate the mentioned problem at our end.  

Regards, 
Yuvaraj D.

Sergio Sant'Anna · Answer

Hello Yuvaraj,I was able to determine that the problem #1 in my end was with my Chrome Browser.Unfortunately I could not find exactly what was causing this behavior, like some configuration or browser extension. I made several changes in the browser, comparing to another computer with the same version that worked ok, but I was not successful in reproducing the problem.The issue was resolved by reinstalling Chrome in my end.Thanks for your help,Sérgio Sant'Anna

Anandakumar S · Answer

Hi Sergio,We are happy to hear that your problem has been solved. Please let us know if you need further assistance.Regards,Anandakumar S

1) The Print option generates a report with incorrect dimensions, which are always smaller than what is displayed in the preview. This can be easily seen in the available demos (screenshot attached). * The above problem is the most serious and is preventing me from allowing the Print option for my users.	On further analysis of the shared screenshot, the mentioned problem occurs when you customized the page setup value for printing. Our ReportViewer printlayout size is rendered based on the “page setup” value specified in ReportViewer or RDL report. If you have to render the report in particular print layout size then specify the page setup value in ReportViewer or RDL file as shown in below shared screenshot.
2) Reports with two columns are rendered with only one column. (Eg Lables)	We have tested the mentioned problem with our latest Essential studio build and its working properly at our end. So can you please share the screenshot of the CanGrow property issue and two columns issue or RDL report file to validate the mentioned problem at our end.
3) Elements with CanGrow = true are not rendered correctly and sometimes overlap adjacent elements.
4) Export to PDF generates a result with a font different from that used in the original report. (screenshot attached)	We have support to render the default system font in the exported PDF file. So can you please share the font name specified in the report and it would be helpful for us to validate the mentioned problem at our end.

Maybe I did not understand and I apologize if I'm wrong. But I do not see the proposed fit as an effective solution to the problem that can be applied in a production environment. It looks like you had to make a few attempts until you found a page size that had a slightly better result, and for that, you also had to modify a report originally in Portrait to Landscape. As expected, currently the preview and export deliver similar results without any adjustment in Page Setup, why is this necessary for printing? Could you please provide some guidance or example where Preview, Exports and especially Browser Print Preview show similar results?	In RDL standard, we have two type of layout rendering one is normal layout and another one is print layout. In Normal layout rendering, it doesn’t consider the page setup sizes and print layout is rendered based on the page setup value. Hence the normal layout is different from the print layout. As per RDL standard, we cannot able to render the normal layout size for the print layout in ReportViewer.
In the example sent (ReportSample_core1330823103), you used my 2 columns Mailing Labels.RDLC, however it is also generating a single column when I run here, as screenshot below: Anyway, looking at your screenshot of Issue # 3, it also came out with a single column for you. Could you please send your example that ran the 2 columns (side by side) for me to compare with my project?	As of now we don’t have support for multiple column. So we have logged this as a feature request and it will be included in any of our upcoming Essential Studio release.
In my case, the problem occurs when I use elements with CanGrow = true inside a Page Header or Page Footer and only (again) in Browser Print Preview and PDF Export. To facilitate its analysis, the same RDLC modified with this behavior is attached.	We were able to reproduce the mentioned problem with your shared RDL file at our end. We have confirmed that the issue is a defect and logged a defect report on this. The fix for the issue is estimated to be available on our upcoming essential studio release.