Binding Business Object with null Property Bug
Posted: Fri Oct 20, 2006 7:46 pm
I came across a bug I think when testing the 20th Oct Build.
If I bind a Enumerable Collection object to the report which contains a child object in its collection, which also has a sub object = null
Example:
RowObjectCol : System.Collections.CollectionBase <- (Contains RowObject's)
RowObject <- Contains an "int" Property called "Number" and a sub object of "SubRowObject" which is null called "DataObject"
Binding RowObjectCol to the Report produces the following error:
"Cannot Set Column 'DataObject' to be null. Please use DBNull indead."
I came across this testing an existing report of mine which worked with an older build of v1.61
[edit: I tried it with a build of 11th Oct I had and it worked. Tried with the 13th Oct Build and up and it gives the error above]
I've provided a link to a Sample application that Replicates the error here:
Download Sample
If I bind a Enumerable Collection object to the report which contains a child object in its collection, which also has a sub object = null
Example:
RowObjectCol : System.Collections.CollectionBase <- (Contains RowObject's)
RowObject <- Contains an "int" Property called "Number" and a sub object of "SubRowObject" which is null called "DataObject"
Binding RowObjectCol to the Report produces the following error:
"Cannot Set Column 'DataObject' to be null. Please use DBNull indead."
I came across this testing an existing report of mine which worked with an older build of v1.61
[edit: I tried it with a build of 11th Oct I had and it worked. Tried with the 13th Oct Build and up and it gives the error above]
I've provided a link to a Sample application that Replicates the error here:
Download Sample