Sorting on reports using column-headers that have on-demand sub-reports embedded in them only works partially. When the report is first opened, the sorting works fine on all the columns.
The trouble starts when the report is drilled into, and the column headers in the sub-report are clicked on - the data in the report changes.
I checked in about 7 passes under various conditions, and the dataset for the sub-report does not change i.e. the
underlying data does not change. (Am using push model with C#). This leads me to believe that the link field between the main report and the sub-report is being changed at run-time(this is similar to a group field being automatically and irreversibly added to the sort fields collection).
When trying to trap or reset the link field at run-time, am unable to identify an exposed property that could be used in acccomplishing the same.
From all the events exposed for the viewer, there is only one that is fired - the DrillDownSubreport - and a comparison of all seven of the properties before and after the event occurs shows that they are the same. Searched with a very fine toothcomb, but was unable to identify a relevant property that could be used to flag the drill state.
Any thoughts - much obliged.
Amit Kohli
The trouble starts when the report is drilled into, and the column headers in the sub-report are clicked on - the data in the report changes.
I checked in about 7 passes under various conditions, and the dataset for the sub-report does not change i.e. the
underlying data does not change. (Am using push model with C#). This leads me to believe that the link field between the main report and the sub-report is being changed at run-time(this is similar to a group field being automatically and irreversibly added to the sort fields collection).
When trying to trap or reset the link field at run-time, am unable to identify an exposed property that could be used in acccomplishing the same.
From all the events exposed for the viewer, there is only one that is fired - the DrillDownSubreport - and a comparison of all seven of the properties before and after the event occurs shows that they are the same. Searched with a very fine toothcomb, but was unable to identify a relevant property that could be used to flag the drill state.
Any thoughts - much obliged.
Amit Kohli