TM1 Forum

Correct. Chores should run from static cube values. They will not be stopped in case someone puts in a wrong value. That’s a responsibility for users. At least the manual runs are protected. If you want to have chores protected than take out the time to add validation code in the Prolog tabs.

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 overla...

True. You can (and should) build such a mechanism yourself. Even better would be a generic TI that is called and returns the outcome (based on the parameter values, user (or chore), "area" (what type of process is run) and any other logic needed to decide: continue or not. That way, your h...

And that is why only you and George are using the feature….

You’re welcome

Are there cube links through rules ?

Hi, Thank you for your information. How can I reference a cell or cube in the action button? Do i do it in the field provided by adding a formula or some kind of reference? if so, how? Appreciate your response Since you are using the Excel add-in, the action button parameter references can also poi...

Hi Wim, Thank you for your response. Yes, I have a Calendar cube with the different fiscal periods. Could you provide the step by step on how I can do it, please? where exactly can I reference the cube and where should I inpute the cellgets? Many thanks Hello, Do you have a system cube of some sort...

Cross-posted here for a wider audience:

https://community.ibm.com/community/use ... 4eda43146b

Hello all, Here is some code related to dates and times: DatasourceASCIIQuoteCharacter = ''; n = Now; sNow = Timst( n, '\d-\m-\Y \h:\i:\s' ); ASCIIOutput( 'test.txt', sNow ); i = NewDateFormatter( 'nl_BE', 'Europe/Brussels', '', '', 'datetime' ); v = FormatDate( n, 'EEEE dd MMMM y - H:mm', i ); ASCI...

Hello, Do you have a system cube of some sort, to collect parameters like the current fiscal period and year that are being worked on in finance ? Or parameters in that cube to hold file paths and folder structures. Or an ODBC user and password. Etc. That cube could be manual input by the key user, ...

As an example call, use: NumericGlobalVariable( 'nErrors' ); StringGlobalVariable( 'vObject_Name' ); cCube = 'Prm_Init'; vObject_Name = 'Drill_Details (%u% at %t%)'; # Create the drill object (the order of subsets is retained) nErrors = nErrors + ExecuteProcess( 'WG_DRILL_cube_view_drill_setup', 'pC...

Hello, I was able to script a drill-through to a cube view: https://tm1forum.com/viewtopic.php?p=84403#p84403 Have a look there to download the generic process and look at the examples of how to call it. Bedrock is underpinning the new process so you need (at least some of) the Bedrock TI processes....

Fast forward to Q2 2025 and this seems to be fully working. [Still waiting for drills to MDX views though.] I can get a fully dynamic target view without any other action by the user :-) but there is a but (the same but as 5 years ago, not coincidentally since TM1 server did not change here). I wrot...

Why don’t you use that cube and fill it out appropriately? Or should anyone be able to see all dimensions ? (Even if cube security is in place and/or an interface is used)

Saving a subset should also save the alias or principal name choice.

E_PICK was removed from PAfE.

I am very sorry but I don't understand it.
A few pictures might make it clearer.

Do you know who is the author of the process ? Do you know whether it was found online (can you Google some parts of the script maybe) ?

I have the impression that it was custom built for you and that an extension does not exist/should be written by you or someone else.