Posted 23 June 2020, 11:03 pm EST
I have created a report in C# code that displays how I want it on screen, but when I attempt to export it to PDF (or Excel or Word), nothing displays.
This is the class that passes the report through the system.
public class ExportSectionReport : Message<IReport>
{
public ExportSectionReport(IReport value, string path)
: base(value)
{
Path = path;
}
public string Path { get; }
[b]public IReport Report => Value;[/b]
}
IReport is a custom-defined defined class, not one created by GrapeCity. The SectionReport property is of type GrapeCity.ActiveReports.SectionReport:
public interface IReport
{
DataTable Data { get; }
[b]SectionReport Section { get; }[/b]
}
All of our reports are Section reports, and most are created with the designer and have a visual interface created at design time. The way we generate the export is:
private IMessage Handle(ExportSectionReport msg) {
var pdfExport = new PdfExport
{
ConvertMetaToPng = false,
ImageQuality = ImageQuality.Highest
};
msg.Report.Section.Run(true);
pdfExport.Export(msg.Report.Section.Document, msg.Path);
}
The report I am passing through the system inherits from SectionReport:
public partial class CustomerReport : SectionReport
For the report generated in code, this doesn’t work. The export completes, but the PDF is empty. I suspect this is because there is no visual interface. Looking at the msg.Report.Section.Document.Content property after the msg.Report.Section.Run has executed, the Content for a report designed in the designer is far larger than the one designed in code. I am guessing that is because the data is merged with the visual controls to create the export. The data is associated with Section.DataSource is correct in both version, so the data appears to be assigned.
So, is there a different way to export a code-generated report? Perhaps an overload of PdfExport.Export()?
