Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

Testing your Longview Table

Longview strongly recommends testing your Longview Table before you publish your Longview App to users.

Testing is considered complete after you have tested the following, if applicable to your Table:

  • The Table loads without any initial warnings displayed to the user.
  • The Table is read-only or editable, as desired. For more information, see Understanding why a Table is read-only.
  • The Table loads with all controls and images displayed as desired.
  • The Table loads with the correct valid values for drop-down lists and multiple selection lists.
  • The Table has the correct defaults for check boxes, if applicable.
  • The Table honors column order and correctly enables columns based on their EnabledCriteria, if applicable.
  • If you are providing a Table with preexisting data to your users (for example, through import), make sure that any yellow error indicators are resolved.

Understanding why a Table is read-only

There are three cases in which a Table will display as read-only:

  • if you did not include the column from the database table that is the primary key
  • if you created a Virtual DataTable without the WRITABLE option specified in the Table definition
  • if you set the ReadOnly function to TRUE in your Table View definition

Longview recommends that you use the ReadOnly function or create a virtual DataTable to provide your users with a Table that is read-only.

Understanding why buttons are disabled

If a user does not have symbol access for at least one of the symbols specified for a symbol column, and the symbol column is not nullable, the Add, Duplicate, and Delete buttons will be disabled in the Table, and the user will not be able to add new rows.
Published:

Testing your Longview Table

Longview strongly recommends testing your Longview Table before you publish your Longview App to users.

Testing is considered complete after you have tested the following, if applicable to your Table:

  • The Table loads without any initial warnings displayed to the user.
  • The Table is read-only or editable, as desired. For more information, see Understanding why a Table is read-only.
  • The Table loads with all controls and images displayed as desired.
  • The Table loads with the correct valid values for drop-down lists and multiple selection lists.
  • The Table has the correct defaults for check boxes, if applicable.
  • The Table honors column order and correctly enables columns based on their EnabledCriteria, if applicable.
  • If you are providing a Table with preexisting data to your users (for example, through import), make sure that any yellow error indicators are resolved.

Understanding why a Table is read-only

There are three cases in which a Table will display as read-only:

  • if you did not include the column from the database table that is the primary key
  • if you created a Virtual DataTable without the WRITABLE option specified in the Table definition
  • if you set the ReadOnly function to TRUE in your Table View definition

Longview recommends that you use the ReadOnly function or create a virtual DataTable to provide your users with a Table that is read-only.

Understanding why buttons are disabled

If a user does not have symbol access for at least one of the symbols specified for a symbol column, and the symbol column is not nullable, the Add, Duplicate, and Delete buttons will be disabled in the Table, and the user will not be able to add new rows.
For an optimal Community experience, Please view on Desktop