Checkboxes in Tabular Forms The easy way As you may know, Tabular Forms are sometimes lets 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. Why is it so important to keep the generated Apply. MRU processes Because this default processes, which are generated by the Tabular Form wizard are doing a lot of stuff in the background. They take care of Lost update detection, locking and finally the insertupdatedelete without having to write a single line of code. The goal for a developer should always be to keep as much default functionality of Oracle APEX as possible and not try to redevelop that kind of functionality You will find several solutions out there, like the one from Denes Kubicek which will work fine, but which doesnt accomplish the above goal. You have to do a lot of coding and its missing the Lost update detection and locking feature. Which is very important in my opinion. I am trying to see from an SQL console what is inside an Oracle BLOB. I know it contains a somewhat large body of text and I want to just see the text, but the. DB2 Survival Guide DB2 Environment Basics Creating a Database and Tables v6. What is it a Blob How can I use it What differences are between DBMSs Blobs, I would like to save data using blobs but in any DBMS, And then with a library read. Thats why I came up with a different solution which doesnt use the APEXItem. Checkbox function. The solution. Create a regular Tabular Form New PageFormTabular Form. I will use the DEMOUSERS table which comes with the Sample Application. Change the order and the Display As of the columns how you want to have them. Wizard generated Tabular Form after column changes. For the column with the flag, in our example thats ADMINUSER set the property Display As to HiddenChange the SQL Statement of the Tabular Form Region Edit RegionRegion DefinitionRegion Source to include a new column called ADMINUSERCHECKBOXSELECT USERID. Update Blob Field In Db2 Sql' title='Update Blob Field In Db2 Sql' />USERID AS USERIDDISPLAY. USERNAME., ADMINUSER. WHEN ADMINUSER Y THEN checkedchecked. END AS ADMINUSERCHECKBOX. EXPIRESON., CREATEDON. FROM DEMOUSERSFor the new column ADMINUSERCHECKBOX, set the property HTML Expression Column AttributesColumn Formatting to. Spyro 3 Year Of The Dragon Iso Palo. ADMINUSERCHECKBOX valueROWNUM namef. ROWNUM ADMINUSERCHECKBOX has to be replaced by the column name of the newly added column. Create a Page Processing process with the following settings. Type PLSQLName Set ADMINUSER flag. Sequence 0 Important Has to be before all other processesPoint On Submit Before Computation and Validations. Enter PLSQL Page Process. Reset the hidden ADMINUSER flag for all visible records to N. Note gf. 04 maps to the hidden ADMINUSER column. FOR ii IN 1. APEXApplication. COUNT. APEXApplication. N. Set the hidden ADMINUSER flag for those records where the. Y. Note gf. ADMINUSERCHECKBOX. FOR ii IN 1. APEXApplication. COUNT. APEXApplication. APEXApplication. Este captulo describe la sintaxis para los comandos SQL soportados en MySQL. PLSQL Procedural LanguageStructured Query Language is Oracle Corporations procedural extension for SQL and the Oracle relational database. PLSQL is available in. Update Blob Field In Db2 Sql' title='Update Blob Field In Db2 Sql' />Y. END Note See the explanation to find out how to get the correct number for the APEXApplication. Thats it. The default Oracle APEX Tabular Form processes are still working. You can try out the working example on apex. Update Blob Field In Db2 Sql' title='Update Blob Field In Db2 Sql' />Tabular Form with checkbox. The Explanation. Steps 1 3 are just regular tabular form creation steps. Step 4 adds the new column ADMINUSERCHECKBOX, which contains an interesting CASE statement. WHEN ADMINUSER Y THEN checkedchecked. END AS ADMINUSERCHECKBOXThis CASE statement will return checkedchecked if ADMINUSER is set to Yes. This kind of value is needed by the INPUT HTML element which we create in step 5. Step 5 adds the HTML tag to render a checkbox. ADMINUSERCHECKBOX valueROWNUM namef. ROWNUM It uses the COLUMNNAME replacement syntax, in our case ADMINUSERCHECKBOX to get the current value of the column. Thats necessary for the checkbox tag to know if it should be rendered checked or unchecked. If a checkbox is checked by the user, valueROWNUM will tell us which row is effected. The ROWNUM placeholder is replaced with the row number of the visible record in the tabular form. It will always start with 1 and has nothing to do with the pseudo column ROWNUM which can be use in a SQL statement Oracle APEX to map the checkbox column to the APEXApplication. I use a very high number so that the checkbox doesnt conflict with one of the save state columns handled by APEX. A high number makes also sense, because in case you add a new column to your tabular form, you do not have to change the code where you access the APEXApplication. Step 6 creates the process which synchronizes the hidden ADMINUSER flag column with the checked checkbox values of ADMINUSERCHECKBOX. What does it do First of all you have to find out to which APEXApplication. See my posting Which Tabular Form Column is mapped to which ApexApplication. In our example its gf. The first FOR LOOP resets the hidden ADMINUSER flag for all visible records to No. FOR ii IN 1. APEXApplication. COUNT. APEXApplication. Audit Program Sample Philippines here. N. END LOOP In the second FOR LOOP it will set the Yes flag for all those records where we now have a checked checkbox. FOR ii IN 1. APEXApplication. COUNT. APEXApplication. APEXApplication. Y. END LOOP At first hand this statement looks a little bit complicated For checkboxes you have to remember several things. The array which is mapped to a checkbox just contains as many records as you have checked rows. For example If you have 1. A normal column like the QUOTA always returns an array with 1. Thats why its so important to define valueROWNUM in step 5. It tells us which checkbox has been checked. That value of the actual row is contained in the gf. ADMINUSER column. Because we have synchronized the hidden ADMINUSER column array with the checkbox selection, the standard Apply. MRU process will consider the values as if the user had manually entered them in a normal text field. The ADMINUSERCHECKBOX column is not considered by the Apply. MRU process, because for Oracle APEX it is rendered as Standard Report Column. This type of Display As is not treated as saves state. Thats why the Apply. MRU ignores it. Actually it wouldnt even know to which array the checkbox is mapped to. Another advantage of this synchronization technique is that the gf. ADMINUSER has the same array indexing as the normal columns. It allows to write simpler validations code, because all values of the same row are located on the same index position in all the gfxx arrays Final Note. Why dont I just use the APEXItem. Checkbox function in the SQL statement, instead of using my hand written HTML code in the HTML ExpressionSimple reason The Add. Rows process of APEX will not work. Because APEXItem. Checkbox is just called for existing records and not for the new record. Thats why the solutions which use APEXItem. Checkbox have to to redevelop that kind of behavior by doing an UNION against DUAL where the WHERE clause restricts to the current request ADDROWS. But be aware of problems with ordering, when you do that. As I already said in my initial statement. Dont reinvent the wheel, use as much functionality of Oracle APEX as possible I would be interested in your thoughtDo you have ideas for improvement or a better solution Add your remarks in the comment section This posting was originally posted on Der Oracle APEX Experten Blog.