Websheet paging and hidden lines

[mvaspal]

Hi

We are using Action Buttons for running TIs and a few SUBNM, and DBR for title elements. sometimes one DBR formula is referenced by a hidden cell, then another non-hidden DBR cell references this hidden one. So, all these objects are referencing from and to hidden cells. For example, user selects customer, it is manipulated with an excel formula in a hidden cell and an action button uses it as a TI parameter. The websheet calculation is set to automatic. everything is working fine in Excel and TM1Web.

Then we set websheetpaging to true, allowing 80 lines and pageresetmode to 3. Excel still working fine but seems that on the web, hidden cells remain blank even after a user selects a value for a non-hidden cell and this cell is referenced by a hidden cell. And so all of the TIs are failing, etc. I will still try to put a rebuild button on the sheet whether it has any affect but still I would not like to put those buttons on all 50 sheets, not really user firendly.

Has anybody face this problem earlier? Version 9.5.2.

Thanks for your contributions.

Matyas

[lotsaram]

I think we came across this using 9.5.2. It is a bug where hidden cells get calculated only when the websheet is first opened and on subsequent refreshes the values don't get updated. Our use case was pretty similar to yours (assistance with capturing navigation parameters). I can't recall if we reported it or not so there may be an existing APAR. In any case we decided not to wait for a fix from IBM and worked around it by moving the cells to a visible section of the worksheet and "hiding" by formatting the font to background colour. Not the solution we would have preferred but it works.

[mvaspal]

Hi

Thanks a lot for this. I was a bit afraid of that as it is clearly reproducable - when I hide the rows it does not work, when I unhide them, it works. Redesigning at least 20 out of the 50 websheets seems to be a bit painful for me.
Thanks again
Matyas

[mvaspal]

And it seems that even sheet rebuild does not help.

[mvaspal]

Thank you for your input lotsaram, we reported it to IBM and it is being managed under the APAR reference PM48748 at the moment.