Is there a possibility of directly setting a range of numbers a user can enter at the time of entering an amount, something like data validation in Excel? Specifically, users need write permissions on the consolidated element, and we have received a request to prevent the entry of zero on the consolidated element, as the user could then enter an amount that would be mistakenly distributed to all children and cause memory problems. Additionally, we have received a request to prohibit the entry of a number less than zero at certain intersections. We are using PAW version 2.0.83. Thank you in advance for your help and response.

------------------------------
Tina Korinčić
------------------------------

Hi,

First, the parameter ProportionSpreadToZeroCells in the tm1s.cfg file, which is enabled by default, will execute an equal spread to all leaves of any consolidation, if all of them are empty. You can turn it to false, but it will affect all the cubes in the database.

Then, maybe you can set additional "mirror" members in your dimension, or a "mirror" cube, to allow user capture, and perform the validations with the proper rules and then copy those validated values to the main elements only if them are valid. Moreover, you may set up an additional cube to define your validation ranges, like minimum or maximum.

Best regards.

------------------------------
Jose Luis Senas
Data Analyst
Kimberly-Clark Mexico
Mexico City
------------------------------

Dear Jose,

Thank you very much for the response. We will check how disabling the parameter would impact the entire model and whether it would be okay to disable it. If not, we will go with one of the workaround options you suggested.

Best regards,

Tina

------------------------------
Tina Korinčić
------------------------------

Original Message:
Sent: Wed April 24, 2024 11:47 AM
From: Jose Luis Señas Cuesta
Subject: Data validation in PAW

Hi,

First, the parameter ProportionSpreadToZeroCells in the tm1s.cfg file, which is enabled by default, will execute an equal spread to all leaves of any consolidation, if all of them are empty. You can turn it to false, but it will affect all the cubes in the database.

Then, maybe you can set additional "mirror" members in your dimension, or a "mirror" cube, to allow user capture, and perform the validations with the proper rules and then copy those validated values to the main elements only if them are valid. Moreover, you may set up an additional cube to define your validation ranges, like minimum or maximum.

Best regards.

------------------------------
Jose Luis Senas
Data Analyst
Kimberly-Clark Mexico
Mexico City
------------------------------

Data validation is usually done with PickLists in TM1:

https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=dimensions-pick-lists

------------------------------
Matthias Mazaj
PM Factory
Vienna
------------------------------