Page 1 of 1

Action Button to clear a cube = VBA Errors

Posted: Thu May 03, 2012 10:30 am
by Steve Vincent
Has anyone successfully used an action button to pass variables to a TI which then clears data in a cube?

My TI is fine. It builds subsets & a view, clears the data based on a couple of parameters then destroys the subsets & view at the end. Grand. Try running that from an action button and all i get is incomprehensible VBA errors from the TM1 API, which is locked so i have no way to debug the problem. The TI runs fine & does the job, but the action button is throwing a hissy afterwards. If its run on a selection of data where no info exists on the cube (ie. the TI has nothing to do), i get no errors. It seems that its trying to pass something back to the button once complete and its not liking it, but no idea what, why, or have any method to avoid it.

i've used them fine with other tasks such as adding users, or changing security, but this is the 1st time i've tried to delete data with one. Yet another 5 min task has taken up a morning of head scratching & toy throwing... :roll:

Re: Action Button to clear a cube = VBA Errors

Posted: Thu May 03, 2012 10:39 am
by asutcliffe
Steve Vincent wrote:Has anyone successfully used an action button to pass variables to a TI which then clears data in a cube?
FWIW, I've done this a number of times without any problem. I'd be punting that one to IBM.

Re: Action Button to clear a cube = VBA Errors

Posted: Thu May 03, 2012 10:41 am
by David Usherwood
What happens if you publish the sheet to Web (where there's no VBA to get sulky on you :) ) ?

Re: Action Button to clear a cube = VBA Errors

Posted: Thu May 03, 2012 12:46 pm
by Steve Vincent
We don't use the web so i can't test it with that. Turns out that it now wants to work, after i quit Excel completely and restarted it. We keep getting unexplained connection error messages with Excel and Tm1 - normally it causes TM1 formula to either not work at all, or partially work. This wasn't the same error message, but appears to be linked with the same kind of issue. Crops up a lot when you try to log in to another service, or snap data.

Its really frustrating when you get issues like this with no way of explaining them. Makes trusting the software difficult, and writing procedures nigh on impossible.