currently we are upgrading our environments from Planning Analytics (TM1) 2.0.9.15 to 2.0.9.19.
in the new version of PA (local) we are facing a changed behaviour regarding the zero suppression on string values. 
In 2.0.9.15 Views in Architect & Perspectives as well as Reports in PASSS (TM1Web) are doing a proper zero suppression on string values.
Now in 2.0.9.19 the zero suppression is also showing cells with no string value.

The behaviour is triggered when you nest dimension elements in the rows and turn on zero suppression and is triggered even when only 2 dimensions are nested.

We did not change the tm1s.cfg or anything else. So the root of this behaviour seems to be the PA (local) version.

The situation turned out to be even more curious as I was able to create a small test cube within the SData on 2.0.9.19 and I am not able to recreate the behaviour there. The config files (tm1s.cfg) between SData and our instance are using pretty much the same parameters. At least no parameter involved that indicates to be the root of this behaviour.

find below screenshots of the behaviour in view with nested rows and string measure.
one time from 2.0.9.15 - working fine & one time from 2.0.9.19 - not working

is anybody facing the same situation and is this a known issue?
would highly appreciate some help or guidance for further root cause analysis.

kind regards
Bernhard

------------------------------
Bernhard Busslehner
------------------------------

additional insights on the behaviour and the root cause.
The behaviour is related to nested dimensions including C-Elements, either in rows or columns.
The fact that SData did not show the behaviour lead us to differences within the tm1s.cfg

Turned out that the parameter "ViewConsolidationOptimization=F" was the root cause of this behaviour.
Seems there is a changed behaviour in recent PA versions. Till 2.0.9.15 there was no problem at all.
Changed the parameter to ViewConsolidationOptimization=T (default value) and now everything seems to work as expected.

Hope this update helps anybody facing the same or similar issues.

kind regards
Bernhard

------------------------------
Bernhard Busslehner
------------------------------

Thanks for closing the loop on this.

I guess most users would not have had this issue as the default is T, like you mention.

What I am trying to work out is what would the case be where ViewConsolidationOptimization needs to be set to F?

------------------------------
George Tonkin
Business Partner
MCI Consultants
Johannesburg
------------------------------

Original Message:
Sent: Wed March 06, 2024 02:31 AM
From: Bernhard Busslehner
Subject: PA 2.0.9.19 - changed behaviour in zero suppression on string values

additional insights on the behaviour and the root cause.
The behaviour is related to nested dimensions including C-Elements, either in rows or columns.
The fact that SData did not show the behaviour lead us to differences within the tm1s.cfg

Turned out that the parameter "ViewConsolidationOptimization=F" was the root cause of this behaviour.
Seems there is a changed behaviour in recent PA versions. Till 2.0.9.15 there was no problem at all.
Changed the parameter to ViewConsolidationOptimization=T (default value) and now everything seems to work as expected.

Hope this update helps anybody facing the same or similar issues.

kind regards
Bernhard

------------------------------
Bernhard Busslehner
------------------------------

Hi George,
frankly, the parameter usage was triggered by the lack of alternatives.
Our model was facing the hardware limits regarding memory but had enough spare cpu power.
As a quick fix our external partner suggested to set ViewConsolidationOptimization=F as this would reduce the "Cache".

It was a quick fix and did not impact our model - till last week.
We later handled the hardware issues but never changed the parameter back to default.

Frankly, I wrapped my head around it but was not able to find a "real need" where ViewConsolidationOptimization=F would be necessary.

kind regards
Bernhard

------------------------------
Bernhard Busslehner
------------------------------

Original Message:
Sent: Wed March 06, 2024 03:40 AM
From: George Tonkin
Subject: PA 2.0.9.19 - changed behaviour in zero suppression on string values

Thanks for closing the loop on this.

I guess most users would not have had this issue as the default is T, like you mention.

What I am trying to work out is what would the case be where ViewConsolidationOptimization needs to be set to F?

------------------------------
George Tonkin
Business Partner
MCI Consultants
Johannesburg
------------------------------


Original Message:
Sent: Wed March 06, 2024 02:31 AM
From: Bernhard Busslehner
Subject: PA 2.0.9.19 - changed behaviour in zero suppression on string values

additional insights on the behaviour and the root cause.
The behaviour is related to nested dimensions including C-Elements, either in rows or columns.
The fact that SData did not show the behaviour lead us to differences within the tm1s.cfg

Turned out that the parameter "ViewConsolidationOptimization=F" was the root cause of this behaviour.
Seems there is a changed behaviour in recent PA versions. Till 2.0.9.15 there was no problem at all.
Changed the parameter to ViewConsolidationOptimization=T (default value) and now everything seems to work as expected.

Hope this update helps anybody facing the same or similar issues.

kind regards
Bernhard

------------------------------
Bernhard Busslehner

I would put my money on

https://www.ibm.com/support/pages/apar/PH54510

This was a fix for a problem I reported (and posted here some months back) which had to do with settings of 2 config settings. It was caused by a fix in .15 or .16 if I recall corelrectly   If my hunch is correct I would say that the correction in .19 caused different problems. I was due to test this issue rectification in the coming days....

------------------------------
John O'Leary
------------------------------