Overview
In the legacy Construct, WebApp Designers could set ColumnSpan, RowSpan, and LineBreak spanning properties on page columns to control how records were displayed across multiple grid cells and rows.
Cloud Construct takes a different approach, shifting from a single-grid-per-record model to a multi-container presentation strategy. This provides:
Cleaner grid views with only essential columns visible
Better responsiveness for different screen sizes
User control over which data they want to see
Flexible data density achieved at the page layout level, not the cell level
Updated Methodology
In Cloud Construct, the grid is designed with a one-row-per-record model and does not support column/row spanning. Instead, achieve similar data density and user flexibility through a two-part approach:
Approach A: Multiple Container Strategy
Redesign your page to use multiple containers (grids and property cards) that are bound to the same record via shared binding criteria. This provides:
Clean grid view with priority fields
Detailed information accessible in linked containers
Better UX than grid row wrapping
Data density achieved at the page presentation layer rather than grid cell layer
Approach B: Column Visibility Control (Recommended)
For fields that must appear in the grid (for search/filter support) but aren't needed by all users, configure them as hidden by default using is_hidden_on_grid_by_default: true and make them available via the Choose Columns in grid’s menu.