[Navigation] Global Search > Utilities > Form Builder
[Accordion] Overview
The Grid View field provides a structured, table-based layout to capture and present multiple related values efficiently.
Unlike open-ended or event-driven fields, it is designed for concise, repeatable data entry. By bringing related data points together in a single view, it allows clinicians to review information at a glance, promoting clarity, consistency, and efficient documentation.
Grid View enforces a predefined number of rows and columns, making it ideal for scenarios where:
- A fixed number of entries are required
- Data needs to be reviewed side-by-side
- Consistency is more important than flexibility
- Users should not control the number of rows
Grid Views are ideal for structured, short-form data entry and quick clinical review.
[Note] If entries need to expand over time or vary from one patient to another, a Repeating List is the better choice, as it offers the flexibility to add or adjust entries as needed.
Common Use Cases:
- Weekly mood ratings: Track changes over a defined period
- Recent therapy sessions: Review a fixed number of sessions together
- Short-term treatment goals: Requiring a consistent, side-by-side comparison
- Medication compliance tracking: Quickly assess adherence patterns
- Structured assessments: Where standardized responses must be captured and reviewed at a glance
[Accordion] How Grid View Is Different from Other Field Types
The Grid View is not a single field; it is a container that renders a table. Each column is defined by a field added to the Grid View, and each row is defined by a Label control with a Data Source.
Key distinctions:
- Rows are fixed, not user-generated
- All entries are visible at once, without scrolling or expansion
- Users cannot add or remove rows
- Structure is enforced, reducing data variability
This makes Grid View especially effective for snapshot-style clinical data, where consistency and visibility are more important than flexibility.
[Accordion] Why Grid View Configuration Is Unique
Unlike other controls, Grid View configuration starts by defining rows first, not fields
- A Label control determines the number of rows
- The label’s Data Source values determine how many rows appear
- Additional controls define columns, not individual fields
This design allows Grid View to behave more like a matrix than a form section, which is why it supports only a specific set of controls and requires upfront planning.
[Accordion] Getting Started
Grid View configuration is intentionally distinct from other controls.
[Q] Step 1: Add a Label Control to Define Number of Rows
[A]
- Once you add a Grid View control, the Grid View configuration screen will appear.
- If you need to return here later, select the Grid View, look for the "Add Sub Item" property, and click the Set Sub Fields cell.
- The Label control, which will appear by default, defines how many rows will appear in the Grid View.
- The Label must have a Data Source.
- The list values in the Data Source determine how many rows appear.
- Each list value represents one row.
[Q] Step 2: Add Other Fields to Define Columns
[A] Each field added to the Grid View becomes a column.
Supported Column Types:
- TextBox
- Counter
- Dropdown
- Date Picker
- Time Picker
- Label
- Checkbox
Each column in a Grid View repeats across all rows defined by the Label Control.
[Accordion] How Grid Views Behave at Runtime
- All rows and columns are visible at once.
- Rows cannot be dynamically added or removed.
- Data entry is structured and efficient.
- Ideal for side-by-side comparison.
[Accordion] Design Considerations & Best Practices
- Use Grid Views for small, fixed datasets: Grid Views work best when the number of rows and columns is known in advance. They are ideal for capturing consistent data points that do not need to grow over time.
- Keep the column count manageable: Limit the number of columns to maintain readability. Too many columns can make the grid difficult to scan and use, especially on smaller screens.
- Use concise, clear labels: Short, descriptive labels prevent crowded layouts and make it easier for users to understand what information is required at a glance.
- Avoid long text fields: Grid Views are not designed for narrative input. Use short text, numeric fields, checkboxes, or dropdowns instead of large free-text areas.
- Confirm the label Data Source matches the intended row count: Ensure the Data Source used for row labels aligns with the number of rows you expect to display. This helps maintain consistency and prevents confusion during data entry and review.
[Accordion] Common Pitfalls to Avoid
- Forgetting to add the label first: Grid Views rely on labels to define rows. Skipping this step can result in an incomplete or nonfunctional grid.
- Using a dynamic list when a fixed list is needed: Grid View is designed for a set number of rows. If the data needs to grow or vary, a Repeating List is a better fit.
- Adding too many columns: Overloading the grid with columns can make it hard to read and use, reducing efficiency and increasing the chance of errors.
- Expecting users to add rows manually: Grid View does not support user-added rows. If users need to add entries, choose a control designed for flexible data entry.
- Reporting Considerations: Grid View provides limited capacity for reporting, as you are not directly creating a named field for every element of the Grid View. If reporting is critical for this data, you may want to consider adding distinct fields to collect all the information.