Skip to main content

It is even more easy to replace the APEX with the jQuery calendar...

In a previous post I described how to replace the default APEX calendar with a better looking jQuery calendar. But one of the steps is that the "Display as" and "HTML Form Element Attributes" needed to be changed. But using jQuery more extensively that isn't even necessary. When you put the following code in an HTML Region on Page 0 (assuming you already included the jQuery stuff), all existing APEX calendar items are automagically 'converted' to jQuery calendar items. (No guarantee though: I didn't test it on all sorts of pages, may be dependent on your template). Look here for a live demo...

// Remove original Datepicker
$("td.datepicker + td" ).remove();
// Add jQuery Datepicker to all Datepicker input fields that are not hidden
$("td.datepicker > input[type!=hidden]" ).datepicker(
{ dateFormat : 'dd/mm/yy'
, closeText : 'X'
, clearText : ''
, showOn : 'button'
, buttonImage : '#WORKSPACE_IMAGES#calendar.gif'
, buttonImageOnly : true


Patrick Wolf said…
Hi Roel,

is there a reason why you are using "each" instead of just using

$("td.datepicker > input[type!=hidden]" ).datepicker

Because that also seems to work and is a little bit shorter and easier to read.

Patrick Wolf said…
Or you can even use a more compact version which uses the jQuery chaining:

{ dateFormat : 'dd/mm/yy'
, closeText : 'X'
, clearText : ''
, showAnim : 'scale'
, showOptions : { origin: ['top', 'left'] }
, showOn : 'button'
, buttonImage : '#WORKSPACE_IMAGES#calendar.gif'
, buttonImageOnly : true

Too bad that the comment function doesn't allow a PRE tag to format the code. If you use chaining, indenting the code is very important so that you see the structure and which result set is used.

Roel, thanks for the idea.
Patrick, thanks for the more compact syntax.
Roel said…
Thanks Patrick & Louis-Guillaume.
So the code gets shorter every time....
Tim Ward said…
I'm doing the following to replace datepickers in apex 3.2 with the JQuery Datepickers, but my only problem is the images doesn't display next to the field.. Any ideas why that would happen?

"<"link rel="stylesheet" type="text/css" href="#IMAGE_PREFIX#jquery/css/redmond/jquery-ui-1.8.4.custom.css" /">"

"<"script type="text/javascript" src="#IMAGE_PREFIX#jQuery/js/jquery-1.4.2.min.js"">""<"/script">"

"<"script type="text/javascript" src="#IMAGE_PREFIX#jQuery/js/jquery-ui-1.8.4.custom.min.js"">""<"/script">"

"<"script type="text/javascript"">"
$(document).ready(function () {
$(".datepicker ">" input[id]").datepicker();

dateFormat: 'dd-M-yy',
changeMonth: true,
changeYear: true,
closeText: 'Done',
showButtonPanel: true,
duration: 'slow',
prevText: 'Previous',
showOtherMonths: true,
selectOtherMonths: true,
dayNamesShort: ['Sun','Mon','Tue','Wed','Thu','Fri','Sat'],
dayNamesMin: ['Sun','Mon','Tue','Wed','Thu','Fri','Sat'],
constrainInput: true,
showOn: 'both',
buttonImage: '#IMAGE_PREFIX#asfdcldr.gif',
buttonImageOnly: true,
buttonText: 'Calendar',
autoSize: true


// Remove Original Date Picker //
$("td.datepicker + td").remove();

// Add jQuery DatePicker to all DatePicker input fields not hidden //
$("td.datepicker ">" input[type!=hidden]").datepicker();

Roel said…
Tim, where do they display? Can you set up an example on
Tim Ward said…
Guess I should have said that they don't display at all...

I'll try to do something at, but don't they use 4.0 now?
Tim Ward said…
Seems to work fine on Apex 4.0....

Just weird that using the code I showed that the calendar image won't show up on the internal replaced date pickers...

The image shows up if I create a Text Item with class="datepickernew" in the HTML Form Element Attributes of the page.

Popular posts from this blog

Refresh selected row(s) in an Interactive Grid

In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid. The use case I'll cover right here is probably more common - and therefore more useful!

Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user.The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even worse) while you…

Dockerize your APEX development environment

Nowadays Docker is everywhere. It is one of the main components of Continuous Integration / Continuous Development environments. That alone indicates Docker has to be seen more as a Software Delivery Platform than as a replacement of a virtual machine.

However ...

If you are running an Oracle database using Docker on your local machine to develop some APEX application, you will probably not move that container is a whole to test and production environments. Because in that case you would not only deliver a new APEX application to the production environment - which is a good thing - but also overwrite the data in production with the data from your development environment. And that won't make your users very excited.
So in this set up you will be using Docker as a replacement of a Virtual Machine and not as a Delivery Platform.
And that's exactly the way Martin is using it as he described in this recent blog post. It is an ideal way to get up and running with an Oracle database …

apex_application.g_f0x array processing in Oracle 12

If you created your own "updatable reports" or your custom version of tabular forms in Oracle Application Express, you'll end up with a query that looks similar to this one:
then you disable the "Escape special characters" property and the result is an updatable multirecord form.
That was easy, right? But now we need to process the changes in the Ename column when the form is submitted, but only if the checkbox is checked. All the columns are submitted as separated arrays, named apex_application.g_f0x - where the "x" is the value of the "p_idx" parameter you specified in the apex_item calls. So we have apex_application.g_f01, g_f02 and g_f03. But then you discover APEX has the oddity that the "checkbox" array only contains values for the checked rows. Thus if you just check "Jones", the length of g_f02 is 1 and it contains only the empno of Jones - while the other two arrays will contain all (14) rows. So for processing y…