Global Dimensions is a feature that makes it possible to link otherwise unrelated hierarchies. Doing so enables you to perform only one filtration in the criteria bar, this filtration will then take effect on all the hierarchies in the same Global Dimension.
You create an XML file in which you connect hierarchies in a "global dimension" element.
The hierarchies must have the same structure, i.e. same type, same amount of levels, and same content. Anexample to clarify this: if you have a time hierarchy of 'YMD' you cannot combine it with a hierarchy with a 'YQMD' level, they have to be the same. Please note:
- To create a Global Dimension you must provide it with a unique id.
- Hierarchies that should be linked must be included in the same "global dimension" element. You can link as many hierarchies as you wish.
There is no user interface for creating Global Dimensions, so you must create an XML file and create the "global dimension" elements you need. Please follow the steps below and take a close look at the example on the next page, this should enable you to create your own Global Dimensions.
- Create a folder for your XML file. This folder must be located in the 'Settings' folder on the TARGIT Server.
Default path is: 'C:\ProgramData\TARGIT\ANTServer\Settings'.
The folder must be named 'GlobalDimensions'.
- Create an XML file named 'GlobalDimensions.xml' and save it in the folder above.
You are now ready to create Global Dimensions in the XML file.
On the next page you will find an example of an XLM file with two global dimensions elements: 'time_hierarchy" and "time_month".
Use the example and the information below to create your own Global Dimensions.
Below is an example of an XML file with two global dimensions elements: 'time_hierarchy" and "time_month":
<?xml version="1.0" encoding="utf-8"?>
<metadata database="DemoData" cube="Sales" dimension="Period" hierarchy="Period" />
<metadata database="CasualClothing" cube="Clothing" dimension="Posting Period" hierarchy="Hierarchy" />
<metadata database="DemoData" cube="Sales" dimension="Period" hierarchy="Month" />
<metadata database="CasualClothing" cube="Clothing" dimension="Posting Period" hierarchy="Month" />
The global dimension with id="time_hierarchy" in the example above links the "Period" hierarchy (in the "Period " dimension in the Sales cube) with the "Hierarchy" hierarchy (in the "Posting Period" dimension in the "CasualClothing" cube).
Likewise, the "Month" hierarchies in the "Period" and "Posting Period" dimension are linked in the global dimension with id="time_month".
Note: Remember that the hierarchies must have the same structure and also note that the key-values (which are used for Global Dimensions might not be the same as the displayed values - see example below):
Keyvalues vs. Display values
In Global Dimensions the values that are mapped "behind the scene" is actually key values and not so called display values.
In this example I will try to map some weekdays from one cube against some weekdays from another cube and illustrate this point.
One of the weekdays is from TARGITs demodata Salescube.
If I locate the weekday in the source data panel and right click it - I get an offer to see information about it:
The explanation tells me that the weekdays I see (Monday, Tuesday, Wednesday, Thursday etc. has a key that is an integer (1,2,3, 4 etc):
This is important information - it means that when I map Time Weekday against another dimension, that dimension will have to have a similar key.
This attribute from my Data Discovery data source won't do - even though it's showing the same weekdays (display value), the keys are not the same as the previous Weekday from demodata:
In my Data Discovery data source I have another attribute called weekday, where the information shown looks like this:
This will do - even though the displayed values are different - the keys are exactly the same as my Weekday from Demodata.
My Global Dimensions document will look like this:
So remember to look out for key-values when using Global Dimensions.
There is currently a bug that also means that in some cases the attributes need to have the same name for Global Dimensions to work. This will be sorted in the 2022 Spring release of TARGIT.