UltraGridDocumentExport throwing strange error

570

Sean K posted over 15 years ago

Hi, I am trying to use the UltraGridDocumentExporter to export the contents of an ultragrid to PDF. The code that I have written mirrors (almost exactly) some code from an IF employee's blog post. The method that I wrote was working fine, but is now throwing the dreaded "Object Reference not set to an instance of an object" whenever I try to export the grid. I tried using the method on another grid and it works perfectly fine. Both grids are in OutlookGroupByMode so I don't think that is the issue. Here is the exception/stack trace: ExceptionMessage: Object reference not set to an instance of an object. StackTrace: at Infragistics.Win.UltraWinGrid.DocumentExport.UltraGridDocumentExporter.ProcessGridRowInternal(UltraGridExporterHelper ultraGridExporterHelper, UltraGridRow row, ProcessRowParams processRowParams) at Infragistics.Win.UltraWinGrid.DocumentExport.UltraGridExporterHelper.Infragistics.Win.UltraWinGrid.IUltraGridExporter.ProcessRow(UltraGridRow row, ProcessRowParams processRowParams) at Infragistics.Win.UltraWinGrid.RowsCollection.InternalTraverseRowsHelper(IUltraGridExporter exporter) at Infragistics.Win.UltraWinGrid.UltraGrid.Export(IUltraGridExporter exporter) at Infragistics.Win.UltraWinGrid.DocumentExport.UltraGridDocumentExporter.Export(UltraGrid grid, ISection section) at Infragistics.Win.UltraWinGrid.DocumentExport.UltraGridDocumentExporter.Export(UltraGrid grid, Report report) at Infragistics.Win.UltraWinGrid.DocumentExport.UltraGridDocumentExporter.Export(UltraGrid grid, String fileName, GridExportFileFormat fileFormat) at PMS.MainUI.printToolStripMenuItem_Click(Object sender, EventArgs e) in C:\Development\Core\PMS\MainUI.cs:line 591 Here's the code, as I said before, the code works. There seems to be something about the layout of the grid that the exporter doesn't like.... using System; using System.Collections.Generic; using System.Linq; using System.Text; using Infragistics.Documents.Report; using Infragistics.Documents.Report.Section; using Infragistics.Documents.Report.Text; using Infragistics.Documents.Graphics; using Infragistics.Documents.Report.Table; using Infragistics.Documents.Report.Grid; using Infragistics.Documents.Report.Band; using Infragistics.Documents.Report.Flow; using Infragistics.Win.UltraWinGrid; using Infragistics.Win.UltraWinGrid.DocumentExport; using System.Xml; namespace PMS.Reporting { public class PDFExporter { private static UltraGridDocumentExporter myExporter = new UltraGridDocumentExporter(); public static void ExportOMSGrid(UltraGrid pUltraGrid) { Report r = new Report(); ISection s1 = r.AddSection(); s1.PageNumbering.SkipFirst = true; s1.PageNumbering.OffsetY = -18; s1.PageNumbering.Template = "Page [Page #] of [TotalPages]"; ISectionHeader s1Header = s1.AddHeader(); s1Header.Height = 20; IText s1headertitle = s1Header.AddText(0, 0); s1headertitle.AddContent(string.Format("Trade Blotter\n As Of {0}", DateTime.Now.ToString("MM/dd/yy hh:mm"))); s1headertitle.Alignment = TextAlignment.Center; myExporter.Export(pUltraGrid, s1); } } } Any help would be appreciated Thanks, Sean

Parents

469350

Suggested Answer
Offline Mike Saltzman posted over 15 years ago

Are you using the latest service release? This is probably a known bug that is already fixed.

How to get the latest service release - Infragistics Community
Cancel
Reply

Reject Answer

Cancel
570

Sean K posted over 15 years ago in reply to Mike Saltzman

I upgraded to v 9.2 after getting the error yesterday. There are currenty no service releases for the 9.2 WinClient release
Cancel
Reply

Cancel
469350

Offline Mike Saltzman posted over 15 years ago in reply to Sean K

In that case, there are two possibilities.

One is that this is fixed in a service release that is not yet available for v9.2. There may be some fixes that are in the latest service release for v9.1 or earlier that are not yet available in v9.2.

Or, this bug is not fixed. In which case, w would need to be able to duplicate the exception. Can you duplicate this in a small sample project?
Cancel
Reply

Cancel
570

Sean K posted over 15 years ago in reply to Mike Saltzman

Here you go Mike, this sample project throws the same error.

Any help you could offer would be appreciated.

Thanks!

TestPDFOutput.zip
Cancel
Reply

Cancel

Reply

469350

Offline Mike Saltzman posted over 15 years ago in reply to Sean K

Hi,

Thanks for the sample. I duplicated the exception. Looks like it happens when you have FormattedText in the grid and are using GroupBy and try to export. This is clearly a bug.

I'm going to forward this thread over to Infragistics Developer Support so they can write it up and get it corrected for the next service release.
Cancel
Reply

Cancel

Children

570

Sean K posted over 15 years ago in reply to Mike Saltzman

Worked like a charm, thanks Mike!
Cancel
Reply

Cancel
469350

Verified Answer
Offline Mike Saltzman posted over 15 years ago in reply to Sean K

Hi,

What you would have to do is use the InitializeRow event of the UltraGridDocumentExporter. The event args have properties to allow you to skip rows.

So what you would do is export the grid to a section and skip everything but the first row. Then export the grid to a second second and skip everything but the second row. The export the grid to a third section and skip everything but the third row, etc.
Cancel
Reply

Reject Answer

Cancel
570

Sean K posted over 15 years ago in reply to Mike Saltzman

Hi Mike,

Changing the ColumnStyle during the export event did the trick, thanks.

Are you aware of any straightforward way of exporting only certain rows of a grid to a particular section? Ideally, I would like to create a new section/page for each one of my group by rows (and it's children). So if there are 8 group by rows I should get 8 pages, the only catch being that if one group by row has more children than will fit on one page, then that group by row should span two pages each with the same group by header.

Any thoughts?

Thanks in advance
Cancel
Reply

Cancel
469350

Verified Answer
Offline Mike Saltzman posted over 15 years ago in reply to Sean K

Yes, if you don't mind not exporting the formated text, then that's probably a good workaround. How you do that depends on how you set up the formatted text columns in the first place, though. If you are using an Editor or EditorControl, then you need to set that property on the column to null. If you are using the Style property, then you can just set Style to default.

Either way, you should do this in the BeginExport event of the UltraGridDocumentExporter component and do it on the e.Layout that is passed into the event. That way it will affect the export, but not the on-screen grid and you don't have to worry about setting it back.
Cancel
Reply

Reject Answer

Cancel
570

Sean K posted over 15 years ago in reply to Mike Saltzman

Thanks mike, in the meantime should I just change any columns that are FormattedText to something else before exporting? I belive the columns which are formatted text used to be drop down lists, the exporter didn't seem to have a problem with drop downs.
Cancel
Reply

Cancel