An issue has been identified with certain builds of TM1 software which may cause data values to be incorrectly displayed and stored when the TM1 Sandbox functionality is used in conjunction with a specific combination of TM1 rules, TM1 feeders, and access methods, as described further below.
This issue has been identified in the following versions of TM1 software:
- TM1 9.5.2
- TM1 9.5.1
- TM1 9.5.0
This issue occurs only when all the following conditions are present:
- The model contains either a STET or CONTINUE rule, and
- The model uses feeders, and
- The user is working in a Sandbox environment in any TM1 Client, and
- The user has disconnected from a session and logged back in and commits those Sandbox changes.
Using a TM1 client, a user adds or changes the value of a cell in the Sandbox environment. That user subsequently logs out of and back into the client, resuming their sandbox session. The feeder source cell must have a value in the Sandbox and the feeder target cell must not have a value in the Sandbox but the feeder target must have a non-zero value in the Base model. Upon committing the value of the new or modified cell, an entirely different area of data (cells that are not being updated at the time) will change to zero or a number that does not reflect the number which had been there previously.
This has been logged as APAR PM44770. An interim fix which resolves this issue is now available for both TM1 9.5.1 and TM1 9.5.2. This fix will also be incorporated into TM1 9.5.2 Fix Pack 1 currently scheduled to release in October, 2011.
For customers using TM1 9.5.1 or 9.5.2 we strongly recommend you apply the interim fix. To obtain the interim fix, please log a service request with Technical Support.
For customers currently on TM1 9.5.0, please use the interim workaround detailed below.
Should you have a TM1 Server with a model that meets all the conditions listed above, it is recommended that you advise your users to commit their TM1 Contributor Sandbox work in a single session rather than logging off and logging back on before committing.
The content of this Alert is based on the best-available information as of the date of its publication. While every attempt has been made to provide guidance on the known issues at the time of publication, the Alert may not describe all of the circumstances under which the issue described above may occur, and may not provide a resolution for every occurrence of the issue. We continue to work to provide a comprehensive solution. All additional information will be documented in subsequent editions of this Alert and posted on the IBM website http:/ibm.com/support.
WARNING: Failure to follow these important instructions may result in the display and storage of incorrect data values. You are responsible for implementing these changes to ensure that your system remains current with this alert. Under no circumstances is IBM or its suppliers responsible for loss of, or damage to, your data.