Page 1 of 1

10.2 web rebuild 'current book'

Posted: Fri Oct 24, 2014 10:10 am
by JamiseBondi
The setup we have as a standard in our workbooks/websheets is to have a menu page that has a few parameters that are excel named ranges. In subsequent sheets of the workbook we reference these named ranges to speed up the selection process in those sheets.
In 10.1 I've found that if the menu sheet is populated with a version dimension (for instance) and I do a "rebuild active forms" - this has the effect of rebuilding all active forms in the workbook that use this named range.
in 10.2 when I perform the same task it has the effect of only rebuilding the current sheet (menu sheet). There are subsequent sheets that are active forms that are not getting rebuilt. I have to go into each of them to rebuild them.

As a side note here: This behaviour is seen when I have the following situation:
If the workbook has a version dimension and this dimension is not populated when the websheet is opened then I can't get all tabs of the websheet to rebuild without going into each of them and rebuilding individually (10.2 behaviour). I can rebuild all of them from the menu sheet in 10.1
If I pre-populate this menu sheet with a version and then open it up in the web, all active forms are populated without me having to do a rebuild (in 10.1 and 10.2).
So the question is, how would I achieve a "rebuild current book" equivalent in 10.2 that I already have in 10.1 in the web?
I'm on the latest fixpack: 10.2.2.100.123

thanks guys.

Re: 10.2 web rebuild 'current book'

Posted: Fri Oct 24, 2014 12:29 pm
by tomok
Why would you care if all the active forms are rebuilt on opening if there is no selection made for version? If the active form is built off a cube that has the Version dimension in it AND you do not select an element for it then the active form will be empty, right? If the active form is going to be empty after rebuild then why is it necessary to rebuild? Just trying to understand.

Re: 10.2 web rebuild 'current book'

Posted: Tue Oct 28, 2014 1:23 pm
by JamiseBondi
tomok wrote:Why would you care if all the active forms are rebuilt on opening if there is no selection made for version? If the active form is built off a cube that has the Version dimension in it AND you do not select an element for it then the active form will be empty, right? If the active form is going to be empty after rebuild then why is it necessary to rebuild? Just trying to understand.
Hi Tomok,

The scenario is this: Currently (in 10.1) we can have a workbook with many active forms in it - it has a menu tab with a version that is blank. When a user opens the workbook in the web, they select a version (at this point all active forms are empty) and then rebuild the active form while on the menu tab. Now when the user navigates to each active form in turn - each AF is populated without the need to press rebuild on each form. This saves a bit of time.

In contrast to this behaviour: in 10.2 -> the user selects a version from the menu tab and then rebuilds the AF (which updates a hidden excel named range on this menu tab which is what is used in the subsequent active forms), when they navigate to each active form none of them are populated. The user has to rebuild on each active form to populate it. This wastes a bit of time.

So I was trying to get the behaviour I see in 10.1 into 10.2 so that we can still load the workbook up with a blank version (which has other not mentioned maintenance benefits) and still have all active forms populating when the user navigates to each form.
Hope this makes sense?
Thanks.

Re: 10.2 web rebuild 'current book'

Posted: Tue Oct 28, 2014 3:14 pm
by Gabor
How about one of the recent enhancements in TM1 10.2.2 FP1:

WebsheetBackgroundRecalculationMode ... If set to 3, the entire current workbook is calculated ...
http://www-01.ibm.com/support/docview.w ... wg27043558

Re: 10.2 web rebuild 'current book'

Posted: Tue Oct 28, 2014 3:20 pm
by lotsaram
How is the version selected on the landing page? I assume it is a SUBNM? If you change the selection to be picklist driven (so rather than a SUBNM the cell is a DBR to a string cube with defined picklist for version to select and probably with a client dimension) then the sheet can be forced to refresh when picklist values are changed.

This approach definitely works. Whether it works though for the whole workbook or only for the active sheet though is another question. Generally it does make more sense especially in a web application to just refresh on demand so nothing is done on an inactive tab until it is selected. If it only works for the selected tab then try the new background calculation mode setting Gabor suggested. I think that using these 2 things together you should be able to get the result that you want. (However as a WARNING it is generally a good thing and by design that only what is active and visible gets refreshed, this leads to better performance. The background calculation setting is global so it will effect all websheets and could lead to significantly worse performance on the whole if your applications tend to be multi-sheet and not single sheet.)

Re: 10.2 web rebuild 'current book'

Posted: Fri Oct 31, 2014 10:27 am
by JamiseBondi
thanks to both Gabor and Lotsaram for the ideas.

gabor I tried that setting and though it looks to be exactly what I was aiming at, the change "0" to "3" didn't have the desired effect. The active forms in two different workbooks wouldn't rebuild from the menu tab requiring a rebuild on visiting each active form in the workbook. I restarted the Application Server Service and closed and re-opened the browser in checking this setting. maybe there is an additional step?
I'll take it up with IBM in the near future to see what they have to say about it.
Incidentally, in 10.2 the performance is very impressive in rebuilding all tabs on opening and the difference between this and not having the active forms populating is not noticeable at present. I'll check out a few larger forms to see the effect of this change though.

Lotsaram, appreciate the suggestion and I'm sure it'll work. With the number of instances and workbooks that would need changing from the current setup this would be a tall order when the alternative is to revert back to using a default excel named range that does the trick and is a small change. I was hoping for a global change that wouldn't require much effort and time. Thanks anyway for the tip - useful to know going forward.

To answer the question though: the version is chosen from a SUBNM which updates a named range which is used in all tabs of the workbook.

thanks guys.