Differing Views of Committed Data

[MSidat]

Hi All.

Came across a weird issue using TM1 Applications/Contributor/whatever its called now.

We are using CX 10.2.1 and have a user who has gone into a L2 Department in the approval hierarchy to view a websheet of data. Some data points are highlighted in blue denoting uncommitted data somewhere further down the same hierarchy.

The same user within the websheet selects the dropdown of the department hierarchy and selects a L1 Department (in the same sub Hierarchy as the previously selected L2) Again in this view the same series of data cells are highlighted in blue.

However when the user closes the websheet and goes back to the approval hierarchy and clicks directly into the L1 Department the websheet contains all committed numbers (in Black) which are different to the previous view when the websheet was opened by first selecting a L2 then the L1 from within the sheet.

I cant seem to recreate it and only have screenshots as proof of what has happened. A different user with rights to the whole department hierarchy could also see this behaviour. Which resolved it self by clicking on Reset Tab and Views.

Anyone come across this before? and have any reasonable explanation for this behaviour

[PlanningDev]

Not sure if this is the same behavior but a while back we came across something like this.

Essentially if you click into an application at a subtotal level on the approval hierarchy you get a sandbox for that instance of data. You can perform some work and leave it in blue (uncommitted etc.)

Now if you subsequently exited and went back into the application but this time by clicking directly on a single element of the approval hierarchy that also happened to be in the same subtotal you were in previously, you would get a new sandbox for only that element.

What it created was data stored in two different sandboxes for the same elements which made it appear as if you were looking at different data. Never got a resolution from IBM on how the sandboxes could be synced since they are essentially hidden from the user and there was no functionality built in to Applications that would do it.

[MSidat]

Thanks,

It looks like it could be the same issue. Ill do some more testing in dev, hoping to upgrade production to 10.2.2 fp4 soon so will need to test in that environment as well. I cant see a reason why anyone would want this kind of functionality where a user potentially has 2 "default" sandboxes for different levels.

[Edward Stuart]

We've seen issues similar to this as well, the following is available in the Applications Guide but how relevant it is to this issue I am not sure

In TM1 Application Web , you must submit all nodes at the level at which you
take ownership and you can only release ownership at the level you have taken
ownership. For example, if you have taken ownership of a parent node, then
decided that you wanted to submit a child node individually, you would first have
to Release your ownership of the parent node, then take ownership of the child
node in order to submit only the child node. You could then Release ownership of
the child node and re-take ownership of the parent node.

We are seeing bigger issues when data is uncommitted and we roll the model forward