Excel Export causes AfterCellUpdate to fire.

State See Verified Answer
Replies 3 replies
Subscribers 6 subscribers
Views 1056314 views
Users 0 members are here

UltraGrid

1934

Boyd posted over 15 years ago

When I attempt to export a grid using UltraGridExcelExporter AfterCellUpdate events are fired when I call the Export method of the exporter. I have never seen this happen before, any idea what could be causing this to happen? When the grid is exported to Excel I understand that UltraGridExcelExporter makes a copy of the grid for manipulation during export. For some reason this fires the AfterCellUpdate event on my grid. When I check e.Cell.Column.Band.Layout.Grid in AfterCellUpdate during export it is the copy created by UltraGridExcelExporter, so why is it firing on my grid?

Parents

469350

Offline Mike Saltzman posted over 15 years ago

Hi,
The ExcelExporter does not make a copy of the grid, it makes a copy of the Layout. But I can see no reason why this would fire AfterCellUpdate.
For which cells is the event firing? Are there unsaved changes in your grid when you attempt to export?
Cancel
Reply

Cancel
1934

Boyd posted over 15 years ago in reply to Mike Saltzman

The event seems to be firing for all "custom" columns. That is columns which I load from a database which include formula columns and columns where the user is allowed to enter numbers or strings, etc. For the columns where the user can enter information I store their values in the database and populate the grid values on load so these values are definitely being saved. I have found a workaround by just setting a flag if I am exporting but was just curious as to why this event is being fired, thanks for your help.
Cancel
Reply

Cancel

Reply

469350

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

Well, like I said, I can't see any reason why exporting would cause AfterCellUpdate to fire. Unless something else in your code is also occurring during the export.
If you can duplicate the problem in a small sample project, you can Submit an incident to Infragistics Developer Support and they should be able to tell you why it's firing.
Cancel
Reply

Reject Answer

Cancel

Children

No Data