TM1 Forum

Good Morning/Afternoon All,

I am in the process of creating a new cube, which will replace one that contains fewer dimensions, etc. Before I make the switch from CUBE123 to CUBE456 I want to ensure that all processes, TI processes, rules, security, etc., have been migrated to the new cube. Is there an easy way to search all processes, rule files, etc., to identify all references or is this a tedious manual effort?

Thank you advance,
Michael

Hi,

You could open notepad++ and search for the old cube name in the data directory .pro and .rux files. Or you could use the powershell Select-String and output to text file, e.g.:
for rules just replace .pro with .rux in the above

Not sure about the etc's though!

Maren

Or commercial tools such as Qubedocs. Note: I have no advantage of or links with, Qubedocs.

Or roll your own solution by using a TI process to read the PRO and RUX files, etc. Or develop a solution using the TM1 REST API. tm1py has some support for this task at hand.

Hi,

There is a very old but working parser written on perl: https://www.bihints.com/graphing_tm1_data_flow

Wim Gielis wrote: ↑Thu Jul 06, 2023 6:12 pm Or commercial tools such as Qubedocs. Note: I have no advantage of or links with, Qubedocs.

Or roll your own solution by using a TI process to read the PRO and RUX files, etc. Or develop a solution using the TM1 REST API. tm1py has some support for this task at hand.

Or commercial tools such as Pulse. Note: I do have an association with Pulse.

Another way is to use Debug utility 123 (all the usual exclusions and waivers apply when using undocumented features)

Extracts a file with information about all cubes and dimensions

So in short given the following:
DebugUtility( 123, A, B, 'Model_Information_0_1.txt', '', '' );

A = 1 suppresses control objects
B = 1 includes additional feeder/cell information

At the end, for each cube you will see its dependencies to other cubes and vice versa. Includes attributes etc. too.

TM1py has search_for_rule_substring and search_for_string_in_code

Thank you all for the suggestions. I am just finishing up month-end, but will pivot to development efforts shortly.

I greatly appreciate it!

Michael