When defining a task in Avaloq, it's possible to use the pseudo keyword to mark parameters that should not be passed to the underlying task, but should still be accessible from the REP DTM sources.
This is useful if their purpose is to enhance the report functionality but they do not provide meaningful input for the task procedure itself.
They are delcared as:
i_[param_name] pseudo [param_type]
eg:
i_my_param pseudo number
And can then be accessed in the REP DTM like any other task parameter:
task_exec.param("my_param").nr_val
Showing posts with label Avaloq. Show all posts
Showing posts with label Avaloq. Show all posts
05/04/2016
19/03/2016
[Avaloq] Get task parameter value in datamart and use it in layout
When creating a new report in Avaloq, you will typically create/edit a datamart (REP DTM source) and a layout (eg: REP SCREEN scource).
If you wish to use a task parameter to enhance the functionality offered by your report, first store the value in a variable inside the DTM (it will be at TOP level):
then access it from your layout with:
top.my_task_param
If you wish to use a task parameter to enhance the functionality offered by your report, first store the value in a variable inside the DTM (it will be at TOP level):
[Report 2.0]
report some_task.some_dtm
datamart
on init
--get the parameter passed to the task
my_task_param some_datatype assign [task_exec.param("my_task_param").nr_val(1)] --remember to check the DDIC for more appropriate methods other than nr_val. Also pay attention to the sequence number!
connect some_ddic as dm
...
then access it from your layout with:
top.my_task_param
Subscribe to:
Posts (Atom)