Hi guys!
After upgrading from v2009 vol2 to vol3 one of my reports stopped working. It only showed the first detail row of any given datatable.
During the design of the report I used a DataSet and a DataAdapter but during runtime I use a simple DataTable that I bind using the datasource property of the report. With vol 3 that didn't work any more, no error message, nothing. Only one detail row is produced.
The solution was/is to set the DataAdapter to null and the DataMember to "", then everything works again.
(Why is only on row produced, seems to me it should be none or all rows?)
Proposed Solution:
[C#]
XtraReport1 report = new XtraReport1();
report.DataMember = "InvalidDataMember";
report.DataSource =ds ;
report.DataMember = "ValidDataMember";
report.FillDataSource();
or
[C#]
traReport1 report = new XtraReport1();
report.DataMember = "InvalidDataMember";
…
report.DataMember = "";
report.DataSource =ds ;
report.DataMember = "ValidDataMember";
We have closed this ticket because another page addresses its subject:
Only 1 Row Shown in Report
Since I can't comment on another issue I'll post my thoughts here. After reading through the other case I'll say that you should reconsider this issue and handle it, either you throw an exception, or preferably handle it automagically like before*. You guys actually decreased functionality in an upgrade. In charts you throw an exception, so consistency is needed.
* If the tableadapter and datamember match, use them, else try to match column names.
Best regards
Adam
Hi Adam,
This problem was caused by the "auto select" behavior in previous versions of the suite.
In previous versions, when the XtraReport.DataSource gets set at runtime, DataMember validation process appears and if it was unsuccessful, the DataMember will be set to FIRST table name.
This behavior may cause lots of issues if the order of DataTables in the DataSet is changed.
So, we decided to modify this behavior in newer versions of the suite: Currently, when setting XtraReport.DataSource property and the DataMember is valid, everything should work as expected, otherwise a DataMember will be cleared.
And you need to set it afterwards. However, we can't raise an exception in this case since it may break the working functionality for other customers, in case if DataMember property is set after the DataSource, which is a valid scenario at present.
For example :
XtraReport1 report = new XtraReport1(); report.DataMember = "InvalidDataMember"; report.DataSource =ds ; //Exception is raised report.DataMember = "ValidDataMember";Thanks,
Andrew
I'm sorry if you feel that I press on here, but obviously you've introduced one breaking change already.
Now what you describe is invalid in charts. By going about things like you have now, you leave the door wide open for arbitrary errors that will be hard to troubleshoot for the end user. I mean seriously, 1(?!) detail row and then nothing… :-)
In the charts you need to first nullify erroneous references before you bind to/fill the data. (Alternatively raise an exception at binding to a report viewer.)
Charts and reports are quite similar products, and I really feel that charts solved this better with a clear error message.
I do love working with your components, and thats why I feel it's important that you keep them stringent av robust.
Best regards
Adam Nerell
Hi Adam,
Thank you for the feedback.
Yes, we've made a breaking change due to a bug fix(Page Builder - Incorrect data is shown in the first detail record when sorting is enabled for a DetailReportBand).However, we believe that our previous behavior with auto-selecting of the first datatable, if the specified DataMember wasn't found, was incorrect.
I've contacted our R&D team regarding the idea of raising an exception, but I should mention that it's impossible in this case since a DataMember may be supplied after the DataSource, and this exception will introduce a new breaking change.
Thanks,
Andrew