on 03-27-2014 6:54 AM
Hi Colleague,
Currently I'm using one Calculation view CV1 to call another calculation view CV2 as following:
select * FROM "_SYS_BIC"."ags-asord.test/CV2"
WITH PARAMETERS ('placeholder' = ('$$I_CON_NO$$', ':I_CON'));
I_CON_NO is CV1's input parameter, and I_CON is CV2's input parameter.
But it seemed that it will treat :I_CON as a string, not a parameter.
So anybody can advise how to write it correctly?
Thanks,
Doris
Hi Doris,
This works for me to call a calculation graph view from a scripted calculation view:
select * from "_SYS_BIC"."ags-asord.test/CV2"
(placeholder."$$I_CON_NO$$" => :I_CON);
If the called CV is script type, pay attention to parameter case sensitive and check if your parameter is not lower case of mixed....
select * from "_SYS_BIC"."ags-asord.test/CV2"
(placeholder."$$i_con_no$$" => :I_CON);
Regards, Fernando Da Rós
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Doris,
Yes, as I said it's about an script calculation view calling a graph calculation view.
Did you checked on the "parameter case sensitive" on your script calc view (you found this parameter on properties. Try playing around True and false.
It will not solve post my code, as I already made the needful on your SELECT to put it to work.
What kind of error are you experiencing?
Regards, Fernando Da Rós
Hi Fernando,
But my called CV is script one, will it also work?
I cannot find the parameter case sensitive setting, would you please advice where to find?
Also currently i have syntax error
select * from "_SYS_BIC"."ags-asord.test/CV2"
WITH PARAMETERS (placeholder."$$i_con_no$$" => :I_CON);
Please advice further:)
Thanks,Doris
Hi Doris,
Yes, it works also for script calc view.
I prepared a sample demonstration:
- create two script CA
- first named CV_CALLER with input parameter I_CON
- second named CV_CALLED with input parameter I_CON_NO
- both has same output structure with a column RESPONDE NVARCHAR 10 (same as the parameters
The demo idea is call CV_CALLER passing a parameter string, which call the CV_CALLED procedure and put the content of parameter on the RESPONSE column of var_out structure.
Better to put see the pictures:
1) Creating caller CV. I used True for both procedures
2) You can found this info on properties (click on semantic node first)
3) Both parameters are NVARCHAR 10. One one view I_CON on other view I_CON_NO
4) On both views the target output is equal. One column RESPONSE NVARCHAR 10.
5) Both activated... Please forgive the sequence of pictures ... You must first create the CV_CALLED
6) The SQL fill on CV_CALLER parameter I_CON value 'backtome", which flow through CV_CALLED parameter I_CON_NO and back to me in the response column.
I hope it help you to find what is going wrong on your case.
BTW: Tested on revision 70.
Regards, Fernando Da Rós
For those who can't get it work,
try making different names of input parameters
in a Caller and Called procedure/calc view.
In my case, I was trying to pass my IP_TARGET_CCY
from Parent calc view to Child calc view,
but Child always took its own default value.
Only different naming helped.
Kostia
Hi Doris,
Have you tried ('placeholder' = ('$$I_CON_NO$$', '$$I_CON$$'));
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I dont think Parameter mapping is possible. It is only possible with Graphical calculation view as of now.
See these threads for your reference:
Pass input parameters(variables) to CE_OLAP_VIEW
Regards,
Krishna Tangudu
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.