-
Press Release: Apliqo UX and Cubewise Canvas for TM1 to be offered as a single product
Apliqo UX and Cubewise Canvas for TM1 to be offered as a single product Apliqo UX and Canvas for TM1 have been combined to a single product which will be known as Apliqo UX.Future releases of Apliqo UX will contain all features and functionality of both products. Apliqo UX improves the adoption rate and user…
-
Cubewise Opens First Branch In Germany
Cubewise opened a branch in Munich this month, consolidating its role as IBM Germany’s leading Platinum Partner. Markus Fynmore also joins Cubewise Germany as Practice Manager at the new Branch in Munich. Cubewise, winner of the IBM Solutions Bestseller Award 2018, opened its first German branch in Munich this month. (From left to right: Marco…
-
Filter strings in bedrock
Understanding how the pFilter parameter encodes filter strings is central to understanding the bedrock library. Bedrock converts the contents of the pFilter string into views by splitting the string into dimension names and element names and creating the view on the fly. Let’s examine the components of the filter string using the process }bedrock.cube.view.create – pCube = “Employee” – pFilter = “Year…
-
List and Wildcard Functionality in bedrock
The bedrock library has always included support for lists and wildcards in strings passed to parameters. In previous versions of the library, the implementation of list and wildcard support was inconsistent with some bedrock v3 processes allowing users to input a list of objects separated by a delimiter and some included wildcard functionality. However, other…
-
Need to know essentials for Planning Analytics
Our colleagues from Cubewise CODE have done some great work producing not just 1 but 3, “cheat sheets” which are super densely packed with knowledge. Each sheet is separately targeted at End Users, Developers or Administrators. The sheets have some handy colour-coding so you can easily distinguish what should be basic knowledge, advanced knowledge, or “extra reading”…
-
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 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…
-
Attributes in TM1. More things to be aware of
We all know that attributes are a very useful feature of TM1 with many uses for lookups in modeling as well as providing context for reporting. In a recent post, we talked about the Caption attribute as a potential default attribute for all dimensions and how the attribute is linked to the intrinsic MEMBER_CAPTION MDX…
-
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…