RadarCube OLAP Grid and OLAP Chart for WPF: overview

It's the best choice for your WPF BI application. Extremely powerful and high-speed, yet wonderfully flexible when it comes to customizing, our OLAP controls will add to your Business Intelligence application the unsurpassable facilities of our OLAP solution, the best in its class.

Our product is a full-function set of OLAP controls, visualizing OLAP data both as table and as chart. Compatibility with almost any database or Microsoft Analysis Services server as data source, amazing performance and convenience, the maximum range of options - all this is at the service of analysts and OLAP-analysis experts.

Our controls are almost 10 MB of source codes, a few hundred thousand pages' text, almost five years of developing - we've done it all for you. Appreciate our solution at its true value, see our videos, illustrating our control's facilities or download the full-function evaluation version.

 

Detailed features

Data sources and export features

  • Supports any kind of data sources, like database, file etc. Supports Sql Server Analysis Services cubes as a multidimensional data source.
    • There're two versions of RadarCube for ASP.NET:
      • Direct
        Works with relational data sources of any kind through the DataSet, LINQ for SQL or Entity Framework. The real way of storing the data is irrelevant, since the MOLAP - architecture of the Radar Cube Desktop core makes it independent, hence fully universal.
      • MSAS
        Unlike the Desktop version uses Microsoft Analysis Services cubes and local cubes, created by MSAS. The versions from 2000 to 2012 are supported.
  • Supports large-size databases and cubes.
    • The special cache mechanisms and visual improvements allow working with databases containing up to 1,000,000 records (and in the case of MSAS version - practically with Cubes of any size), and with dimensions of many a thousand members.
  • Saving and restoring the current OLAP slice.
    • RadarCube supports a few methods of saving/restoring the state of OLAP slice: the data may be saved both by an end-user and programmatically. The state files are cross-platform - the data saved in WPF can be read in WinForms or in ASP.NET-version of RadarCube, and vice versa. Moreover, the Desktop version also supports the saving mode for Cellset with the Cube data. Play video
  • Handy integration with charting and other third-party components.
    • RadarCube may serve as data source for other controls - in this case RadarCube provides its current Cellset as data source. Data can be exposed in different modes - see the RadarCube documentation for details.
  • Export the Cellset to the most popular formats, like PDF, HTML, GIF, XLS etc.
    • In addition to copying to the Clipboard, RadarCube allows exporting an OLAP cellset into many other popular formats.
      RadarCube has lots of options for tuning its appearance and changing the contents of cells upon export, enabling/disabling paging and many other things.

OLAP specific features

  • Calculated measures of a few different types (row-table based measures, custom-aggregated measures and measures based on other Cube cells).
    • Play video RadarCube Direct supports many types of aggregating functions and, moreover, allows you to implement your own aggregating functions. Number, string or data fields can be used as measures.
      The Direct-version also supports the measures calculated on the fact table row level - a value of such measure is calculated sequentially for every row of the fact table during its fetching. The source data for measure calculation of this type is the information of the current row of the fact table and the rows of the dimension table related to it.
      Moreover, both MSAS and Direct versions support measures calculated from the current cellset data. The way of calculating can be implemented programmatically.
      Also it is possible to add measures, defined by MDX expressions.
  • Calculated hierarchy members.
    • Both the Direct and the MSAS versions allow creating additional calculated members inside any hierarchy. These members come very handy for, say, displaying some intermediate results. The algorithms of calculating such members are implemented programmatically in the appropriate control's event handlers.
      There's also an option of creating calculated hierarchy members through the end-user interface, with MDX expressions.
  • Attributes which store additional information about hierarchy members.
    • Play video Informational attributes contain additional information about dimension members. For example, for "Personnel" dimension the attributes may include information about home addresses and phone numbers. Usually attributes are presented as fields of the same dimension table that describes the dimension itself. A short video below will demonstrate you how to define attributes with Cube Editor and the way it looks in OLAP Grid.
  • Hierarchies of three types:
    • Attribute (or flat) hierarchies
    • Parent-Child hierarchies
    • Multilevel hierarchies
    • Play video On the core level RadarCube supports a few types of hierarchies:
       
      attribute (or flat)
      ordinary lists of titles and, possibly, a set of additional attributes. For example, the title for the Customers table will be Customer Name, and the set of attributes may include EMail, HomePhone, etc.
       
      parent-child
      created on the basis of self-referencing tables.
       
      multilevel
      created based on fields of one or a few tables, logically connected to each other by one-to-many relation.
       
      It's worth mentioning that both parent-child and multilevel hierarchies can also contain additional attributes.
  • A few types of drill-down support separately for every hierarchy member.
    • Play video RadarCube is the only OLAP-client that simultaniously supports a few types of drilling. These are:
       
      drilling down to the next level
      applied to multilevel hierarchies;
       
      drilling down to children of a parent-child hierarchy member
      applied to parent-child hierarchies or for member-groups.
       
      drilling down to the next hierarchy
      applied, when a few hierarchies are placed into the same active row or column area.
       
      Each type of drilling is marked by a unique icon.
       
      With this tool an analyst is able to create most complex OLAP-reports, impossible for any other OLAP-client, and display in the OLAP-environment the exact amount of information he needs at the moment.
  • Different simultaneous measure display modes (values, per cents from various totals etc).
    • Play video The same measure can be displayed in Grid in different modes: it can be exposed in its' absolute mode - as a value, or in relational - in per cent value from the totals by columns or by rows.
  • Member grouping on any hierarchy level.
    • Play video Besides standard OLAP operations, such as pivoting and drilling, RadarCube also supports member grouping. Groups may be created in hierarchies of any kind. Member grouping makes understanding and analyzing an OLAP-slice much easier, for example, applying the Pareto principle, you can save the "unimportant" for the current analysis hierarchy members into member groups.
  • Individual hierarchy or dimension customizable sorting on any level.
    • Play video Any hierarchy level may be sorted in three ways: in alphabetical order, in descending order or by default (with elements coming in the same order they do in the table or on the MSAS server). Besides, you can programmatically override all three methods, assigning "ascending" and "descending" order any custom meaning. For example, you can range the months not in alphabetical order, but from January to December.
  • Ascending or descending sorting based on any column value in the OLAP grid.
    • Play video Sorting by value allows an analyst to quickly pick out OLAP-cube elements he needs for the current analysis. It's worth saying, that the cells may be sorted not just by their absolute values, but by their per cent relation to rows' or columns' totals.
  • Filtering of any set of hierarchy members with or without applying these filters in the OLAP calculations.
    • Play video RadarCube allows using complicated filters applied to an arbitrary subset of members of different dimensions and hierarchies. At that, it doesn't matter if the filtered dimensions are situated in the active area (of rows or columns) - the applied filters and Cellset configuration are not interdependent.
      Moreover, besides the filters applied to hierarchy members, there're also context and visual filters - see other sections of "Detailed features".
  • Context filtering of the hierarchy members depending on their values in the Grid. Major/minor members selection, either based on their rank or on the Pareto principle.
    • Play video The result of applying context filters depends on the currently displayed Cellset and on the Cube data. For example, it is possible to apply such filters as "Show 3 most significant members of the Product Categories level by Internet Sales Amount values", "Show only the members that contain "ic" in their names", or "Display the data related to the third quarter of 2003". The context filters may be applied not only to dimensions, but to measures as well/ like: "Show the data cells with Sales Amount value over $1,000,000".
      Moreover, besides the context filters, there're also visual filters and filters applied to separate hierarchy members - see other sections of "OLAP specific features ".
  • Threshold visual filtering feature.
    • Play video Unlike filters for hierarchy members or context filters, visual filter is of the visual type - it simply lets you hide the values beyond the threshold defined by the user - without recalculating the whole Cube.
  • Supports the Writeback option (the Cube cells editing).
    • Play video RadarCube supports editing Cube cells.
      Native MSAS Writeback is used for the MSAS version, but for the Direct-version a programmer will have to implement the preferred way of changing the database.
  • Supports the Drillthrough option (browsing the relational data aggregated into a Cube cell).
    • Play video RadarCube supports browsing database data, aggregated into a displayed Cube cell (drillthrough). This operation is supported in both the MSAS- and the Direct-versions of RadarCube.

Appearance

OLAP Chart features

Direct version specific features

MSAS version specific features

  • Support of the MSAS Actions.
    • RadarCube supports MSAS Actions, such as URL, Drillthrough, Rowset etc. All these actions are interpreted according to their description in the MSAS Cube, and are accessible through the context menus of the corresponding RadarCube cells.

  • Support of Time intelligence features.
    • In the MSAS-versions for the data cells that deal with time measurement there is an option of using the "Time Intelligence" features - a powerful means for statistical analysis of Time series. It can be accumulating amounts, moving average or evaluating values growth in comparison to the previous period, etc.
      Time Intelligence functions are available through the context menu of data cells.
      As many other things in RadarCube, the Time Intelligence menu can be tuned programmatically.

  • Displaying results of arbitrary MDX queries.
    • Not only can RadarCube be used as a tool for browsing a multidimensional cube, but it can also display the results of MDX-queries. In that case, the Grid doesn't support such operations as drilling, pivoting, sorting, grouping, and filtering, but as always you’ll be able to change a cell's contents and its look and feel, as well as fix the row/column headers.

 

Why RadarCube

Different data sources

For a data source the control supports the MSAS server version 2000 or higher or any other database that has a NET provider. Due to the special cache technology the control is able to operate with the bases of up to 1,000,000 records, and in case it's an MSAS-version - with databases of practically unlimited size. It's the only control that is able to fetch data from several database tables and support both "Star" and "Snowflake" schemas on the MOLAP-core level.

Be careful! The commercial version of the control is shipped in two versions: Desktop (for working with relational databases) and MSAS (for working with the Microsoft Analysis Services server). Make sure you've ordered the correct version!

Usability

In addition to the flexible settings, the RadarCube for WPF has different popup menus that make it easy to access the RadarCube numerous functions. The menus are truly context-dependent and have unique options for each of the Grid cells and other items, depending on both cell type and content. Also, you can easily customize any popup menu by using an appropriate event.

NET Platform independence

RadarCube has a growing trend of unifying Desktop and Web platforms with its mobile representations. No matter which platform you work on - you will have the similar look and feel and almost the same API. This will allow you to share your code between the programming platforms and your users may move to a different platform with ease. In addition the cubes and states saved on one platform may be read on any different platform so you can use the same data right away without any additional steps.

OLAP controls's API

The RadarCube core has a detailed and well-documented API, which allows you to perform any OLAP-slice modifications from within your application, obtain information about any Cube or Grid cell. You can create your own sorting and context filtering. We can surely say the RaradCube is a constructor you can use to create OLAP-reports of any complexity.

Client requirements

  • NET Framework 4 or higher.

Developer requirements

  • Visual Studio 2010 (recommended) or 2012.
  • For RadarCube for MSAS: ADOMD.NET, Microsoft SQL Server Analysis Services OLE DB Provider.

Latest versions

February 12, 2013

RadarCube for WPF 1.50.1

Changes Download