Ok I might be asking for something stupid here.
I would like to have an option where the form is based on a query. This is not a dynamic form.
There are some queries I can not place in a view as the "where" clause needs to be "added" inside the query.
Example
select * from (
select e_epi_id
, q_record_number
, q_label_text
, r_ev_id
, r_que_et_id
, r_que_record_number
, r_record_number
, r_response_value
, vsi_vs_id
, vsi_record_number
, vsi_item_value
from radiography_v )
pivot (
max(r_ev_id) r_ev_id,
max(r_que_et_id) r_que_et_id,
max(r_que_record_number) r_que_record_number,
max(r_record_number) r_record_number,
max(q_label_text) q_label_text,
max(r_response_value) r_response_value,
max(vsi_vs_id) vsi_vs_id,
max(vsi_record_number) vsi_record_number,
max(vsi_item_value) vsi_item_value
for q_record_number in ( 1 rn1, 2 rn2, 3 rn3, 4 rn4, 5 rn5,
6 rn6, 7 rn7, 8 rn8, 9 rn9, 10 rn10, 11 rn11) );
It requires a where condition as
where r_ev_id=21340631 and r_que_et_id=8
So the query in the form would be like
select * from (
select e_epi_id
, q_record_number
, q_label_text
, r_ev_id
, r_que_et_id
, r_que_record_number
, r_record_number
, r_response_value
, vsi_vs_id
, vsi_record_number
, vsi_item_value
from radiography_v
where r_ev_id=:P100_EVENT_ID and r_que_et_id=8)
pivot (
max(r_ev_id) r_ev_id,
max(r_que_et_id) r_que_et_id,
max(r_que_record_number) r_que_record_number,
max(r_record_number) r_record_number,
max(q_label_text) q_label_text,
max(r_response_value) r_response_value,
max(vsi_vs_id) vsi_vs_id,
max(vsi_record_number) vsi_record_number,
max(vsi_item_value) vsi_item_value
for q_record_number in ( 1 rn1, 2 rn2, 3 rn3, 4 rn4, 5 rn5,
6 rn6, 7 rn7, 8 rn8, 9 rn9, 10 rn10, 11 rn11) );
I need the fields to be pre-defined as I need to handle hide and show as well as some other dynamic actions at field level. But dynamic forms are not helping me much in that area and it starting to get quite complicated.
One way I worked it is by using Grid & Page item Binding, but I would need to hide the grid and that does not work as the grid is the driver and the form is a slave so to speak. Or can I hide the grid all together somehow. I do need custom processing anyway as the pivoted data set needs to be unpivoted to process into its respective table.
Standard APEX allows you to build a form based on a query. So you may ask why don't you use that then. Well maybe I have to, but I prefer to keep everything in the FOEX realm.
However I am open to alternatives. I might have to go down the route of an APEX collection and populate that through a procedure on selection of an event (that is a radiography event).