Hi,
I just upgraded to 2009 Q3 Reporting and all my reports are broken, saying:
An error occured while processing TextBox 'txtNumber':
The expression contains object 'Number' that is not defined in the current context.
the field Format is:
this.txtNumber.Value = "=Format(\"Invoice Nr.: {0}\", Fields.Number)";
and the Entity is assigned in NeedDataSource event.
I just upgraded to 2009 Q3 Reporting and all my reports are broken, saying:
An error occured while processing TextBox 'txtNumber':
The expression contains object 'Number' that is not defined in the current context.
the field Format is:
this.txtNumber.Value = "=Format(\"Invoice Nr.: {0}\", Fields.Number)";
and the Entity is assigned in NeedDataSource event.
6 Answers, 1 is accepted
0
Hi fruzicka,
Unfortunately this happens to be a defect that for some reason has slipped into the release version. We are already working on and we would release an internal build that resolves this issue by the end of the week.
In short the problem appears when the data source is some kind of object array, object list or similar collection of System.Objects but not a specific type. In your case, when a non-enumerable object is used, an object array with only one item is created internally, that unfortunately causes the described behavior.
There are two possible solutions: rollback to the previous version and wait for the fix (end of the week) or use a typed collection: List<Invoice>;
Once again please accept our apologies for the troubles caused.
All the best,
Steve
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Unfortunately this happens to be a defect that for some reason has slipped into the release version. We are already working on and we would release an internal build that resolves this issue by the end of the week.
In short the problem appears when the data source is some kind of object array, object list or similar collection of System.Objects but not a specific type. In your case, when a non-enumerable object is used, an object array with only one item is created internally, that unfortunately causes the described behavior.
There are two possible solutions: rollback to the previous version and wait for the fix (end of the week) or use a typed collection: List<Invoice>;
Once again please accept our apologies for the troubles caused.
All the best,
Steve
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
Jon
Top achievements
Rank 1
Rank 1
answered on 12 Nov 2009, 07:57 PM
I'm getting the same problem on a couple of my reports that the datasource is set to an nhibernate retrieved object. There is a subreport that is an IList but even the fields that are directly from the datasource are not showing up. Most of my reports are fine though, so I can't figure out what causes just those few to freak out.
0
Jon
Top achievements
Rank 1
Rank 1
answered on 19 Nov 2009, 07:27 PM
What is the status of this fix? My customers are getting a little antsy to get "invioces" or whatever back :)
0
fruzicka
Top achievements
Rank 1
Rank 1
answered on 19 Nov 2009, 07:48 PM
I have downloaded DEV build 1113 and it's working with EntitySpaces objects, so Im sticking with that build for now.
0
Hi guys,
The internal build 1113 fixes the problem. For the more information about this version, please see the release notes.
Kind regards,
Svetoslav
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
The internal build 1113 fixes the problem. For the more information about this version, please see the release notes.
Kind regards,
Svetoslav
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
0
Jon
Top achievements
Rank 1
Rank 1
answered on 21 Nov 2009, 05:12 PM
edited.. problem went away after reboot.