---
sourceDocument: Brazil Sales Customer Relationship Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/order-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Sales Customer Relationship Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Layouts: Field grid setup

# Layouts: Field grid setup {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Layouts: Field grid setup

A field grid is a layout component in ServiceNow that organizes multiple fields into a matrix or table format, allowing for repeated collection of the same set of information multiple times.
Unlike traditional sets, field grids support referencing other rows and can expand horizontally or vertically.
This feature is particularly useful when you need users to input repeated data entries efficiently.
Show full answer Show less  

## Field grid layout setup

To configure a field grid in a layout, you do not require a column set because the field grid itself generates rows and columns. Instead, you use specific row types:

* **fieldgrid**: Declares the use of a field grid in the layout.
* **fieldgriddata**: Defines each column within the field grid.
* **field**: Specifies each individual cell within the grid (not each row).

Fields intended for the grid should be defined beforehand and associated with the appropriate blueprint. Tools like Matrix Loader can assist in defining these fields.

Note that individual cells cannot have both a label and an input field simultaneously. If both are specified, only the input field will appear in the layout.

## Field grid UI controls

You can customize various UI aspects of the field grid by updating the **value** column in the layout CSV file. Customizable options include:

* **Gridline visibility:** Control display of gridlines between cells with options such as `all`, `horizontal`, `vertical`, or `none`. Default is `all`.
* **Dynamic column headers:** Use field names to dynamically set headers.
* **Field width:** Specify widths for columns or the entire grid using pixel values, viewport widths, or CSS calc() expressions.

## Fieldgrid and Fieldgriddata elements

These elements allow fine control over the grid's appearance and behavior by setting values in the layout CSV:

* **fieldgrid element values:**
  * `indexPre` and `indexPost`: Strings displayed before or after the row index number.
  * `indexVisible`: Toggle visibility of the index column (default is true).
  * `maximumHeight`: CSS max height for the grid (e.g., "180px").
  * `gridlines`: Controls gridline display as described above.
* **fieldgriddata element values:**
  * `fieldIndex`: Field name used for the column header (label must be blank if used).
  * `width`: Sets the width of the field, with several accepted formats (e.g., px, vw, calc()).

Specifying widths for any fieldgriddata element changes the overall grid width behavior to `auto`, allowing precise control of column sizes.

## Practical application for ServiceNow customers

ServiceNow customers can leverage field grids to streamline data collection when the same information needs to be gathered repeatedly, such as multiple entries with related data points. The ability to reference rows and customize grid appearance enhances both data integrity and user experience. By configuring field grids through CSV files and layout blueprints, customers can efficiently deploy complex, dynamic forms tailored to their business needs.  
A field grid collects multiple fields in a single layout, but unlike a set, it can reference other rows.

A field grid presents numerous fields in a matrixed layout. These are helpful when you need to request the same set of information a predetermined number of times. Field grids allow users to create a table of repeated values. In a
field grid, rows can reference other rows, while in a set a user cannot write rules between indexes.

Field grids can expand in columnar or row direction (that is, horizontally or vertically).

Define all fields that are intended to be displayed in the field grid. Matrix Loader is a good tool for this. Associate the fields with the blueprint in which they will be used.

## Field grid layout setup {#layouts-field-grid-setup__section_ytx_gtg_phc}

To add a field grid to the layout, a column set is not needed because the field grid creates the rows and columns. Instead, the following row types are needed:

* fieldgrid: this type tells the layout that a field grid will be used in the layout
* fieldgriddata: this type is used for each column of the field grid
* field: this type is needed for each cell in the field grid (not each row)

{#layouts-field-grid-setup__ul_z4b_4b4_3hc}

The first three images show the CSV file. The last image shows the corresponding user layout. The numbers above align with the numbers in the images below. (Because number 3 is shown several times, a letter is added for clarity.)
Individual cells in the field grid cannot have both a label and an input field. Note that by 3C, both a label and input field are added to the layout CSV file. However, only the input field goes in the layout.


[fieldGrid Sample Layout JSON](https://docs.google.com/document/d/123dT0vwmwBUWgyrEV5RzI3rH3WugJd2xUUkpI9O2Ias/edit?usp=sharing)

## Field grid UI controls {#layouts-field-grid-setup__section_njs_3tg_phc}

Various aspects of the field grid UI can be controlled by updating the value field in the layout CSV file:

* Gridline visibility
* Dynamic column headers
* Field grid field width
{#layouts-field-grid-setup__ul_ohq_514_3hc}

## Fieldgrid elements {#layouts-field-grid-setup__section_rxg_ltg_phc}

The following values can be added to the value column of fieldgrid elements:

* indexPre: String value to be displayed in the index column before the index number. optional
* indexPost: String value to be displayed in the index column after the index number. optional
* indexVisible: true \| false, whether to display the index number and column in the field grid layout. Optional, default: true
* maximumHeight: Maximum height to set in CSS px. I.e. "180px". optional
* gridlines: all \| horizontal \| vertical \| none, control how grid lines are displayed between cells. Optional, default is all.
{#layouts-field-grid-setup__ul_phq_514_3hc}

## Fieldgriddata elements {#layouts-field-grid-setup__section_dmh_mtg_phc}

The following values can be added to the value column of fieldgriddata elements:

* fieldIndex: name of field to use for header value. Optional. If included, the label for the fieldgriddata element should be blank.
* width: width of the fields. Optional. If included, examples of valid value are auto, 300 (px are assumed here), 300px, 20vw, and calc(100% - 100px).

{#layouts-field-grid-setup__ul_qhq_514_3hc}

Field grids default to 100% width. If even one width value is specified for a contained fieldgriddata component, the field grid's width changes to auto so that a specified width can be applied.
[Example field grid dynamic headers and grid lines CSV file](https://drive.google.com/file/d/1MrYYBg8_tjHOa2QfhHWLmkReNbRDmkA-/view?usp=share_link)

[Example field grid width CSV file](https://drive.google.com/file/d/130w2Cz-5R7z1BwFO7_o1rD9IIlPol3DQ/view?usp=share_link)

