There seems to be a bug with the latest 13.2 reporting dlls.
This exception is now thrown for code that previously worked fine:
"The page number is bigger than the totally page count in the sections.
Parameter name: pageNumber"
A converter is used in a footer for the page number but even commenting that out the error is still thrown when the preview is called:
xamPreview.GeneratePreview(report, false, true);
Any ideas?
Hi,
I have been looking into your post and it seems that you use our WPF Reporting. I tested the reported method with the latest ServiceRelease for our WPF controls(13.2.20132.2005) and it seems that everything goes right. I am attaching the sample application(WPFReportingIssue.zip) that I have used for my tests.
Could please try to modify it in order to reproduce the use that you are having ?
Looking forward to hearing from you.
I am not able to recreate it easily with an example...it only happens after several pages of a many page report. Each page with a header and footer and a section (UIElement) on each page. For me it occurs at page 3 of an 8 page report. There is pagination event checking to get grids formatted just so. So it is quite complex.
There are also lots of page variables that appear with that in the report object fed to the preview... Logical/physical etc so I can't readily see an obvious mismatch. It seems to go through the page number converter multiple times even tho its only on the footer per page. Totally worked fine with previous version. Can you please check what changes you made around that specific error message? In the meantime I will keep trying to recreate it with the sample.
Thank you for your reply. I am glad that everything works as you expect now.
Thanks Yanko! We tried with the new dlls downloaded today and it seems to have done the trick..works fine again for many pages! I appreciate your help.
Hello,
Thank you for your reply. It seems that we have similar issues submitted in our internal system. I believe that they are fixed in our latest Service Release for WPF 13.2 that we have shipped out today.
You can download it going to our web site -> Account -> Select you product -> Service Release Tab.
Please let me know, if you reproduce your issue after installing the latest Service Release.
Here is the stacktrace from the generatepreview onward:
at Infragistics.Windows.Reporting.Report.Paginator.GetPage(Int32 pageNumber)
at System.Windows.Xps.Serialization.Toolbox.GetPage(DocumentPaginator paginator, Int32 index)
at System.Windows.Xps.Serialization.DocumentPaginatorSerializer.PersistObjectData(SerializableObjectContext serializableObjectContext)
at System.Windows.Xps.Serialization.DocumentPaginatorSerializer.SerializeObject(Object serializedObject)
at System.Windows.Xps.Serialization.XpsSerializationManager.SaveAsXaml(Object serializedObject)
at System.Windows.Xps.XpsDocumentWriter.SaveAsXaml(Object serializedObject, Boolean isSync)
at System.Windows.Xps.XpsDocumentWriter.Write(DocumentPaginator documentPaginator, PrintTicket printTicket)
at Infragistics.Windows.Reporting.Report.ProcessXpsDocumentWriter(XpsDocumentWriter writer, PrintTicket printTicket, PrintQueue printQueue)
at Infragistics.Windows.Reporting.Report.GenerateReport(Object reportObject)
at Infragistics.Windows.Reporting.Report.ExportToXPS(Stream stream)
at Infragistics.Windows.Reporting.Report.Export(OutputFormat outputFormat, Stream stream)
at Infragistics.Windows.Reporting.XamReportPreview.GeneratePreview(Report report, Boolean showPrintDialog, Boolean showReportProgressControl)
I am experiencing some issues with the report GeneratePreview
1, When I try to add two sections to a report where the first section XamDataGrid stretches over multiple pages then the second report loses its first page (section1 and section2 only)
2, When I try to add a chart after a multipage grid then I get this same exception please find my updated source attached. You will need to delete some of the rows in the grid to display the preview generated. (section1 and section3 only) It works if I add the chart before the multipage grid.
Let me know what I am doing wrong. Many thanks