|
Problem When the columns bound to the Grid are not defined in the Grid dataSource, and are passed to the exporting method in Code behind, a null exception is thrown as follows. <Exception> System.NullReferenceException was unhandled by user code </Exception> Reason The dataSource passed to the exporting method is compared with the Grid dataSource. Thus, when a column is not defined in the Grid dataSource, it is obtained as null value and hence throws a null exception. Solution You need to ensure that the columns bound to the Grid are defined in the Grid dataSource before exporting the Grid. |
2X faster development
The ultimate ASP.NET Web Forms UI toolkit to boost your development speed.
This page will automatically be redirected to the sign-in page in 10 seconds.
You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.
I ran into this problem and my columns were the same as the grid but did not solve the problem, what solved it was remove the filter. I was filtering the grid before export but the items in the controller have no filtering. ej Grid = 2 rows, datasource before the export is called have 4 rows, making the error appear. Once both have synchronized data, it started working.
Hi Theresa,
To find out the root cause we need the following details,
1. Code example of a Grid and Controller.
2. Have you used foreignKey column in Grid?
3. Essential Studio Version details.
4. Share the business object model.
5. If possible send me the issue reproduceable sample.
Regards,
Prasanna Kumar N.S.V
Recently a had the same problema, and my DataSource was complete, so for a log time I couldn't figure it out, it end up been a problem with the GridProperties.SummaryRows that for some reason had some information in it and, when resetted to new List<SummmaryRow>, worked just fine.