Colsort tied to hidecolumn

(3 posts) (2 voices)
  • Started 2 years ago by nsepetys
  • Latest reply from nsepetys
  1. nsepetys, Member

    Hello myDBR Representative,

    It appears that if you hide a column that uses the colsort command it will also hide the corresponding column used for sorting. In other words if colA is used for display purposes and colB is used for sorting. If I want to hide colA, it will also hide colB (when using the hidecolumn command). Up until we updated to 4.9 we could use the column for sorting (data column) for the export to excel, since the presentation of data usually doesn't work well when translating to excel. Is this hiding logic intentional? If it is intentional is there a work around we can use for now?

    - Noah

    Posted 2 years ago #
  2. myDBR Team, Key Master

    Noah,
    yes, that is intentional. The aim is to reduce the code needed for the common functions.

    myDBR provides quite a many commands that use additional columns to include the parameter to be used (usually data based). Prior 4.9 when using commands like this, one needed to hide the extra columns as they were, in most cases, not included in the final report. Since 4.9 myDBR automatically hides these columns (no need for separate dbr.hidecolumn).

    Columns that are that are automaticlly hidden are the ones that are used as parameter to following commands:

    • dbr.rowstyle
    • dbr.rowclass
    • dbr.cellstyle
    • dbr.cellformat
    • dbr.tooltip
    • dbr.cellclass
    • dbr.sortcol
    • dbr.rowstyle
    • dbr.rowclass
    • dbr.footer.cellclass
    • dbr.footer.cellstyle

    If you still want to show the column, just select it twice in the result set.

    --
    myDBR Team

    Posted 2 years ago #
  3. nsepetys, Member

    Makes sense. Thanks for explaining.

    Posted 2 years ago #

Reply

You must log in to post.