Hi Everyone,
I have written a pre-submit process that checks in validation cube for possible issues and, in case of any, interrupts the submit action together with a proper message.
This is working fine.
However, beside the mesage I would also like to open a drill view which would show more details about the validation issues.
I've put the ExecuteProcess('}drill...') inside the pre-submit process together with the necessary parameter values.
I've also tried to put RETURNVIEWHANDLE('B_Monthly_Validations','Drill_B_Monthly_Validations');
Both of these don't work.
It means, the pre-submit process is still working fine in TM1 Contributor, it interrupts the submit in case of an error, it still produces a message, but no extra drill view is opening.
So my question is: is it possible to open a drill view in a workflow process at all? Or am I doing something wrong.
Thanks!
Drill view in a workflow process
-
- 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: Drill view in a workflow process
Nice concept what you are trying to do but I think you need to try something different.
I can't imagine that this could be made to work. The }Drill_ processes are quite unique in that they return something to the UI with ReturnViewHandle but ONLY when executed from the cube viewer or DBRW, that is the calling UI is critical. The overall central concept of TI processes is that they run on the server typically as a "background ETL" type process, that is there is no UI at runtime for a TI process. Drill processes are an exception to this but only when called from certain specific UIs. No doubt if you call a drill process from within another process and are careful to pass in valid parameters for cell context then the process will execute just fine (in the background) but as the TI has no UI context nothing will happen when ReturnViewHandle is called.
I can't imagine that this could be made to work. The }Drill_ processes are quite unique in that they return something to the UI with ReturnViewHandle but ONLY when executed from the cube viewer or DBRW, that is the calling UI is critical. The overall central concept of TI processes is that they run on the server typically as a "background ETL" type process, that is there is no UI at runtime for a TI process. Drill processes are an exception to this but only when called from certain specific UIs. No doubt if you call a drill process from within another process and are careful to pass in valid parameters for cell context then the process will execute just fine (in the background) but as the TI has no UI context nothing will happen when ReturnViewHandle is called.
Please place all requests for help in a public thread. I will not answer PMs requesting assistance.
-
- Posts: 2
- Joined: Fri Jun 27, 2014 12:37 pm
- OLAP Product: Cognos TM1
- Version: 10.2.0
- Excel Version: 2010
Re: Drill view in a workflow process
It's a shame that you have confirmed my worst expectations.
But anyway, thank you very much for your quick answer.
Regards!
But anyway, thank you very much for your quick answer.
Regards!
- paulsimon
- MVP
- Posts: 808
- Joined: Sat Sep 03, 2011 11:10 pm
- OLAP Product: TM1
- Version: PA 2.0.5
- Excel Version: 2016
- Contact:
Re: Drill view in a workflow process
Hi
If your front end is in Excel rather than TM1 Web, so you have access to VBA then you can trigger a Drill Thru process by VBA
Do a search on the forum for
VBA to trigger drill through
There is an example there
You could then replace the Action button with a standard Forms or Control Button and then use VBA to trigger your validation process and have it put a Good/Bad flag into a cube, which has }Clients as a dimension so it can be user specific. You can then get the flag value using the DBR formula as a macro, and if Bad then you can use the VBA in the post referenced above to run the drill thru. You will just need to have a DBRW formula on the sheet that has the Drill Thru linked to it.
If you are using TM1 Web as the front end then as far as I know the only option is to have another button that a user clicks on to get further information if there is an error, and to then show this in an Active Form or Slice on the same sheet or to jump to another sheet. Another possibilty might be to use the HYPERLINK function and the URL API to let them jump to a View or Web Sheet
Regards
Paul Simon
If your front end is in Excel rather than TM1 Web, so you have access to VBA then you can trigger a Drill Thru process by VBA
Do a search on the forum for
VBA to trigger drill through
There is an example there
You could then replace the Action button with a standard Forms or Control Button and then use VBA to trigger your validation process and have it put a Good/Bad flag into a cube, which has }Clients as a dimension so it can be user specific. You can then get the flag value using the DBR formula as a macro, and if Bad then you can use the VBA in the post referenced above to run the drill thru. You will just need to have a DBRW formula on the sheet that has the Drill Thru linked to it.
If you are using TM1 Web as the front end then as far as I know the only option is to have another button that a user clicks on to get further information if there is an error, and to then show this in an Active Form or Slice on the same sheet or to jump to another sheet. Another possibilty might be to use the HYPERLINK function and the URL API to let them jump to a View or Web Sheet
Regards
Paul Simon