Skip to Main Content
Feature Request FR-620
Product Area Application Builder
Status CLOSED

17 Voters

Classic Reports: Unlimited conditional column/row templates

fac586 Public · Nov 15 2013

Custom report templates should support an unlimited number of conditional column/row templates rather than being limited to 4 as at present. (The UI would be similar to the multi-row implementation of Dynamic Action true/false actions.)

We reviewed this idea carefully, and while it was interesting, we concluded that due to all the internal implications we need to take into account, it is unlikely to make its way into APEX.

Comments

Comments

  • azmat OP 12.2 years ago

    Would dearly love this. The limit of 4 really is too low.

  • gemma wood OP 10.6 years ago

    10 would be nice.

  • jayson hanes Admin OP 4.1 years ago

    Is this need still relevant?

  • fac586 OP 4.1 years ago

    Absolutely!

  • jayson hanes Admin OP 4 years ago

    I think it's safe to say that this functionality is on the roadmap, as per this idea https://apex.oracle.com/ideas/FR-1869 - "Refresh region on PL/SQL Dynamic Content"

  • fac586 OP 4 years ago

    I think it's safe to say that this functionality is on the roadmap, as per this idea https://apex.oracle.com/ideas/FR-1869 - "Refresh region on PL/SQL Dynamic Content"

    Sorry Jayson, I have to totally disagree. Report templates are a far superior low-code solution for generating custom content than PL/SQL Dynamic Content regions:

    • Less code all round
    • Code is far simpler and clearer: just HTML + column substitution strings + SQL expressions instead of htp.p + ifs + loops + variables + all the ||, (), ', " and ;
    • Works seamlessly with other declarative features such as pagination, column formatting, and HTML Expressions
    • Reusable
    • Already supports dynamic refresh

    In 15+ years of APEX development I think I've created two PL/SQL Dynamic Content regions, and on the forum I've yet to see one that I couldn't convert into a custom report template.

    I haven't voted for FR-1869 because (a) I don't need it; and (b) it will result in the production of code that is poor quality and difficult to maintain. Conversely, If I was only allowed to pick one feature for implementation it would be this one.

  • jayson hanes Admin OP 4 years ago

    okay.. I'm wrong then. I reverted the status. Sorry about that!

  • fac586 OP 4 years ago

    Thanks!