TM1 Forum

Further testing: • a chore that runs a TI process can write without issue, when the chore runs on a schedule • a chore that runs a TI process, when the chore is run by a particular user, will run with the security rights of that user So you can you summarize: - what do you see in your environment? ...

What I observe in my tests is: • a user in the ADMIN or DATATADMIN group can write to the overlay security locked cell • a user not in the ADMIN and not in the DATATADMIN group cannot to the overlay security locked cell • a user in the ADMIN or DATATADMIN group can run a TI that writes to the overl...

For my 2 cents, it works for me. The GIF should demonstrate how I use the overlays to block off scenarios e.g. snapshots and periods on the rolling forecast that are not relevant and should not be input. My overlay cube for the demo only has two dimensions: Scenario and Period. Essentially when I b...

guys I know that I need to put logics to avoid writing on closed months and as I already mentioned, I am not catering for the 99% of TIs that are written good, I am trying to cater for the next 1%. I have hundreds of TIs in the system and I don't have the time (as it is not the focus of my project) ...

What's your actual requirement? I never in 25 years so far working with TM1 found something that can't be solved with cell security. I see no need for the overlay cubes TBH. sorry went radio silent. the idea is that I have hundreds of TI on the server and I want to avoid people to run a perfectly w...

if you have a better idea, be my guest.

just for the records.

I queried IBM and they confirmed that I am not losing my mind, TIs are not impacted by the layer.
essentially it is an useless feature as you can just put the cell on read.

Try adding a rule with the following: ['OverlayData']=S:'1'; That should block all input across the defined dimensions, assuming no admin user. On PAoC, ensure the test user is not a subscription admin or similar too (CAMID groups). I tried via rules. I tried via TI. The Overlay is 1. I can write w...

I removed the data admin status from the account but it is still an highway, I can write, clean, rewrite etc.

I would like to lock cells to everyone but this is not really working.

I am an admin but I have an account that is data admin too.
I removed the data admin status on the account and assigned it to some random groups and still no cigar.
I can still write and clean with the no more data admin account.

Is there a piece of knowledge I am missing? am I getting crazy? I am trying to create a security overlay cube in my PnL cube ('PA on cloud'). I am creating the cube with the appropriate mapping (in a security TI). Then I apply SecurityOverlayCreateGlobalDefault ('Profit and Loss', '1:1:0:0:0:0:0:0:0...

kangkc wrote: ↑Wed Jan 17, 2018 10:24 am Rest API Port via the parameter :
HTTPPortNumber

If not specified, default is 5001 (PA 2.x), hence conflict.

Gotcha!

Thanks a lot.

Hi, In the last 10 years, whenever I wanted to put 2 TM1 instances on the same server (say Dev and Test), I used 1 gold rule: Change the port number/ client message port number and everything will work. The golden rule worked till today. Now I am probably ignoring something basic but this is the sit...

To answer your question: a TM1 server crash can never be explained away as 'by design', it's always a defect. Assuming, of course, that you had an actual server crash. On your version, provided you don't have AutomaticallyAddCubeDependencies=F, dependencies should be detected and added automaticall...

Hi, so as far as I know. the dependency between cubes is changed when: System restarts Rules are saved/recalc feeders a view is opened Now I have this case. 9480 [1a4] INFO 2015-09-29 09:10:43.447 TM1.Server TM1CubeImpl::ProcessFeeders: Computing feeders for base cube 'cube 1'. 9480 [1a4] INFO 2015-...

silw wrote:

qml wrote: log4j.logger.TM1.Lock.Exception is safe in that respect.

From 10.2.2.4 Fix list:
PI42411: TM1 SERVER CRASH WITH TM1.LOCK.EXCEPTION ON

ok... maybe I should wait for the patch to be installed then...

just a last question before putting the brain at work, will the debug on the log properties degrade the performance a lot? Not the one I suggested. It should produce very little additional output: basically one line for every encountered lock conflict. If you switch on a bunch of verbose loggers li...

After I played with TM1 for a while trying to achieve my goal, I personally think TM1 is just in demo stage, not supposed to be sold as commercial product. Even with 10.2, the fact is still the same. There are too many defects in any steps (problems exist every where from top to bottom). How do you...

integratedsecuritymode 5 integrated login That is a very important piece of information. CAM logons seem to cause more locking than native logons, I imagine mostly due to the fact that users' security needs to be updated. The logger should tell you what objects you're getting locks on and we can ta...

Wat's your IntegratedSecurityMode? integratedsecuritymode 5 integrated login Have you tried switching on lock exception logging in tm1s-log.properties? log4j.logger.TM1.Lock.Exception=DEBUG Have you tried the following config parameter? It is meant to prevent locks on logoff, but maybe it could hel...