Creating Composite Keys for levels of a Natural Hierarchy

The Current Country Attribute KeyColumn Property…

…will be changed into

Whenever changing KeyColumn we must define NameColumn…

…and check the Order By attribute is Key.

For the City attribute the changes are:

And the Customer Name property:

Now we should see the Warning Sign disappear and be able to Process this Dimension.

From a TARGIT End User perspective the Hierarchy is still the same.

Only difference is that related attributes are by default visible to the End User – this appears in the source data tab of the TARGIT Client like this:

Since the City attribute is now related to the Country, this relation is now visible to the End User. The same goes for Customer Name which has an attribute relationship to Customer Name.

This is not very useful in this particular case and therefore we choose to hide these related attributes in Analysis Services.

On the Customer Dimension Hierarchy you can expand the different levels and the related attributes appear to be seen.

Now we right click on the City attribute and choose properties

From the list of Properties we set Visible to False

When we have hidden both related attributes (and deployed/processed) the Source data tab in the TARGIT Client no longer shows the attributes.