Invalid date format after APEX upgrade

Question

We are currently working on upgrading our applications from 1.6 to the new APEX 3.2 version. After the upgrade of one of our systems I have a tabular form that is returning the error 'Invalid date format found'. The date that is getting entered into the system is being displayed and choosed via a sql popup. The code for the pop up is
SQL CODE
create or replace view next_weeks as
with t as (
select
trunc(sysdate) + (rownum - 1) / 2 d
from
dual
connect
by rownum <= 28)
, call_info as (
select
c.call_identifier, c.callback_date, c.callback_cancelled
from uid_csr_schedule c
select
to_char(d, 'fmDy MM/DD/YYYY AM') l
, to_char(d, 'dd-mon-yy hh:mi:ss AM') v
,to_char(d, 'mm/dd/yy hh:mi:ss AM') o
from
t
where
((select count(callback_date) from call_info ci where ci.callback_date = t.d
and (ci.callback_cancelled is null or ci.callback_cancelled !='Y'))) <
(select csr_calls_per_period from uid_sch_system_default)
minus
select
to_char(d, 'fmDy MM/DD/YYYY AM') l
, to_char(d, 'dd-mon-yy hh:mi:ss AM') v
,to_char(d, 'mm/dd/yy hh:mi:ss AM') o
from
t
where
(select count(callback_date) from call_info ci where ci.callback_date = t.d
and (ci.callback_cancelled is null or (ci.callback_cancelled !='Y')))
=(select override_amt from uid_sch_call_override
where (to_char(begin_date,'dd-mon-yy') || ' ' || upper(period)) = to_char(t.d, 'dd-mon-yy AM'))
union select
to_char(d, 'fmDy MM/DD/YYYY AM') l
, to_char(d, 'dd-mon-yy hh:mi:ss AM') v
,to_char(d, 'mm/dd/yy hh:mi:ss AM') o
from
t
where
((select count(callback_date) from call_info ci where ci.callback_date = t.d
and (ci.callback_cancelled is null or ci.callback_cancelled !='Y'))) >=
(select csr_calls_per_period from uid_sch_system_default)
and
(select count(callback_date) from call_info ci where ci.callback_date = t.d
and (ci.callback_cancelled is null or (ci.callback_cancelled !='Y')))
<
(select override_amt from uid_sch_call_override
where (to_char(begin_date,'dd-mon-yy') || ' ' || upper(period)) = to_char(t.d, 'dd-mon-yy AM'))
order by o
The form then has the item set as a popup with a date format mask of dd-MON-yy hh:mi:ss AM. The popup displays fine and the date is shown in the field but the error is received when I try to save the information. If I change the application global setting of date format mask to dd-MON-yy hh:mi:ss AM then this error goes away however, it creates problems on all the rest of my pages that use this date in the where clause of the queries. Is there a way to solve the problem above without having to change the globalization parameter or do I need to change this parameter and then redo those queries?
Thanks for your help!
Amber

Answer 1

Amber,
It's interesting that the problem goes away if you set the global date format to be the same as the column level. The column level should trump the global setting. What process is returning the error? Are you sure it's the MRU or could it be something custom?
You could consider adding a process before the MRU fires that uses alter session to change the date format.
Regards,
Dan
Blog: http://DanielMcGhan.us/
Work: http://SkillBuilders.com/