Setting Advanced Subset Properties

For most cases, the basic and default settings of subsets is sufficient for most applications.   There are times, however, when additional capability or information is required, such as flattening hierarchies, or restricting which dimensions allow the member lists to be modified at run time.   These options you will find in the Advanced Properties page of the subsets.  


ES Subset - Advanced Properties


The available advanced subset properties are:

hmtoggle_arrow1        Allow Member List to be Modified at Runtime        

This option enables (or disables) the ability for the user/application to control the list of dimension members to use when rendering the subset.  If this option is disabled, any parameters supplied in the URL for this dimension, which attempt to alter the member list, will be ignored.


hmtoggle_arrow1        Force positional replacement of members        (this option applies to Structured Views only)

There are some instances where a structured view that is initially set up in Enterprise Services will change over time, but will be changed by the elements that are selected in the columns.  One of the more common cases is a variance style view.    In a variance style view, usually a temporal dimension (i.e. Scenario, Period, Month, Year etc) is used on the columns such that a variance comparison can be displayed.   Consider the view as shown below:

Variance View

In this case, the variance is a monthly budget by Business Unit view.   When the view was first created, the Jan and Feb months were used to define the structure of the view.   In the application, however, suppose the user is given the option to change which two months to compare.   When the user alters which months are selected it is important that the view always returns a total of three columns of data or the variance page in the application may fail.   Enabling this option, forces the view to always return three columns of data; one for the business unit, and two months, even if only one member (or more than two members) was provided by the user/application.

If only one month (assume Mar) was provided by the user on the URL (i.e. http://localhost/es3/esweb.svc/json/MonthlyFinancials?Period=Mar) for the Period dimension, then the results would still return three columns, but the Feb column would have all blank values.   Without this option enabled for structured views, only two columns would be returned.


hmtoggle_arrow1        Include Hierarchy        

Include Hierarchy option group adds columns to the results which effectively Flatten the hierarchy so that relationally aware applications or components (such as grids) can now provide native capabilities like filtering, sorting and grouping on the data returned from TM1.   Flattening can be performed on both level based dimensions and ragged (or non-uniform) dimensions.  

TM1 Dimension

Flattened Dimension

Level Based Hierarchy

Flattened Hierarchy

There are a number of options that can be applied when including (flattening) a hierarchy.  For a detailed explanation of these options and how they apply to level-based and ragged hierarchies, see topic Flattening Hierarchies.