User defined column headers in listing reports

by André Friese on September 12, 2018

It would be nice to have the option to set column header different from the fieldname.

Especially for reports with related items, when displaying any value from the related item the related field name is always added to the actual fieldname. This results in very long column headers with more than one line breaks.

e.g. we are using reports on stateforms to provide some information of related fields. The reports are inside a groupbox, which is labeled with the item. Like "Related Dynamic Problem". In the Report itself the columns are labeled like "ItemID (Related Dynamic Problem)", "State (Related Dynamic Problem)" etc.

Currently we are forced to remove the suffix (Related Dynamic Problem) with Javascipt, but actually we just want to give our own labels to the columns.

  • Ideas

    Status
  • Please login to view any attachments.

  • Hi,

    I checked with Development and an Advanced report developer can define own names for fields, but this feature does not support sub-relational fields, so problem with long names with qualifiers cannot be solved there.

    That said, we'd be resistant to this enhancement because:
    1. This could be a source of confusion for users in the organization who use such reports because they will not be able to relate that information at report header to exact well-known names of fields used universally at items, workflows, etc.
    2. Actual problem should be invalid initial names of fields (and looks like this is what you are trying to solve).
    3. There is no problem of displaying such fields and report data because browsers easily wraps long names at the header or data so the report looks nice.

    Since you already have solution for this implemented with javascript, for the rest of customers this, most likely, would be just source of confusion in both aspects (i.e. random names for standard fields and lack of qualifiers for joined/related data).
    David J. Easter Commented by David J. Easter October 05, 2018
    #1 Reviewer  -  

    Hi,

    I checked with Development and an Advanced report developer can define own names for fields, but this feature does not support sub-relational fields, so problem with long names with qualifiers cannot be solved there.

    That said, we'd be resistant to this enhancement because:
    1. This could be a source of confusion for users in the organization who use such reports because they will not be able to relate that information at report header to exact well-known names of fields used universally at items, workflows, etc.
    2. Actual problem should be invalid initial names of fields (and looks like this is what you are trying to solve).
    3. There is no problem of displaying such fields and report data because browsers easily wraps long names at the header or data so the report looks nice.

    Since you already have solution for this implemented with javascript, for the rest of customers this, most likely, would be just source of confusion in both aspects (i.e. random names for standard fields and lack of qualifiers for joined/related data).

    No, I did not try this, because it's really too much effort for just renaming columns. I would need this for more than one report, which means I'd have to create al lot of XML files for all the views which are at the end quite similar to my primary tables.
    Besides I want to be flexible and be able to add or remove columns whenever I want, without recreating the XML and view and restarting IIS.
    So actually, this is not really an useful workaround.
    André Friese Commented by André Friese September 25, 2018
    Top 50 Reviewer  -  

    No, I did not try this, because it's really too much effort for just renaming columns. I would need this for more than one report, which means I'd have to create al lot of XML files for all the views which are at the end quite similar to my primary tables.
    Besides I want to be flexible and be able to add or remove columns whenever I want, without recreating the XML and view and restarting IIS.
    So actually, this is not really an useful workaround.

    Have you tried using Advanced Reporting for this?
    David J. Easter Commented by David J. Easter September 24, 2018
    #1 Reviewer  -  

    Have you tried using Advanced Reporting for this?

     

PrintEmail