TM1 Forum

You do realise that generally speaking a TI script doing that in some other TM1 model would not work in your model? You can try and write this script yourself as it's the most basic of tasks for which TI can be used. If you don't feel you have enough skills for that then you probably should think of...

You need to switch on Security Access for the process(es) that attempt to make any security changes. More on the subject here: http://publib.boulder.ibm.com/infocenter/ctm1/v9r4m1/index.jsp?topic=/com.ibm.swg.im.cognos.tm1_dg_dvlpr.9.4.1.doc/tm1_dg_dvlpr_id7301AllowingProcessestoModifySecurityDat.ht...

... or put " > C:\myfile.txt" at the end of your command to print anything the OS says to a text file.

It is all described in the TM1 Rules Guide.

You should do something along these lines:

The best approach is to create a Dynamic Subset with the following MDX code This subset will not need any maintenance, it will always be automatically up to date.

You can also consider creating a TI Process that would be called from your VBA for every data line (or column or cell etc), take the data you want to write to the cube (and all dimension elements too) passed as parameters and the actual writing to the cube can be done by the TI. I have employed this...

There are a number of ways to achieve that, the simplest one not even requiring a macro, just a flag cell and DBS formulas (maybe somewhere in a hidden area. Like that: =IF(FlagCell=1,DBS(...),0). The user would submit data by changing the flag value (manually, using a button, from a dropdown etc) a...

I can't remember right now, but if you just delete the }ClientProperties cube, would that still erase all the users from the server? This should be enough to zero out all the passwords.

I can't see any code that would remove / rebuild the cube, so it must be something else. Maybe you can go through your other chores/processes and search for anything like I really can't think of anything else right now.

Just a stab in the dark here, but maybe you are facing the problem of circular reference? TM1 would display the same error message (which does not help much!) if you tried to spread, say, a value from a parent to its child. Check if your reference element is not a parent of your target element.

How many active chores do you have in your model? Is it possible for you to go through them and list all the processes involved? If there aren't too many, you could post the code in the Prolog, Metadata, Data and Epilog tabs of these processes so that we can help you pinpoint which other process del...

It looks like the cube PROD_MARZE gets deleted outside of your process, so that when it gets executed it cannot find it and falls over on the first line of code. Are you aware of any other process in your environment that would be deleting this cube periodically?

But till now I was sure I had such an issue in one of former versions (definitely before 9.5), so I tried those days to type the aliases manually in the }ElementAttributes cube and they were there only till server restarting. After that they came back to blank. Now I am not so sure about it. On 9.5...

Steve, You only need to feed your string cube (and security cubes are string cubes) if you use SKIPCHECK and you want to work with zero-supressed views. I wonder why you might need it in the first place. I would just write such rules with no SKIPCHECK and no FEEDSTRINGS and no FEEDERS. And yes, you ...

Just a stab in the dark here... Since you can refer to your subset when you already have it defined using the [dim_name].[subset_name] formula, how about trying to create a few nested subsets, making use of one another, sth along the lines of: {UNION( {[dim_name].[subset1]}, {[dim_name].[subset2]} )...