Customisable for fields that have sub fields or columns (Name, Address, Matrix, Configurable List...) if they are presented as single or as multiple

  • tbawa
    Asked on August 4, 2015 at 9:57 AM
    Customisable for fields that have sub fields or columns (Name, Address, Matrix, Configurable List...) if they are presented as single or as multiple columns - again separate the form presentation from the report presentation as the audience or the way its processed may differ
  • Charlie
    Replied on August 4, 2015 at 10:41 AM

    Hi again,

    Could you give a sample on this? What I understand is that you would like to have an option to convert the fields with sub fields to be outputted as one column or multiple column (depending on the number of sub fields).

    For the fields with sub fields, they are separated to multiple columns.

    Customisable for fields that have sub fields or columns (Name, Address, Matrix, Configurable List Screenshot 30

     

    In this example, the Address sub fields are separated on each column. Same with the Matrix field. This allows to easily manage and import the data to other fields when needed.

    For the HTML Table Listing report, they are also separated on separated columns.

    Customisable for fields that have sub fields or columns (Name, Address, Matrix, Configurable List Screenshot 41

     

     

    To confirm, you would like to have an option for the data on the fields with sub fields to be presented on either multiple columns (which already exist) OR in one column (which means they will be concatenated). Is that correct?

    Thank you.

  • tbawa
    Replied on August 4, 2015 at 11:11 AM

    There seem to be some inconsistencies in that the Grid reports treat an input field that has sub fields (e.g. a Name) as a single field while the Excel reports treat it as separate fields. I would opt for making it consistent can configurable for these.

    Matrix fields are also treated differently. In Excel they are completely 'linearised' while in Grids they are shown as everything in one cell.

    Configurable Lists on the other hand are shown in all reports in one cell.

    I guess for Configurable Lists a fully 'linearised' representation is undesirable as that would lead to a variable number of columns.

    So we end up the the following combinations:

    Multi Sub Field fields: one row one column | one row multiple columns

    Matrix fields (or generally grids with known fixed dimensions): all in one cell | one row with multiple column (vertically sliced) | one column with multiple rows (horizontally sliced) | multiple column and multiple rows | one row and number of rows * number of columns columns (linearized)

    Configurable Lists (or generally for widgets that have an unknown number of rows): all in one cell | one row with multiple columns (vertically sliced) | one column with multiple rows (horizontally sliced) | multiple column and multiple rows

     

    Cheers

  • Charlie
    Replied on August 4, 2015 at 12:36 PM

    Thank you for pointing it out. Unfortunately, I believe we adding the Configurable list widget on this request might confused the developers are we also have a lot of widgets that outputs multiple entries, and they might vary from the data structure on how they were developed. CSV, Excel, Grid and Table is part of the Reports function so I believe that feature will still cover them.

    The complexity of the combinations might be confusing when implemented on the reports, and not sure how the developers will be adding it for each report. 

    So to summarize, you would like the following options to be outputted:

    1. In Multi Sub Fields you'll have an option to:

    1.a One row one column

    1.b One row multiple column

     

    2. In Matrix fields you haven an option to:

    2.a All in one cell

    2.b One row multiple column

    2.c One column with multiple rows

    2.d multiple column and multiple rows | one row and number of rows * number of columns columns (linearized)

     

    It seems like the options are quite complex and not sure if that will be implemented to all of the report types. I believe using the API would be beneficial to output the submission data with this complexity.