TM1 applications and uncommitted sandbox data
Posted: Tue Jan 15, 2019 7:59 am
Hey all,
I'm running into some issues with sandboxes and tm1 applications and I'm wondering if anyone has some insight regarding this situation.
What is causing the problem:
• User A uses Tm1 application to update forceast figures for november (during november 2018), but doesn't commit, figures remain blue.
• It's now december 2018 and november has changed from a forecast month to an actual month. CellSecurity locks data entry for actual months.
• User A updates forecast figures for december (during december 2018) and uses commit to add them to the base model.
• However, the data doesn't commit and the tm1server log notices an error because it is trying to commit the november and december data from the sandbox to the base model which is now locked (for november) by CellSecurity.
• This means that none of the data in the sandbox gets committed to the base model.
Ultimately the user should have committed their november data during november and then there wouldn't be any issues. However, these issues seem to occur every once in a while.
I tried removing sandboxes (to start with a clean slate next period) during periods where people do not use the application but noticed that I couldn't identify/remove sandboxes of users who weren't logged in since the reboot of the model.
Ultimately I'm looking for a solution to the problem where 'old' uncommitted data can be automatically cleared before a new cycle of data input starts.
Please let me know if you have any suggestions.
Kind regards,
I'm running into some issues with sandboxes and tm1 applications and I'm wondering if anyone has some insight regarding this situation.
What is causing the problem:
• User A uses Tm1 application to update forceast figures for november (during november 2018), but doesn't commit, figures remain blue.
• It's now december 2018 and november has changed from a forecast month to an actual month. CellSecurity locks data entry for actual months.
• User A updates forecast figures for december (during december 2018) and uses commit to add them to the base model.
• However, the data doesn't commit and the tm1server log notices an error because it is trying to commit the november and december data from the sandbox to the base model which is now locked (for november) by CellSecurity.
• This means that none of the data in the sandbox gets committed to the base model.
Ultimately the user should have committed their november data during november and then there wouldn't be any issues. However, these issues seem to occur every once in a while.
I tried removing sandboxes (to start with a clean slate next period) during periods where people do not use the application but noticed that I couldn't identify/remove sandboxes of users who weren't logged in since the reboot of the model.
Ultimately I'm looking for a solution to the problem where 'old' uncommitted data can be automatically cleared before a new cycle of data input starts.
Please let me know if you have any suggestions.
Kind regards,