apex_item.date_popup2 when over 100 rows — oracle-tech

    Forum Stats

  • 3,708,965 Users
  • 2,241,167 Discussions
  • 7,840,723 Comments

Discussions

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

apex_item.date_popup2 when over 100 rows

Scott WesleyScott Wesley Posts: 5,840 Gold Crown
edited September 2020 in APEX Discussions

If I define a classic report with one column defined using apex_item.date_popup2, it renders as expected until the 100th row.

select rownum rn, apex_item.hidden(p_idx => 10, p_value => rownum, p_attributes => 'id="f10_'||rownum||'"') hidn,apeX_item.text(p_idx => 5) txt,apex_item.date_popup2            (p_idx       => 01            ,p_value     => sysdate            ,p_size      => 7            ,p_attributes => 'class="apx-date-picker" disabled '            ,p_maxlength => 10            ,p_max_value => null            ,p_min_value => null) dtrfrom dual connect by level <= 105

For instance, the above query produces rows as expected until the 100th record - then the icon stops rendering

pastedImage_2.png

And the console complains

[DOM] Found 5 elements with non-unique id #apex_date_01_10:

pastedImage_18.png

The 100th row uses

id="apex_date_01_99"

While the 101st row uses

id="apex_date_01_10"

And the icon button simply isn't rendered.

This is on APEX 19.2, replicated on 20.1, also applicable when using pagination.

pastedImage_15.png

This doesn't seem expected?

It's as if the ID is just getting trimmed, but I'm curious if there could be a workaround - beyond generating the entire string myself.

Tagged:
Scott Wesleyjariola

Best Answer

  • fac586fac586 Senior Technical Architect Posts: 19,191 Black Diamond
    edited September 2020 Accepted Answer
    Scott Wesley wrote:If I define a classic report with one column defined using apex_item.date_popup2, it renders as expected until the 100th row.
    1. selectrownumrn,apex_item.hidden(p_idx=>10,p_value=>rownum,p_attributes=>'id="f10_'||rownum||'"')hidn
    2. ,apeX_item.text(p_idx=>5)txt
    3. ,apex_item.date_popup2
    4. (p_idx=>01
    5. ,p_value=>sysdate
    6. ,p_size=>7
    7. ,p_attributes=>'class="apx-date-picker"disabled'
    8. ,p_maxlength=>10
    9. ,p_max_value=>null
    10. ,p_min_value=>null)dtr
    11. fromdual
    12. connectbylevel<=105
    select rownum rn, apex_item.hidden(p_idx => 10, p_value => rownum, p_attributes => 'id="f10_'||rownum||'"') hidn ,apeX_item.text(p_idx => 5) txt ,apex_item.date_popup2  (p_idx => 01  ,p_value => sysdate  ,p_size => 7  ,p_attributes => 'class="apx-date-picker" disabled '  ,p_maxlength => 10  ,p_max_value => null  ,p_min_value => null) dtr from dual  connect by level <= 105 

    For instance, the above query produces rows as expected until the 100th record - then the icon stops rendering
    pastedImage_2.png

    And the console complains

    [DOM] Found 5 elements with non-unique id #apex_date_01_10:

    pastedImage_18.png

    The 100th row uses

    1. id="apex_date_01_99"
    While the 101st row uses
    1. id="apex_date_01_10"
    id="apex_date_01_10"
    And the icon button simply isn't rendered.This is on APEX 19.2, replicated on 20.1, also applicable when using pagination.
    pastedImage_15.png

    This doesn't seem expected?

    Long term bug: date_popup2 gets displayed only for first 100 rows

    Unlikely to be fixed following the deprecation of APEX_ITEM.

    It's as if the ID is just getting trimmed, but I'm curious if there could be a workaround - beyond generating the entire string myself.

    As described in the linked thread that would be the required workaround.

    Scott Wesleyjariola

Answers

  • fac586fac586 Senior Technical Architect Posts: 19,191 Black Diamond
    edited September 2020 Accepted Answer
    Scott Wesley wrote:If I define a classic report with one column defined using apex_item.date_popup2, it renders as expected until the 100th row.
    1. selectrownumrn,apex_item.hidden(p_idx=>10,p_value=>rownum,p_attributes=>'id="f10_'||rownum||'"')hidn
    2. ,apeX_item.text(p_idx=>5)txt
    3. ,apex_item.date_popup2
    4. (p_idx=>01
    5. ,p_value=>sysdate
    6. ,p_size=>7
    7. ,p_attributes=>'class="apx-date-picker"disabled'
    8. ,p_maxlength=>10
    9. ,p_max_value=>null
    10. ,p_min_value=>null)dtr
    11. fromdual
    12. connectbylevel<=105
    select rownum rn, apex_item.hidden(p_idx => 10, p_value => rownum, p_attributes => 'id="f10_'||rownum||'"') hidn ,apeX_item.text(p_idx => 5) txt ,apex_item.date_popup2  (p_idx => 01  ,p_value => sysdate  ,p_size => 7  ,p_attributes => 'class="apx-date-picker" disabled '  ,p_maxlength => 10  ,p_max_value => null  ,p_min_value => null) dtr from dual  connect by level <= 105 

    For instance, the above query produces rows as expected until the 100th record - then the icon stops rendering
    pastedImage_2.png

    And the console complains

    [DOM] Found 5 elements with non-unique id #apex_date_01_10:

    pastedImage_18.png

    The 100th row uses

    1. id="apex_date_01_99"
    While the 101st row uses
    1. id="apex_date_01_10"
    id="apex_date_01_10"
    And the icon button simply isn't rendered.This is on APEX 19.2, replicated on 20.1, also applicable when using pagination.
    pastedImage_15.png

    This doesn't seem expected?

    Long term bug: date_popup2 gets displayed only for first 100 rows

    Unlikely to be fixed following the deprecation of APEX_ITEM.

    It's as if the ID is just getting trimmed, but I'm curious if there could be a workaround - beyond generating the entire string myself.

    As described in the linked thread that would be the required workaround.

    Scott Wesleyjariola
  • Scott WesleyScott Wesley Posts: 5,840 Gold Crown
    edited September 2020

    Thanks, Paul. Not sure how I missed that the first round of searching.

    ,p_item_id => 'apex_date_01_'||to_char(row_number() over (order by my.order), 'tm9')

    Also feel I could have worked that one out myself, I must be slipping ;p

Sign In or Register to comment.