TM1 Forum

I have a client who is using TM1 Contributor for data entry purposes, but does not want to allow the user to spread data down a dimension hierarchy from a Total to the base (level 0) elements.
I have attempted to use element security to give the user READ access at the Total level. However, this does not block the user from using the Spreading Tool at the Total (consolidated) level.
Hiding or deleting the Total element is not an option since it needs to be visable and usable for the string measures.
I have not attempted cell level security, but I expect that will have the same outcome since element level security does not work.
Do you know of a way to disallow the users from using the Spread Method Tool?

Thank you for any input you can provide.

You should look into the Contributor config file. I think you may be able to stop the spreading capability there. Of course, that's going to preclude spreading on all the views, not just this particular scenario.

Thanks Tomok.

I looked in both pmpsvc_config.xml (doc in pmpsvc_config.xsd) and the Ops manual Chapter 2: TM1 System, Parameters in the Tm1s.cfg file (TM1 v9.5.2 SP1). The closest I come is the Spreading Precision parameter.
Good idea, its just not there as an exposed control can that I can find. If you know where to find this, please let me know.
Thanks again!

Christopher Redmond

Hi Chris,

After re-reading your question are you saying you want to disable the right-click spreading menu itself? (which I don't think is possible) Or that you think there is a bug with Contributor not respecting element security when spreading?

Assuming its the later:

Have you double-checked the obvious? e.g. are you 100% sure that the user is not a member of another group that gives write access to the "total" element and therefore the effective security level is write and not read? Have you checked that this is indeed specific to Contributor and it isn't possible to spread in am excel sheet or cube view?

I don't have any particular experience with whether element security is quirky in Contributor but I have used the approach of setting element security to read on consolidated elements to disable spreading in the past where this was a requirement for the model and it certainly works as expected in perspectives, and TM1Web cube views and websheets. If you have verified that this is specific to Contributor and works as you want in Excel and TM1 web then I would think of such inconsistent behavior as a bug.

I know this sounds like a lot of work, but is it feasible for you to have the normal hierarchy (up which natural consolidation takes place) hidden and then have a visible matching hierarchy for which the values are specified by a rule pulling from the corresponding hidden items. The spreading menu would still be available but if they try to spread from the calculated totals they will get the message "Spreading operation has failed because the contents of the cells cannot be modified".

Duncan P wrote:I know this sounds like a lot of work, but is it feasible for you to have the normal hierarchy (up which natural consolidation takes place) hidden and then have a visible matching hierarchy for which the values are specified by a rule pulling from the corresponding hidden items. The spreading menu would still be available but if they try to spread from the calculated totals they will get the message "Spreading operation has failed because the contents of the cells cannot be modified".

Thanks for the suggestion Duncan.
I think I am too far down the path on the project for the client to agree to a redesign of the cube. I have been explaing to them from the beginning that the Spreading Method is inherent to the product and I didn't anticipate the possiblity of blocking this feature.
I'll keep your idea in mind in case I don't find a simpler solution and they continue to push on this issue.

Thanks again!

lotsaram wrote:Hi Chris,

After re-reading your question are you saying you want to disable the right-click spreading menu itself? (which I don't think is possible) Or that you think there is a bug with Contributor not respecting element security when spreading?

Assuming its the later:

Have you double-checked the obvious? e.g. are you 100% sure that the user is not a member of another group that gives write access to the "total" element and therefore the effective security level is write and not read? Have you checked that this is indeed specific to Contributor and it isn't possible to spread in am excel sheet or cube view?

I don't have any particular experience with whether element security is quirky in Contributor but I have used the approach of setting element security to read on consolidated elements to disable spreading in the past where this was a requirement for the model and it certainly works as expected in perspectives, and TM1Web cube views and websheets. If you have verified that this is specific to Contributor and works as you want in Excel and TM1 web then I would think of such inconsistent behavior as a bug.

Lotsaram,
Tanks for the ideas. You bring up some interesting points.
So far, I have had a different experience than you describe. I find the Contributor and Perspectives/Architect behaior to be the same. The security I am applying is only on the CAM groups, not the }tp_ groups. I am applying READ access across the board on all CAM groups including 'Everyone' for the consolidated element. This behavior may be by design since the groups do have WRITE access at the leaf level. I would be interested in hearing the specifics on how you were able to block it with security. On the surface, it sounds like the same approach as I am using.