Page 2 of 2

Re: Load Parent Child Hierarchies from ODBC into TM1

Posted: Wed Nov 20, 2013 5:07 pm
by kingaj12
I am a newbie to TM1. I would like to just write a process that avoids wizards altogether. Is there a way to do this?

Re: Load Parent Child Hierarchies from ODBC into TM1

Posted: Wed Nov 20, 2013 7:00 pm
by David Usherwood
Er, yes....
Set all variables coming through to other and cut your own code.

Re: Load Parent Child Hierarchies from ODBC into TM1

Posted: Wed Nov 20, 2013 7:05 pm
by kingaj12
David Usherwood wrote:Er, yes....
Set all variables coming through to other and cut your own code.
... but how do you do that without clicking a dropdown box on the wizard?

Re: Load Parent Child Hierarchies from ODBC into TM1

Posted: Wed Nov 20, 2013 9:46 pm
by Duncan P
If your process has a data-source then it will have variables, and you must set them to "Other" (manually) in order to use them. This will involve clicking drop-downs. However as some kind soul pointed out recently you can select them all and then a change to one will apply to them all, so only one drop-down interaction is required.

If your process doesn't have a data source just click on the Advanced tab and start typing in the Prolog and Epilog sections.

Re: Load Parent Child Hierarchies from ODBC into TM1

Posted: Wed Nov 20, 2013 9:58 pm
by kingaj12
Thanks Duncan P. I think that settles the matter unless some other kind soul has an idea.

Re: Load Parent Child Hierarchies from ODBC into TM1

Posted: Wed Nov 20, 2013 10:28 pm
by Alan Kirk
kingaj12 wrote:Thanks Duncan P. I think that settles the matter unless some other kind soul has an idea.
I'm not sure what the issue is with selecting the drop downs to change them to Other. You're aware that you only do it once, right? You do it when you're developing the code, you save the process, and they remain set to to other for all time unless you go into edit mode and change the data source. (Which you wouldn't normally need to do anyway; you'd set the data source dynamically by setting a value for one of the TurboIntegrator Local Variables. (Refer to the Reference Guide for details.)) It's not something that you do every time you run the code.