Have you ever tried to do a nested IF THEN ELSE statement inside IBM Cognos Report Studio? If you have, you might run screaming because you can’t get the syntax just right. Granted, you could read the tips at the bottom as you build the syntax but shoot yourself in the head if you are not a programmer. You probably could pickup Chinese faster.

The idea behind this is that when creating a D-Cube you create it putting the D-List in order of 1-5. This helps in priority conflicts of formulas and formats. Plus, when you browse the library the D-Lists are sorted by the type of D-List. Easy Right? Maybe yes, Maybe no. The naming convention is open to interpretation. If I have a D-List for Years and it has no calculations, is it a 4 or a 3? What about a D-List that has Current Year Budget, Prior Year Actual, and a variance between Current Year Budget and Prior Year Actual. Is this a 5 since it has versions or is it a 1 since there is a calculation? What about a D-List that was a 3 but I’ve recently included a subtotal in the D-List do I need to go back and rename this to a 2?

The numbering method works great in a training class environment to help us learn the dimension order when creating the D-Cubes. After we learn the order, do we really need to number our dimensions?