I have a workbook that allows users to run processes against private subsets. It first pulls the elements of the private subset and displays them in a column of the workbook. Then each cell containing an element is passed as a parameter to a process which creates a public subset with the USERID tagged to it. Then it runs the requested process against all elements of the public subset.
It all works fine in perspectives but on the Web...it won't display the elements. I use a series of SUBNM formulas to pull display each element in sequence but on the web all the cells return blank. They have a subset editor button available to click on and when you do...it has the correct subset displayed and even the correct element pre-selected....if you hit OK it will then display in the cell. But I need it to show up in the box without having to go in and select each one.
Again, this all works perfectly in perspectives but the elements won't display automatically on the web.
Any help would be appreciated!
Terry
Display elements of a private subset on TM1Web
-
lotsaram
- MVP
- Posts: 3706
- Joined: Fri Mar 13, 2009 11:14 am
- OLAP Product: TableManager1
- Version: PA 2.0.x
- Excel Version: Office 365
- Location: Switzerland
Re: Display elements of a private subset on TM1Web
I think since Contributor has been on the scene that TM1 web has been reconfigured and one of the results is that private subsets and views are not really recognized since otherwise this could interfere with what gets displayed in Contributor application tabs and workflow. This is probably why your solution doesn't work in the web.
If the intent is just to allow users to process for some reason a list of members (private subset aside) then assuming the list could have a variable number of members that could be small to large then having an individual parameter in a TI for each subset member seems also a somewhat clumsy way of handling this. Why not have a cube that could have 3 dimensions of i) dimension,ii) user and iii) index where the user can select members against the index for the relevant dimension (this could be controlled by picklist also). Then all that needs to get passed to the TI as parameters is user name and dimension name. Then the TI uses a view as the datasource which can be built dynamically. I think this would be much neater and easier and no issues with working on the web. (NB you could convert the list to a public subset in the process also if you wanted)
If the datasource MUST be a private subset then I think you are stuck (unless IBM make private views and subsets more readily available in TM1 web again as opposed to needing to be quite deliberately selected). You could use the TI function to publish a private subset and make it public then use the public subset as a data source but unfortunately I think there is no option to make the name different from the private subset name in the case of conflicts or to revert a public subset back to a private one.
If the intent is just to allow users to process for some reason a list of members (private subset aside) then assuming the list could have a variable number of members that could be small to large then having an individual parameter in a TI for each subset member seems also a somewhat clumsy way of handling this. Why not have a cube that could have 3 dimensions of i) dimension,ii) user and iii) index where the user can select members against the index for the relevant dimension (this could be controlled by picklist also). Then all that needs to get passed to the TI as parameters is user name and dimension name. Then the TI uses a view as the datasource which can be built dynamically. I think this would be much neater and easier and no issues with working on the web. (NB you could convert the list to a public subset in the process also if you wanted)
If the datasource MUST be a private subset then I think you are stuck (unless IBM make private views and subsets more readily available in TM1 web again as opposed to needing to be quite deliberately selected). You could use the TI function to publish a private subset and make it public then use the public subset as a data source but unfortunately I think there is no option to make the name different from the private subset name in the case of conflicts or to revert a public subset back to a private one.
-
terry720
- Posts: 15
- Joined: Thu Mar 29, 2012 7:27 pm
- OLAP Product: Access
- Version: 9.5.2
- Excel Version: 2003
Re: Display elements of a private subset on TM1Web
Thanks, sorry for the delay in responding.
The point of this exercise is to allow users to run processes on a private subset of jobs. TI can't see into private subsets so I have to get the list of jobs put somewhere it can see them. I considered your first suggestion but then users would have to manually add the list of jobs to a cube whereas they already have those jobs in a subset. They will balk at this. That's why I came up with the process of using a workbook to pull each job from their subset in order and then push the contents of those cells as parameters in a process that constructs a hidden public subset...which TI can then see and use to run the process.
The point of this exercise is to allow users to run processes on a private subset of jobs. TI can't see into private subsets so I have to get the list of jobs put somewhere it can see them. I considered your first suggestion but then users would have to manually add the list of jobs to a cube whereas they already have those jobs in a subset. They will balk at this. That's why I came up with the process of using a workbook to pull each job from their subset in order and then push the contents of those cells as parameters in a process that constructs a hidden public subset...which TI can then see and use to run the process.