Is there any way or functions available for error handling in TM1's TI process?
If errcode = 3604 then
...
else
.....
endif;
Thanks in advance.
Error handling.
-
- Posts: 59
- Joined: Thu May 26, 2011 5:04 am
- OLAP Product: COGNOS
- Version: 9.0
- Excel Version: 2007
Error handling.
Configuration Details
Microsoft Window Server 2003 Exterprise x64 Edition Service Pack 2
RAM 32 GB
using IBM Cognos Express Xcelerator (Version 10.1)
MS-Office Excel 2010 (12.0.6514.5000)SP2 MSO (12.0.6425.1000)
Microsoft .NET Framework 3.5
Microsoft Window Server 2003 Exterprise x64 Edition Service Pack 2
RAM 32 GB
using IBM Cognos Express Xcelerator (Version 10.1)
MS-Office Excel 2010 (12.0.6514.5000)SP2 MSO (12.0.6425.1000)
Microsoft .NET Framework 3.5
-
- Site Admin
- Posts: 6647
- Joined: Sun May 11, 2008 2:30 am
- OLAP Product: TM1
- Version: PA2.0.9.18 Classic NO PAW!
- Excel Version: 2013 and Office 365
- Location: Sydney, Australia
- Contact:
Re: Error handling.
You wish. As, indeed, do most of us.ryan wrote:Is there any way or functions available for error handling in TM1's TI process?
If errcode = 3604 then
...
else
.....
endif;
Thanks in advance.
The closest you can get to that is to write some code to ensure that you check your variables for valid input. (Non-empty, beyond a certain length, translates to a non-zero numeric value, or what have you.) If you find something invalid, use a standard If block to handle the exception. (Do an ItemSkip or ItemReject, write to a log file, use a default or whatever.) Otherwise the only "error handling" that you have is what TI will do for you, which is up to and including tossing out the row as a result of (say) a key error.
"To them, equipment failure is terrifying. To me, it’s 'Tuesday.' "
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.
-----------
Before posting, please check the documentation, the FAQ, the Search function and FOR THE LOVE OF GLUB the Request Guidelines.