TM1 Forum

Hi All,

We provide "Data Source Name", when select ODBC as "Data Source Type".
In screenshot we have ML_DHDB_QA, I need to get automatically same name in prolog/epilog.
If any more information is required, please let me know.

Regards,
Deepak Jain

Please have a look at the available TI functions and variables.
You will end up with the information such as specified here:
http://www.tm1forum.com/viewtopic.php?f ... 429#p57429

Hi Wim,

I went through scenario, and kept in mind to have as proposal. If we don't have anything direct. We can have a lookup cube.
We are having multiple environments, but ODBC connection names are different in environments.

When we are having migration from one environment to another, we are forced to change ODBC, lookup cube will help as mentioned. But we are not having anything like lookup for now.

Business requirement is, if we are having incorrect ODBC, it should pop-up an error message in TM1Web.

I want to know, do we have anything which helps directly.
For example to get TI process name, we give getProcessName(). Hope IBM come with something getDataSourceNameForServer.

Regards,
Deepak Jain

deepakjain2020 wrote:Hi Wim,

I went through scenario, and kept in mind to have as proposal. If we don't have anything direct. We can have a lookup cube.
We are having multiple environments, but ODBC connection names are different in environments.

When we are having migration from one environment to another, we are forced to change ODBC, lookup cube will help as mentioned. But we are not having anything like lookup for now.

Regardless of how the "Business" feels about it, the ONLY two ways I know how to accomplish what you want is to either utilize a lookup cube or make the ODBC connection a parameter and let the user provide that every time the TI is run.

deepakjain2020 wrote:Business requirement is, if we are having incorrect ODBC, it should pop-up an error message in TM1Web.

TM1 doesn't do this natively. The only way I know to do this is to, guess what, have a lookup cube, compare the user provided ODBC string against the lookup cube, and do a ProcessQuit if they don't match.

Hi Tomok,

We have very few TI process which access ODBC, with no user having view to it.
We have decided to have same ODBC name across environments.

Thanks for valuable comments.

Regards,
Deepak Jain

deepakjain2020 wrote:We have very few TI process which access ODBC, with no user having view to it.
We have decided to have same ODBC name across environments.

That's fine for me and keeps it clean and simple.
The solution with a lookup cube is a good one too.
Feel free to use what suits you best.