RuleLoadFromFile & RuleSaveToFile

[Steve Vincent]

We have RuleLoadFromFile , why not RuleSaveToFile?

The only time i have come across the need to load rules from a file is when i want to avoid them slowing down dataloads via TI. Most people manage rules in server explorer, but to turn them off, load data then turn back on you need to keep a backup copy of the original rules. This means you end up with multiple copies of the rule file and the chance to get them out of sync.

Being able to save the existing rules first to a location of your choosing would make the existing function so much more ... functional.

[Gregor Koch]

Agree, that it would be a useful function but it is also very easily done with ExecuteCommand and a batch file.

[jim wood]

I agree Gregor you can do it this way but the the 2 format lines at the top of the RUX file make life a little more difficult. Havinf this command would help keep any rule editing within Architect in line with any source files easily,

Jim.

[Gregor Koch]

Not sure what you mean as I only see one line:

Code: Select all

FORMAT==100

and that one gets copied fine with the batch and gets copied back with the existing ruleload command.

[jim wood]

That's the line I mean't. Did I say 2..........

[Harvey]

How about SubsetGetMDX, or many other functions to interrogate the properties of subsets and views? I understand that the focus of TI is on creating new objects, as opposed to reading existing ones, but I agree it would be nice if it had a more complete API.

I recently developed a solution for this, called the Flow TM1 API Console. It allows you to get pretty much any property from a TM1 server and have it returned to a TI process. This will eventually be one of the free tools that Flow partners get access to, and I think it'll turn out to be quite handy.

It's in beta right now, so wouldn't be appropriate for production use, but I'd be happy to let a few members play with it.