Working on the Flow Model Packager, I often have to make random changes to a model so I can test the model compare and deploy functionality.
Yesterday, I was using the item-based approach sample server as my test case, and decided to try to implement a more real-world change than I usually do (most of the time, I just add and delete things randomly for testing purposes).
This led to the idea of creating a new reporting cube that would ignore Category and Subcategory, but organize payments by “Payment Range”.
Using the item-based approach proved very flexible in this case, as I was able to add a quick rule and feeder to the input cube and create an entirely new cube which would report on information that wasn’t previously captured.
It also brought up some issues regarding re-triggering numeric feeders in TM1 10, which I will cover in an upcoming article.
For now, I thought I’d share the results for comparison — the model is attached. Happy modelling!