As you may know, Tabular Forms are sometimes let’s say “a little bit tricky”. They are missing some common features which are available for Page Items. One of them is the declarative support for Checkboxes. With the following step by step instruction you will be able to add checkboxes in Tabular Forms without loosing the existing wizard generated functionality.
Maybe you have already used a PPR (Partial Page Rendering) report, by setting the “Report Template” property to “template: 7. Standard (PPR)”.
Have you ever asked yourself how Oracle APEX maps the columns of a Tabular Form to the Apex_Application.g_fxx (alias Htmldb_Application.g_fxx, alias WWV_Flow.g_fxx) array?
In the last release of the ApexLib Framework I have also added a sometimes useful API to hide the “Select All” checkbox of the row selector of an Tabular Form. This can be useful to prevent the user from selecting all records for delete.
One problem with Tabular Form Column is that they don’t have a “Maximum Width” property as Page Items do. APEX automatically generates a maxlength=2000 for all columns. What is the result? The user gets a
when he enters a too long value. Not really nice, isn’t it? And now he has to start counting so that he knows where to cut of…
I have added another small usability enhancement to the ApexLib Framework.
When you call the API
it will register the keys Up and Down to navigate to the previous/next record in a Tabular Form. This should work for manually build (with Apex_Item) and also for the default updateable Tabular Forms.
It is by intention that the Up/Down key doesn’t work on textareas and select lists, because on that type of field the Up/Down is used by the widget.
Try it out on the ApexLib Feature Demonstration site.
Today at 00:50 (when normal people are already sleeping) I finally made it to release version 1.0 of the Oracle APEX development framework, called ApexLib.
Today I was the hole day at a customer and had no chance to blog about it. Continue reading
You have a Tabular Form with 3 columns (Amount, Tax, Total) and want to populate the Total column with the sum of Amount and Tax as soon as Tax has been entered.
Do you want to have highlighting for the tabular form column cells which have an error? Then you should read the rest of the posting!
Maybe you already had the “joy” to find out that accessing the “Row Selector” column of an updateable tabular form isn’t that straightforward as expected. Because the corresponding g_f01 array isn’t indexed by row number as the other column-arrays of the tabular form.
Instead it contains as many values as you have checked rows. The value of the array entry contains the “real” row number for which it has been checked. So you can have the situation that g_f01 has a count of 2, but your g_f02 containing the EMPNO contains 15 rows. In the case if the g_f02 is your “driving” array, because you want to process all the records and only for the checked ones you want to do something special, it can get really challenging for a new APEX programmer (and even for a more experienced one).