Set the number of column and row displayed by Contributor

[comma]

By default, Contributor will only display 20 columns and 100 rows maximum per page. If your view has more than 20 columns or 100 rows, then you have to click the next page button. Can we change this? I would like to display more column / row per page to increase the usability of my view. I've read the Contributor User Guide and Admin Guide, but no luck.

[kwijibo]

The solution is found in the TM1 operations guide. Here is the relevant excerpt from the documentation of version 9.5.1.
(source: http://public.dhe.ibm.com/software/data ... tm1_op.pdf , p.167 f):

Changing the Cube Viewer Page Size
By default, the IBM® Cognos® TM1®Web Cube Viewer displays pages of TM1 data with 20 columns and 100 rows, and includes the dimensions list in the row count.
Steps
1. Edit Web.config.
2. Locate the following code:
CubeViewerRowPageSize
CubeViewerColumnPageSize
3. Change the value for the row and/or column page size.
4. Save Web.config.
5. Log in to IBM Cognos TM1 Web.
For example, if you set the row page size to 10, the Cube Viewer displays nine rows of data, plus the row of dimensions.

The file 'web.config' is found under your TM1Web install location (usually C:\Inetpub\wwwroot\TM1Web\).
This applies to TM1Web and contributor client.

Cheerio

[comma]

Thanks, kwijibo. Guess I missed that out, sorry.

Another question, has anyone find the maximum column and row before the load time become unacceptable?
I've tried 50 columns x 200 rows, but it started to get a bit laggy

[sachin]

Bumping this thread ... we are in similar situation. I'd like to know what, if any, was the performance impact you faced. Does anyone know of, an upper limit for rows or columns, beyond which the performance becomes sub-optimal?

The changes that need to be done are for web.config, which we believe is used by TM1 web. We were surprised that TM1 Application (aka TM1 contributor) was relying on the components of TM1 web to achieve its functionality!

[mvaspal]

HI

This depends on a couple of factors when we talk about cube views (not websheets for now):
- network speed,
- browser rendering speed,
- calculation time on server side (amount of data, rules, etc.)
- your understanding on what is "sub-optimal"

As much as I know there is no upper limit in the configuration but if you set this too high, as you experienced, it starts rendering really slowly.

When I was playing around with this using a SKU dimension with ca. 1500 elements on rows and a few measures on the columns it was still OK with 2-300 rows per page and started to become slow after ca 4-500 rows per page. This wasn't a rule heavy cube, just a very few variance and index calcs on the columns, simple ratios. In complicated websheets this 2-300 lines might be already too many to render at once.

The changes that need to be done are for web.config, which we believe is used by TM1 web

Check out the URL when you open up a node - it is something like http://servername/TM1Web/contributor.aspx
My understanding is that only the Application portal and the workflow page is a Java application deployed usually in Tomcat (pmpsvc) but when you open up a node it is already linked to the .NET based TM1Web.

[sachin]

Well, with 20 rows and columns, it already renders slowly. We tried to increase 100 rows by 50 columns and it was painfully slowly with it. Perhaps the dev server we are in needs more horse power! Anyway, our users who are accustomed to EP, pagination in TM1 will be hard to adjust to. So we will have to make the screens 1 X 1 (i.e. no pagination)

When we saw the instructions, we initially thought it was for only TM1WEB. Later we found it also applies for TM1 Application (aka Contributor). Since pmpsvc uses Tomcat, we were shocked to see that it is using a .Net component instead of Java! OTH, in EP that isn't the case.