Page 1 of 2
Report errors - where did they go?
Posted: Thu Aug 12, 2010 8:25 pm
by chris.procter
When I used the .Net version of SS, if there was a problem on the report, the error exception or whatever would be displayed in a window at the bottom of the preview window in the designer.
In the .Wpf version, the preview pane appears not to refresh from it's previous contents, and no error message is visible anywhere.
Is there an option to display this information somewhere? I have two reports with problems, but I'm unable to solve them as I can't figure out the specific error.
Report errors - where did they go?
Posted: Fri Aug 13, 2010 1:20 am
by Alex K.
Hello,
Which version of Stimulsoft Reports.Wpf do you use?
Please send us your .MRT file for analysis.
Thank you.
Report errors - where did they go?
Posted: Fri Aug 13, 2010 1:34 pm
by chris.procter
I'm using 2010.2.749 10 Aug 2010
I'm not sure how much help the reports would be, as they use a number of custom libraries, but I'll attached one here.
(I'm still also having some speed / memory issues when running our reports, but I've been unable to get any specific information so far.)
Report errors - where did they go?
Posted: Fri Aug 13, 2010 1:37 pm
by chris.procter
I'm using 2010.2.749 10 Aug 2010
I'm not sure how much help the reports would be, as they use a number of custom libraries, but I'll attached one here.
(I'm still also having some speed / memory issues when running our reports, but I've been unable to get any specific information so far.)
Report errors - where did they go?
Posted: Fri Aug 13, 2010 1:38 pm
by chris.procter
Whoops - attached wrong file. Here's the one.
Report errors - where did they go?
Posted: Mon Aug 16, 2010 4:11 am
by Alex K.
Hello,
We made some improvements in that direction about a week ago.
Please check the latest prerelease build and let us know about the result.
Thank you.
Report errors - where did they go?
Posted: Tue Aug 17, 2010 3:00 pm
by chris.procter
I think I've figured out what the problem was:
We couldn't get the StiPropertiesProcessingType.Browsable option to work, so to prevent the report from traversing the entirety of our business objects (very slow), I converted only the required properties in to an anonymous type.
To avoid changing the report, I used nested anonymous types, ie:
Code: Select all
rm.RegData("RebatesInfo", rebates.Select(r => new {r.Amount, r.Type, r.Level, r.Date, Referral = (r.Referral== null) ? new {FullName="", Code = (int?)null} : new {r.Referral.FullName, r.Referral.Code}}));
which looks to have got converted in the report to
Code: Select all
Amount,Pleasant.Numeric.Measures.DecimalMeasure`1[Pleasant.Numeric.Measures.Money]
Type,Avena.Data.RebateType
Level,System.Int32
Date,System.DateTimeOffset
Referral,<>f__AnonymousType2`2[System.String,System.Nullable`1[System.Int32]]
_ID,System.Int32
_Current,System.Object
That anonymous type doesn't seem to have let the report load properly, and (as I was saying earlier), the .Wpf version didn't display any error messages, so it just gave a blank report.
I've changed things to use only 1 level of anonymous typing, and I think it's working.
Report errors - where did they go?
Posted: Wed Aug 18, 2010 2:09 am
by Andrew
Hello,
Could you please send us a sample project for investigation to
support@stimulsoft.com .
Thank you.
Report errors - where did they go?
Posted: Thu Aug 19, 2010 1:22 pm
by chris.procter
Hi - I've sent a sample project to that email. It looks like the problem also requires setting the BusinessObject.MaxLevel property to 1 (something we have to do to prevent a slow traversal of all our objects).
Report errors - where did they go?
Posted: Mon Aug 23, 2010 2:47 am
by Jan
Hello,
Sorry we can't support anonymous types now. It required big amount of changes in our source codes abd we can't make it now.
Thank you.