TM1 Forum

I've done a bit of searching around looking for a specific answer to my question but haven't found it yet.

I understand that caching and stargate views happen automatically and that the cache is wiped out on a particular cube when any data change is made within one of it's control cubes (}ElementAttributes_* for example). What I would like to know is if making data changes inside of the security control cubes affects the cache of all other cubes?

I've seen some funny stuff with caching of attributes. I think with them being essential to the system and dimensions the caching is handled slightly differently. The only way I've found to completely clear the attribute cache (without deleting anything) is to do a restart,

Jim.

Thanks Jim. I appreciate that. Another question in line with this one would be if I make changes to }CubeSecurity on the server, does the cache for every other cube get cleared?

bradleycsimpson wrote:I understand that caching and stargate views happen automatically and that the cache is wiped out on a particular cube when any data change is made within one of it's control cubes (}ElementAttributes_* for example). What I would like to know is if making data changes inside of the security control cubes affects the cache of all other cubes?

The calculation and view cache for a cube is actually wiped out when a data change is made anywhere in the cube itself or in any "upstream" cube that the cube has dependencies on. Dependencies are set by rules (either intra-cube feeders or calculations on the RHS of a rule line.) A cube does not necessarily have a dependency on the }ElementAttributes_... cubes of all its component dimensions, the dependency will only be there if rule calculated values depend on attribute values.

In addition to data changes which affect the caching only within the web of interlinked rule dependencies a meta data change (addition or removal of element or change in hierarchy structure within a dimension) will I believe invalidate the cache for ALL cubes.

Data and security are independent in TM1. So for example in the following hierarchy:
A
- A1
- A2
- A3
where leaves A1, A2 & A3 all hold a value of 10 then any user who has access to rollup A will see a value of 30, regardless whether they can see all, one or none of the leaves. (Seems like the right and sensible approach to me since a given cube cell address has only one correct value and it should be the same for everyone, but not all tools take this approach.)

So changing values in security cubes or doing a security refresh should in theory have no impact on caching - unless that is that you have cube rules which do some lookups on the security cubes in question.
(I believe as far as a security refresh goes that this *may* have changed from earlier versions, but I am assured that at least since 9.5 that security refresh will not dump the cache.)