What I understand from your post is that, a massive data is deleted by the user. I means user is overwriting the data.
This not because of any bug with TM1,
It is only because your excel in which you are using DBS and DBSS function is not properly placed and mapped to particular cell.
harrytm1 wrote:Hi all,
Wish to check if you have experienced the following bug which happened recently.
We have a budgeting model with HR, Capex, Profit and Loss and Balance Sheet cubes etc. The number of users accessing TM1 concurrently can be as high as 20 or more as they are using it for budget submission. The total user base is more than 50 contributors. It is currently on TM1 version 9.5.2 FP2.
The main methods of submission are through DBSend templates and data spreading in cube views.
It was reported that massive amount of data was missing across multiple cubes such as Headcount, New Capex, P&L. It spans not only to the budget version that they are using now, but also on actuals.
We looked t the transaction logs and found that data was deleted (both numeric and string) in several cubes at the exact same time by one User ID. This user belongs to an User Group that has access to the affected cubes and he was using DBSend templates to send capex data just seconds before that.
From the logs, his ID was writing data in the New Capex cube and then suddenly, at the same timestamp, it began to clear both numeric and string data in the same cube, as well as other cubes. Obviously, he couldn't have physically done so as there are more than 600 thousands of transactions under his ID at exact same time.
We still couldn't find the cause the triggered this mass data deletion event. In the end, we had to painstakingly use the "Backout" function in Transaction Query GUI to restore the deleted data batch by batch.
Has anyone experienced similar issue in 9.5.2 FP2 or even 10.1/10.2 versions? Any idea if this was fixed in later version, especially 10.2? I couldn't find this bug in the fix lists unless I missed it. I will push for an upgrade to 10.2 if it is confirmed that it is fixed in 10.2.
We are at wit's end, so any suggestion and advice will be greatly appreciated! Many thanks in advance!
harry