I am rebuilding an Oracle Form. Based on the layout of the Oracle Form, the corresponding layout in an APEX app would have a Form region, but with an Interactive Grid in the middle of the Form region.
Specifically, I want there to be a Form region with some of the fields at the top of the Form, then an Interactive Grid in the middle, and the rest of the fields at the bottom of the Form.
So far, I have not found a (great) way to do this. I'm hoping the solution is painfully simple. Notwithstanding that hope, here is what I have tried:
- Form A with half of the fields, then an Interactive Grid, then Form B with the other fields. The problem with this is that there are now two forms. I don't like this. For one, I haven't fully figured out how to submit data to one table from two forms (along with one create/save button) but it also seems inelegant.
- A Static Content region with half of the fields, followed by a Interactive Grid, and then another Static Content region with the other fields. Of course, the Page Items/Fields in the Static Content regions have to be manually initialized and processed. This is actually what I ended up doing in one scenario, however, the corresponding table is a legacy table that doesn't have a primary key (nor even a field that could be turned into a primary key if I wrote an ALTER statement against it, without great difficulty anyways…) so in this case I needed to do manual processing anyway. My current scenario has a table that does have a Primary Key, but otherwise works largely in the same way, i.e. the interceding Interactive Grid on the UI side.
Basically, I'm wondering what would be the most idiomatic way to construct this in APEX. Again, what I am wanting to construct is a Page that corresponds to a single database table, in which I have some of the fields at the top of the page, then an editable interactive grid, and then the remaining fields below the interactive grid. The fields above and below the interactive grid all correspond to a single database table (the reason they are separated is due to idiosyncratic business logic). I would like to take advantage of automatic / declarative page item initialization and processing, if at all possible, instead of having to do it manually.