The special cache mechanisms and visual improvements allow operating databases up to 1,000,000 records (and in case of MSAS version – in fact, bases of any size), and dimensions of many a thousand members.

RadarCube supports a few methods of saving/restoring the Grid: the data may be saved both by an end-user and programmatically. The Grid-state files are cross-platform - the data saved in ASP.NET can be read in WinForms or in VCL-version of RadarCube, and visa versa. Moreover, the Direct version also supports a saving mode for Cellset with the Cube data.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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".

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 ".

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.

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.

It is possible to programmatically change the contents of OLAP Grid cells, change the cell text, and insert images and icons into cells and even arbitrary HTML, Silverlight or ASP.NET fragments. OLAP Grid will automatically adjust the size of the cell to its contents.

The width of Grid columns is automatically adjusted to the contents of the cell, no matter what exactly they contain: text, images, or something else. Naturally, you can change cell’s width, if you like.

The option of page viewing hierarchy members is enabled in RadarCube OLAP Grid by default. The exact settings can be selected individually for each hierarchy: you can set the number of elements on a page, or disable paging altogether. You can also use the option of page-viewing in the hierarchy filters editor.

RadarCube offers an advanced system of context menus that provides users a quick access to all control's options. But more that that: any additional function may be implemented into RadarCube programmatically and then accessed via the context menu.

RadarCube's interface is very convenient for localization - all the lines visible for an end user, can be translated into any language. Moreover, any translation made by any user is also available to the rest of them, and is included into the next release of RadarCube. Thus, at the moment RadarCube is translated - fully or partially - into more than 20 languages.
By default, RadarCube uses the preferred language of an end-user's browser - but there is an option of strictly defining the main language for RadarCube.

RadarCube allows commenting on the contents of the cells, saving the comment even if the position of the cell in the Grid is changed. All comments cab be stored in the Grid state file and read later.

RadarCube OLAP Grid allows you to paint cells with different colors, depending on their values and a selected color scheme. This makes presentation of OLAP-data much more visual.

RadarCube RIA OLAP Grid supports three modes of selection, that can be transformed into one another simply by pressing Shift or Ctrl. The purpose of making two additional modes was to achieve a better presentaion of information in the Grid, visualizing in different colors and histograms the full range of values from the selected cells. The selected Grid area may also be copied to the Clipboard, and then pasted, for example, to Excel.

An OLAP-slice can be visualized – if necessary – by Areas, Lines, Splines, Bars, Pies and Points. End-users are able to select the type of visualization through a convenient context menu.

Both X and Y axes of the diagram are able to display hierarchies as well as measures. In case, measures will be selected for both the X and the Y axes, we’ll see the visualized correlation between measures on both axes of the charts, depending on the factors (hierarchies), set by the Detail-modificator.

The drilling operation in OLAP Chart is somewhat different from the same operation in OLAP Grid: OLAP Grid supports only the step-by-step drilling of a value, while OLAP Chart visualizes the whole value of elements on the same level, while intermediate levels may be skipped.
For example, for the Year-Quarter-Month hierarchy it is possible to visualize only the "Year" and the "Month" levels, skipping the "Qarter".

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.