I have something which borders on being a bug, though it may be (arguably) an undocumented feature.
There are some commands in TI which will not throw an error even if the input is valid. SubsetDestroy, when called with a non-existent subset name, comes to mind. This is useful behaviour (since you don't need to check whether the subset exists first), but I've recently encountered one which just seems odd.
AssignClientToGroup will not throw an error if the client doesn't exist, if the group doesn't exist, or if both don't exist.
At the very least IMHO that should be added to the documentation. At most, it should throw an error.
A poll has been provided below.
Thoughts?
Should an invalid Assign Client To Group throw an error
-
Alan Kirk
- Site Admin
- Posts: 6643
- 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:
Should an invalid Assign Client To Group throw an 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.
-
lotsaram
- MVP
- Posts: 3698
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: Should an invalid Assign Client To Group throw an error
I haven't ever noticed this since I always make sure there's a DIMIX test on }Clients and }Groups before using this function since I would always want to trap this and know about it anyway. But thanks for pointing it out. I'm with you - it would make sense to throw a minor error.