How to create a TM1 view in Architect using a level?

[abcuser]

Hi,
using Cognos BI 10.2 accessing using TM1 10.1.1 cube using Dynamic Query Mode on the same Windows 2008 R2.

I have a the following report in Cognos BI in columns there are measures, but in rows there is a level MarketBuyer from Market dimension. Market dimension has the following hierarchy: top Market member --> MarketContinent --> MarketCountry --> MarketBuyer. This hierarchy is also specified in control cube }HierarchyProperties and so the level used in Cognos BI.

This report runs for two minutes and I would like to speed it up. In tm1top.ini I have set refresh=1 and running tm1top to monitor if TM1 is bottleneck or Cognos BI and I see TM1 is executing report for almost two minutes (some seconds less).

So my idea to spead up a report execution is to create a TM1 view, run it as scheduled chore using ViewConstruct process command and so make sure the data from this view are already in memory when accessed from Cognos BI.

Now the problem. In TM1 inside "cube | Views" right click and "Create new view". In columns I have drag and drop a measures (the same as in Cognos BI report) and in rows I need MarketBuyer level. Is there a way to add this level to view? Or is there another way to add members from this MarketBuyer level? It would be nice that I would not need to update this view manually each day - this is daily updated cube and new buyers can be added daily.

Thanks

[David Usherwood]

This is pretty much TM1 101. When creating the view, click on the Market dimension and select by level -

Select by Level.jpg (968 Bytes) Viewed 2680 times

. Just bear in mind that:
a TM1 levels are numbered upwards - zero is the lowest level. Level Names are only relevant to BI;
b Since you want to add new elements which arrive from your feed, make the subset dynamic.
Create the view including that subset, write a one line TI to viewconstruct it each morning. I'd say that should help quite a bit. Using Multithreaded query would make the construct run faster but that's not an issue you have mentioned.