Contributor View issue

[cdhodge2002]

So I have a view that I have out on contributor. It is an all encompassing view that has Months and Measures in the columns of the view. The client is requesting that in the current month they be able to see all the measures, but the in the proceeding month they only want to see one of the measure. These measures are for data entry. In the model I designate the current month in the model and I am attempting to use cell security to control what is seen but I am having no luck. This is a data entry cube so I can not use zero suppress to control what is seen. I am sure someone has experienced this before, does any body have any advice on how to do this? It would be easy in a websheet but it is not in contributor.

[standtrue]

If someone knows how to create an asymmetric cube view I'd love to hear it...frustrating to have it available in EV but not TM1's own adhoc views.

What we've usually done is create a new cube with a hybrid time/measure dimension with the appropriate combinations as leaf elements.

In TM1 10.1 you can use websheets in your "Contributor" applications, though that probably doesn't help you right now

[cdhodge2002]

Yes 10.1 would solve all my issues, but that is out of the question.

[declanr]

Another option would be to go the websheet route but build an approval hierarchy into your model manually.

It might seem like a bit of work for you now if you already have a working model but for myself it has always been the starting point as opposed to using contributor, mainly due to the flexibility offered by websheets that isn't available in contributor.

Or at least it wasn't until 10.1 and despite some unusual behaviour I have noticed with "websheet contributor" I suppose they will be the route I now go with on occasion.

[cdhodge2002]

Unfortunately websheets are out of the question, we are in the middle of UAT and a view change request came in.

[declanr]

Unfortunately websheets are out of the question, we are in the middle of UAT and a view change request came in.

In that case I think your main options would be:

1/ Just explain that is the way it has to be (My Favourite)

2/ Build an intermediate cube for data entry that is the same as your existing cube but has 1 dimension which is a consolidation of Period & Measure.
Use that cube for the users to enter data into and via a subset you can show all the measures for current month and then only the one measure for subsequent months.
Then rule drive these values across to the main cube.

[PlanningDev]

Not sure if this was stated but you could separate the current month and proceeding month into two different views. This way you could have all measures underneath current month and only the one measure in the proceeding month. Unfortunately I dont think its possible to get what you want in one view without going the route "declanr" layed out.