TM1 Forum

Don't mind me, a bit more Googling led me to this: https://www.ibm.com/docs/en/planning-analytics/2.0.0?topic=report-change-cube-datasource-custom-reports Also this: https://quebit.com/askquebit/dynamic-planning-analytics-server-names-in-pax/ Posted here in case anyone else has the same problem.

I have some PAX reports that were built from cube views in Dev. The model built in Dev has now gone live into Prod. Do I have to completely redo my PAX reports, or is there anything I can edit to repoint the links from within the same files? (I suspect I know the answer to this, but optimism never h...

Interesting, thank you. I'll have to have a play with that.

And I guess I could make the cube rule conditional on the value of the Model Environment...

ETA: not quite the same thing as a security cube?

I have a process called from PASS with three input parameters, where the user selects different versions of the TB: Select current year budget version Select current year actuals version Select next year budget version I also have a separate model environment cube where the user can specify whether ...

Yes, TM1 Web (although PASS isn't a term I've come across before... has something rebranded?) Using element security is an interesting idea, I'll have to try it out. I am trying to display the top and bottom levels of a three tier hierarchy so I would just need to make sure that hiding the middle pa...

Tm1RPTROW in PAfE has a parameter that you can use to suppress drilling on consolidated elements.

Is anyone aware of an equivalent setting (or MDX that would achieve the same result) in a standard websheet cube view, please?

Hi both, thank you for your replies. I meant to come back to this today but nothing went to plan. And I'm now on leave until July so I will need to hold that thought for ten days...

I have a dynamic subset that is defined in the set editor using MDX, and I have created a subset calculation in a cube view to aggregate over this subset. If I click on the MDX View, I can see the code that has been used to create the calculation. For reference, the subset definition is EXCEPT(FILTE...

gtonkin wrote: ↑Fri Jan 20, 2023 9:02 am (AFAIK TM1Set only supported on local)

Well *that's* annoying.

Thought I'd update this just in case anyone is looking for similar guidance in the future. I never did get my code to work and our consultants weren't able to offer any insight. So I gave up on that approach and instead just used the dimension (leaves) as my data source, grabbing the new parents usi...

my advice would be to learn how to use bedrock Thanks. Unfortunately I have exactly zero chance of getting it installed (large public sector org with mountains of red tape). I'm also only on this project for the next four months before my secondment ends, which is really annoying but it is what it ...

Oh I understand while loops in principle, just working out which exact task you meant I should loop. Be interesting to see the HierarchyCreate Code for these directorates (pDir) Prolog: vCount=1; IF(HierarchyExists('FOR_Nominal', pDir)=1); HierarchyDeleteAllElements('FOR_Nominal', pDir ); ELSE; Hier...

@gtonkin they're not as random as they might seem "pDir" is the name of the Directorate entered as a parameter. Multiple alternate hierarchies will be created, one for each Directorate. "vNom" are the nominal codes which are leaves of the original dimension in the source cube, an...

Good points, @Maren - but I was following the conventions set out by our software developer consultant (who we are no longer getting help from) and they haven't thrown up issues before. I'm now working on the Metadata and plan to go back to the Prolog later. Parameter 'pDir' defines the name of the ...

Ah, thanks @ascheeval. Good to know that it worked for you. I wonder whether it's something in the configuration of our specific system. I'll have a look at bedrock. Theoretically there's even a dedicated TI function - CreateHierarchyByAttribute() . But a bit of Googling suggested it was too buggy t...

Hi, I am trying to write a TI process that creates an alternate hierarchy within a dimension using attributes as parents. (dimension name = 'FOR_Nominal') I was taught that when you are transferring data between cubes, you should always create and refresh a "dummy view" of the source data ...