If you are looking to use IDataReader interface to view the underlying data in a silverlight application then a way which I can think of is to add a web service to get the underlying data, using the same approach as suggested in the windows sample. Next you can reference that service to your silverlight project to get the data.

But Pivot Viewer alredy has functionality to read underlying data as we can see in your sample above. The component can provide data and all what I need is the function that is similar to the following:

This is possible in the latest maintenance release. I would recommend downloading our hotfix from here though:

http://downloads.datadynamics.com/gcaa-2.1.706.0.zip

Once installed, take a look at the CustomUnderlyingDataGrid sample project (installed by default to: C:\Users\Public\Documents\GrapeCity\ActiveAnalysis\2.1.706.0\Samples\Windows.Forms\CS\CustomUnderlyingDataGrid\CustomUnderlyingDataGrid.2010.csproj)

Thank you for clarifying your requirements and providing additional information. Regarding you request related to the underlying data, I have opened a new feature request to add a functionality similar to the IDataReader, in the silverlight assembly. The tracking number is Case 156537.

For your second request to add the SetCubeFilter to the MdxDataSource class in the silverlight assembly, I have opened another feature Case 156536. However, I would like to tell you that you may want to check the MdxCubeFilter Silverlight sample which is shipped with ActiveAnalysis. This sample demonstrates how to establish server side connection to MDX data source with cube filter.

You will be notified once a build containing these features would be released in future.

The development team has asked me to get some more information from you regarding the implementation of Case 156536 related to the addition of the SetCubeFilter to the MdxDataSource class in the silverlight assembly. In general scenarios most of the users would prefer to use the ServerSideDatasource instead of client MdxDataSource, because it requires to share connection string on client side.

Since we already provide a way to apply the cube filter when working with ServerSideDataSource, I would like to know why are you looking to stick to the MdxDataSource? Could you please provide some detailed information about your use case and how do you look to implement it?