Add columns to a Table

  1. On the Extended Properties page of a Table, click Columns.
  2. Enter a Display Name to appear as the column header at runtime, for example, Customer Name.
  3. Enter a Name to identify the column header during mapping.
    Note The name and display name can be the same.
  4. Select a Data Type for a column.

    Based on the selected data type, the controls on the Column Type list are displayed.

  5. On the ColumnType list, select the control to add to the column.

    The available controls are :

    • Text

    • Drop-down

    • CheckBox

    • Calender

    • Hyperlink

    • Image

    • Action List

  6. For Align Text, set the alignment for the column text. (Default: left-aligned)
  7. Change the column Width as needed. (Default: 100)
  8. By default, the column is visible at runtime. To restrict the visibility of the column at runtime, click No for Visible (Default: Yes)
  9. To restrict editing of column text at runtime, click No for Enabled. (Default: Yes)
  10. To wrap the text inside a table cell when the text is greater than the column width, so that entire text is displayed to the user without the need to expand the cell or hover over it to get a tooltip, click Yes for Wrap Text. (Default: No)
    When you view the table at runtime, the cell content wrap onto the next line. The text without spaces is not wrapped.
    Note
    • The Wrap Text property is only available when the data type for the column is String or Date, and the column type is Text.

    • This property is available for a Table control on desktop, tablet and mobile forms but not available on a capture form.

  11. Change the order of columns in a table using the Up/Down buttons.
  12. Add controls to the table column. See Add controls to a table column.
  13. Click Save.

Properties of a capture table column

Width

Change the column width as needed. (Default: 100)

Read-Only

Allow the user to edit the field at runtime. (Default: No)

If any fields in a table on a Capture form are set as hidden\read-only (Validation form>Table>Extended Properties>Column), then it can possibly prevent a user from completing a Validation activity. The reason is that when a user adds a row to a table, all the cells in that new row are marked invalid (including any hidden or read-only cells). As a result, all the visible cells in the table do not mark the table as valid and the user is not able to complete the Validation activity.

If you want to hide fields from one user but visible to others, you either define the hidden field as ‘Always Valid’. See Configure validation for document fields or define validation rules that run during the ‘Add Table Row’ event that will set the valid flag as ‘true’ for hidden and read-only cells. See Add field validation for document fields.

Multiline
Use the Multiline property to handle text that may go beyond one line, such as customer address. (Default: No)
Visible
Choose whether the column be visible at runtime. (Default: Yes)
Preserve Line Breaks
Allow preserving line breaks for a multi-line field when lassoing, so that the line breaks are preserved when data is populated in the field.