This content has been marked as final. Show 10 replies
We are working for a generic fix for the patch set, but you can fix this right now by adding an id parameter to your call to htmldb_item.date_popup / APEX_ITEM.DATE_POPUP
Though it's not in the documentation , an oversight that will be fixed, you can generate an id that overrides the APEX generated id. It is the next parameter after the attributes parameter.
So you immediate fix is to change your query like this,
Notice the call to the popup has 'datepicker_'||rownum added, this will set id for the date picker and it will now be set to datepicker_1 , datepicker_2 and so forth
select gl_rpt_item_id, description, act_flag, htmldb_item.hidden(1, gl_rpt_item_id) as item_id, htmldb_item.date_popup(6,rownum,date_value,'DD-MON-YYYY',11,11,decode(act_flag,'I','"DISABLED"'),'datepicker_'||rownum) new_gl_dt from gl_rpt_item where is_clinical = 'Y' and act_flag <> 'I'
I took the decode out so you could see the id change easier.
I figured this out and it was to do with my rownum. I appended 'datepicker_'||rownum into my SQL to see what was going on.
My second row on the report had a value for the above as datepicker_10 so when using it, the field in row 10 of my report was getting populated.
What I did was include the rownum in my SQL and then order it by rownum and this seem to fix it.
I'm coming across this same issue with the date picker updating the first row, but I'm using APEX 3.0.0.00.20.
I've tried adding the date_picker||rownum but it doesn't work. i.e.
Any suggestions (and upgrading isn't a valid option)????