For the DataTable
approach it will indeed be necessary to flatten the data, e.g. use columns like Address_State
and flatten the data among all Addresses and States.
Our developers came up with another approach that seems more simple and easier to implement and maintain. Next I will explain it:
You should use the ItemDataBinding
event of the data item (e.g. Table, Report, etc). At this point you have the values of the Report Parameters - in their Processing
instances (namespace Telerik.Reporting.Processing
). So, it is possible to construct the query that will be used to fetch the data. Thus, you may request from the service the count of the data records that will be requested by the original data source (WebServiceDataSource
). If you decide that this count is too big, you may set the DataSource
of the data item (its Processing
instance) to Null
, and the original data request will be skipped. Note that as you modify the Processing
instance of the data item, the definition instance (namespace Telerik.Reporting
) will not be changed, and on the next processing the data source from the definition will be preserved. If the decision is that the data should be fetched from the original source, it won't be necessary to make any changes.
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Feedback Portal
and vote to affect the priority of the items