One of the necessities in a properly designed DWH is a calendar table (aka date dimension). Usually, it’s one of the very first tables created in a DWH and it’s populated once for as many years in the past as well as in the future as needed. This blog provides a script for an Oracle database that can help loading a calendar table.
In my previous post I showed how to display “all” in a WebI report when the “all” value is selected in a drill filter. This blog will discuss almost the same. The only difference now is that the “all” value is selected in an input control.
Usually, a hierarchy in a WebI report “occupies” as many columns in a table as there are hierarchy levels. It means that if you want to show in a table a measure let’s say on a yearly, quarterly and monthly level, there are 3 columns in front of a column that shows the measure – one column for the [Year] dimension, one for the [Quarter] dimension and one for the [Month] dimension. Something like this simple report based on the eFashion universe:
If a hierarchy goes deeper and deeper (10+ levels deep hierarchy of products is not so unusual) then there are more and more columns in a table. In such case, displaying the hierarchy in just 1 column does not only save the space in the horizontal direction but may be much more appealing to report users. So have about the above table turned into this:
Let’s have a look how to achieve it using breaks and formatting.