Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Label Column Span of 2 Error - This is not supported as the page item itself only has 2 Column(s) av

Tony FatourosJun 28 2017 — edited Jun 28 2017

Hi,

Using the latest public release of Oracle APEX v5.1.

Really hoping someone can assist here as I'm not too sure what I am doing wrong with regards to trying to horizontally set some page items within a button container and unfortunately am receiving the below error.

FYI, my button container region has a column span of 12 as I want to use the full width of the page. I have six page items that I want to place within this region but at soon as I include the sixth page item, I get the below error. If I don't display this sixth page item, I don't get the error message below.

It says that I have a Label Column Span of 2 but I actually don't with all the page items set to Automatic under Grid section.

I really don't know what is going on here since I have the whole 12 grid to play with.

Any help would be great.

Thanks.

Tony.

Error Message:

Label of Page Item P2_REF_NO cannot be rendered as the label column span grid setting for this page item is invalid. It is set to be displayed with a Label Column Span of 2. This is not supported as the page item itself only has 2 Column(s) available.

Contact your application administrator.

Technical Info (only visible for developers)

  1. is_internal_error: true
  2. apex_error_code: WWV_FLOW_GRID_LAYOUT.LABEL_COLUMN_SPAN_TOO_BIG
  3. component.type: APEX_APPLICATION_PAGE_ITEMS
  4. component.id: 62060709389539220
  5. component.name: P2_REF_NO
  6. error_backtrace:
  7. 7.  ----- PL/SQL Call Stack -----
  8. 8.    object      line  object
  9. 9.    handle    number  name
  10. 10. 0x275a36ca8       940  package body APEX_050100.WWV_FLOW_ERROR
  11. 11. 0x275a36ca8      1008  package body APEX_050100.WWV_FLOW_ERROR
  12. 12. 0x275a36ca8      1400  package body APEX_050100.WWV_FLOW_ERROR
  13. 13. 0x277e245d8       382  package body APEX_050100.WWV_FLOW_GRID_LAYOUT
  14. 14. 0x1973387d0      1543  package body APEX_050100.WWV_FLOW_FORMS
  15. 15. 0x152e41650      1376  package body APEX_050100.WWV_FLOW_DISP_PAGE_PLUGS
  16. 16. 0x152e41650      1875  package body APEX_050100.WWV_FLOW_DISP_PAGE_PLUGS
  17. 17. 0x152e41650      1200  package body APEX_050100.WWV_FLOW_DISP_PAGE_PLUGS
  18. 18. 0x152e41650      1862  package body APEX_050100.WWV_FLOW_DISP_PAGE_PLUGS
  19. 19. 0x152e41650       982  package body APEX_050100.WWV_FLOW_DISP_PAGE_PLUGS
  20. 20. 0x17fb06df8      2393  package body APEX_050100.WWV_FLOW_PAGE
  21. 21. 0x17fb06df8      2620  package body APEX_050100.WWV_FLOW_PAGE
  22. 22. 0x25db94968      4922  package body APEX_050100.WWV_FLOW
  23. 23. 0x135b82608       173  procedure APEX_050100.F

0x272acea98         2  anonymous block

This post has been answered by AnnelizeF on Jun 28 2017
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jul 26 2017
Added on Jun 28 2017
5 comments
2,546 views