You have many options:
Use LINQ + ADO.NET Entity Framework + SSAS Entity Infrastructure Provider is the easiest way, especially if you need ASP. NET code depends on SSAS data. Some data grids, such as ASPxGridView, will allow users to reorder columns, filters, and row order and dynamically generate LINQ changes in response to user actions.
ADOMD.NET + MDX - you can do it this way if you know MDX very well, but there is a lot of work for the dynamic interface, and I do not recommend this option if # 1 can do work, especially if you need ASP.NET code that depends from SSAS / ADOMD.NET data (MDX + ADOMD.NET does not provide type security, does not support refactoring and unit testing).
(This is not MVC, but a regular ASP.NET parameter). For maximum user level flexibility, use Pivot Grids such as XtraPivotGrid - your users will be able to move rows to columns and back, change filters and order and the pivot grid will generate a modified MDX for you. Again, I do not recommend this option if you need ASP.NET code that depends on this data.
(I work for Agile Design LLC, the company that created the SSAS Entity Framework provider )
EDIT: in the comment below: -Yes, the SSAS Entity Framework provider works with ASP.NET MVC and WebForms. MSI includes a demo web application.
source share