-
Enabling hierarchies, how does it affect your current model?
Welcome to this instalment of our series on upgrading to Planning Analytics. If you’re here then you probably know about the new features that PA brings such as Workspace, hierarchies and multi-threaded feeders, but you’re hesitant about whether to implement the new features due to concerns about the impact on your current mature implementation. If this describes…
-
How to reference intersections of hierarchies in rules
This is a follow on from the previous article on working with hierarchies in rules. It will deal with how to address the intersection of two (or more) hierarchies in the right-hand side of a rule statement and the left-hand side of a feeder statement. Note this is accurate as at version 2.0.6.71 Intersections of hierarchies…
-
An unintended benefit of hierarchies
The Leaves hierarchy When an alternate hierarchy is added to a dimension in TM1 for the first time a Leaves hierarchy is also automatically created in the background. The Leaves hierarchy has some special properties as it contains only leaf elements (inserting consolidations is not possible). The maintenance task of inserting new elements into the…
-
How to work with hierarchies in rules
This article is a little longer than normal, but we do go into quite a bit of detail with some examples of how the hierarchy syntax works in various situations. It’s step-by-step so should be not problem for anyone with an understanding of TM1 rules to follow. All code examples have extra spacing added for…
-
We old-schoolers need to revisit the language we use to talk about dimension structures
Back Then … In the TM1 world, many people have for many years been used to saying “hierarchies” when referring to hierarchical dimension structures e.g. Ancestor > direct children (consolidated) > intermediate consolidations > ultimate leaf descendants When TM1 was just TM1 and dimensions didn’t have named hierarchies this was OK as it was still…
-
Using hierarchies for PickLists
PickLists, a quick recap. As we know PickLists in Planning Analytics can be defined in 3 ways: as static lists using the form static::item1:item2:item3 based on dimensions using the form dimension:dimName based on subsets using the form subset:dimName:subName PickLists can be defined either via naming a dimension attribute “PickList” and defining a string value for…