Caution with new “Runtime Where Clause” in Oracle APEX 3.1

Found out the hard way that the new property “Runtime Where Clause” for processes (eg. Fetch, DML) has a serious bug. The value of the property gets exported and is contained in the export file of an application, but it isn’t set when you import an application!!!

Because most of us are not developing on the production system, that bug is a real show stopper for that feature, because you never get the identical application onto the production system or to the customer.

The problem has been reported and according to Scott from the APEX team, it’s getting fixed in 3.1.1

Note: The “Optional Where Clause” of “Get Next or Previous Primary Key Value” processes is not effected by that behavior, this property was already available before Oracle APEX 3.1