PAW Synchronise Action Button parameters with Sheet Selections

Post Reply
User avatar
Posts: 749
Joined: Sat Sep 03, 2011 11:10 pm
OLAP Product: TM1
Version: PA 2.0.5
Excel Version: 2016

PAW Synchronise Action Button parameters with Sheet Selections

Post by paulsimon » Sat May 23, 2020 2:56 pm


As far as I am aware there is no way to synchronise the parameters to a TI Process on an Action Button with selections made in PAW (short of embedding a Web Sheet which for me anyone defeats the purpose of PAW).

For us this is absolutely critical. Without this, we will not be able to do most of the things that we currently do in TM1 Web, in PAW.

Our users typically make selections on a Web Sheet, review numbers in a table, and then click an Action Button which will carry out various actions, typically validating data, updating Workflow cubes, moving data from one cube to another, building dimensions, etc. The selections that they make on the web sheet are the ones that get passed to the TI process as parameters. There does not appear to be a way to do this in PAW. Users instead get prompted to re-select values for the parameters when they click the Action Button, which would not be acceptable.

I suspect that this is fairly important to a number of other people. If you think it is important too, then please vote for the IBM Idea that we raised using the link below ... itted_idea

If I have misunderstood PAW, or if you have some way around this, other than those ruled out in the request, then please let me know.


Paul Simon

Posts: 1659
Joined: Mon Dec 05, 2011 11:51 am
OLAP Product: Cognos TM1
Version: PA2.0 and most of the old ones
Excel Version: All of em
Location: Manchester, United Kingdom

Re: PAW Synchronise Action Button parameters with Sheet Selections

Post by declanr » Sat May 23, 2020 3:11 pm

There are a number of things that you can’t quite do with the synchronisation- such as what you have highlighted and another common one of selecting an element in 1 dimension; such as a Country Code in a country dimension and seeing its corresponding element selected in another dimension e.g all Stores for that Country in the Store dimension.

Or even selecting version x may mean you want version X in most of your views; but 1 or 2 views should be a subset of version X and the equivalent version from last year etc.

As such I tend to not use the selector widgets at all and instead have picklists for selections in a cube containing the }client dim.
Then you have full control with MDX subsets and CellGetS in TIs being used instead of parameters.
It does the job well as a workaround; it would be nice out of the box but I imagine it would be a very big development for the widgets and sync settings to give all of the functionality that we would like.
Declan Rodger

Post Reply