Forum Stats

  • 3,781,163 Users
  • 2,254,485 Discussions
  • 7,879,599 Comments

Discussions

apex 21.2 BUG: apex_item.checkbox and #ROWNUM# not working

massi_cic
massi_cic Member Posts: 6 Green Ribbon

Hi all,

I have and old apex application 4.1 migrated to 21.2. In some pages I have a classic report where I implemented a checkbox in order to select and delete certain rows.

SQL Query:

select apex_item.checkbox (50, '#ROWNUM#',NULL, NULL, ':', 'f50_' || '#ROWNUM#') "select", ...

then in the report I have this:

<input type="checkbox" name="f50" value="#ROWNUM#" id="f50_#ROWNUM#">

I know that replacing '#ROWNUM#' with rownum is "working" (not as I actually need) , because i got this

<input type="checkbox" name="f50" value="3" id="f50_3">

But when selecting rows I must rely on report '#ROWNUM#' instead of database-level rownum

My question is: WHY Apex is no longer corretly interpreting '#ROWNUM#' ?

Thank you all

Max

Tagged:

Best Answer

Answers

  • tirone
    tirone Member Posts: 176 Bronze Badge

    Hy,

    i ran into the same problem.

    I migrated my application from Apex 4.2 release to 21.2 release.

    On many pages I have used this technique to delete records from the DB:

    I present the records in a classic report with a checkbox using a query like this:

    select

    apex_item.checkbox (10,

                               '# ROWNUM #',

                               NULL,

                               NULL,

                               ':',

                               'f10_' || '# ROWNUM #'

                              ) "select",

    .....................

    ..................

    then in a process like this I delete the selected records:

    DECLARE

    vRow BINARY_INTEGER;

    objid varchar2 (200);

    BEGIN

    FOR i IN 1 .. apex_application.g_f10.COUNT

    LOOP

    vRow: = apex_application.g_f10 (i);

    objid: = apex_application.g_f02 (vRow);

    delete from .....

    where obj_id = objid;

    END LOOP;

    END;


    But after upgrading to release 21.2 # ROWNUM # is no longer valued; therefore the process fails

    Any help will be appreciated.

    Thank you all

    regards

    saverio

  • Carsten Czarski-Oracle
    Carsten Czarski-Oracle Member Posts: 1,258 Employee

    Hi,

    thank you for reporting this. I can reproduce the behavior, which appears to be introduced with the latest release APEX 21.2. In APEX 21.1 this does not occur.

    I have filed bug 33600780 to track this issue. We will work on fixing this as soon as possible.

    Best regards

    -Carsten

  • tirone
    tirone Member Posts: 176 Bronze Badge

    Many Thanks Carsten,

    I hope to get feedback on a fixing or at least a workaround as soon as possible.

    I have several applications with many pages where I have adopted the technique that I have illustrated in the post and I would like to upgrade them to release 21.2, but at the moment I am stuck.

    Changing this technique would be too expensive for my company.

    A question :

    Will I get information about the solution in this post or should I check on My Oracle Support?

    Best regards

    Saverio

  • Carsten Czarski-Oracle
    Carsten Czarski-Oracle Member Posts: 1,258 Employee

    Hi Saverio,

    we plan on making the fix for this available with the APEX "bundle patch", for which we plan to release within the next few weeks - I don't have a concrete ETA for this yet.

    Best regards

    -Carsten

  • User_QYZM7
    User_QYZM7 Member Posts: 1 Green Ribbon

    Hi,

    I have the same problem.

    I migrated my application from Apex 4.2 release to 21.2 release.

    Do you know a workaround?

    When will the bugfix be released?

    Thank you

    Fabio

  • Carsten Czarski-Oracle
    Carsten Czarski-Oracle Member Posts: 1,258 Employee
    Accepted Answer

    Hi Fabio,

    the patch bundle was released today: download and apply patch number 33420059, which includes the fix for that issue.

    Best regards

    Carsten

  • massi_cic
    massi_cic Member Posts: 6 Green Ribbon

    Thank you very much Carsten,

    During these days we are applying the patch and let you know!

  • tirone
    tirone Member Posts: 176 Bronze Badge

    Many Thanks Carsten,

    we applied the patch and the problem was fixed.

    Best regards

    saverio