TM1 Forum

stingo wrote: ↑Wed Jun 25, 2025 4:07 pm ...what version are you running?
...

TM1 Build Number: 11.8.02800.9 (2.0.9.20 IF2)

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

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

And now there are two of us using security overlays... In my scenario I am using rules to set the OverlayData to 1 to block intersections. Data admin can write to these intersections but a TI process that runs as a pseudo-data admin cannot and you need to apply CubeLockOverride in cases where this m...

Part 9 just added In the last part of the Introduction to MDX Views series in Planning Analytics, we look at a practical example of joining data from multiple cubes into one view. The example looks at bringing in the underlying components of an allocation model to present them in a concise view all...

That error message may also appear when the TM1 Login Server URI points to a TM1 instance that is not running/not available/wrong port etc.
Double-check that this instance is accessible from your new server: HTTPPortNumber, firewalls etc. etc.

Have a look for some guidance in this article. If you are trying to convert the value in the attribute to a member, you will need to use StrToMember() If you are trying to display the attribute in a view then you need to create a calculated member. Either way, the content in the articles should guid...

If you added the security group, why not just let it do what it should?
Sounds like you need two groups.

Have you test Trace Cell to see that they cannot see the underlying values?

To get a member from the subset try something this: That should return the first member.
Will return the second member.

Try Part 7 of my Introduction to MDX for more insights...

HI, If you are using PAfE then the documentation I referred you to is valid. The names may say Cognos but what you need to automate PAfE is detailed in those references. This has nothing to do with Cognos Automation and it is purely confusing naming again by IBM.

Start here - Should get you going with the prerequisites you need using the CognosOfficeAutomationExample.bas and CognosOfficeMessageSuppressor.cls files. Without these you will battle.

Is this not a side effect of someone attaching Performance Mangler (Modeler) to the model - sure I have seen this many times.

Best to put your calculations and rules on hold until tomorrow and take the day off.

If you don't believe me, have a look at my proof using MDX with the most basic of math to test if 3 > 1 + 2

... My understanding is that in the medium term there is an expectation that PASS will become part of PAW. ... My understanding is the TM1Web, the UI to PASS will fall away and websheets will need to be embedded into PAW. To allow PAW to render these websheets, you will need PASS running as the &qu...

I was pondering Declan's statement too and went back to Cubewise's 7 tips for writing faster rules , point 6. I have not had any cause to retest or dispute their 40% faster claim as I have seen similar results over the years. Are there edge cases we should know about or has something changed e.g. hi...

HI Maren, I tried this on PAW 2.0.101 with a reference to my User Preferences cube rather than an attribute on the }Clients dimension: WITH MEMBER [Scenario].[Scenario].[UserVersion] AS STRTOMEMBER("[Scenario].[Scenario].[" + [_S-User Preferences].( STRTOMEMBER("[}Clients].[" + U...

Yes, something like: WITH MEMBER [Version].[Version].[UserVersion] AS STRTOMEMBER("[}Clients].[" + USERNAME + "]").PROPERTIES("TestVersionA") MEMBER [Version].[Version].[Version Variance] AS STRTOMEMBER("[Version].[Version].[" + [Version].[Version].[UserVersio...

It is likely the nesting of the StrToMember

Try create another intermediate/calculated member to get the value of TestVersionA then use that in the outer StrToMember.

Have a look at this article , specifically the section showing }StatsByCube. I create the calculated member Memory per Populated Cell to give an indication of whether or not reordering dimensions may help. Over 30 could prompt further review but it is not quite that simple as each dimension needs by...