> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/form-node-parts/jsgrid-report-part.md).

# jsgrid Report Part

### Description

The jsgrid part is predominantly a form-oriented node you can use to collect multiple pieces of data for a range of categories. In addition, it can be used to neatly present the results of a collection as a report part. It is especially useful for the simple presentation of arrays in the LogicNets Assessment Framework.

This article is limited to the features of the jsgrid part that can be used for reporting features. See the article called jsgrid for information on using jsgrid as a form part node.

Example

Click [here](/release-9/example-gallery/how-to-guides/how-to-guide-hard-and-soft-matching-applications.md) to access a sample project that includes the js grid report part.

### Use

For any multi-dimensional array, you can use this part to present multiple elements in tabular style. The parameter settings allow for a title, column headers with interpolation (i.e., you can use *$(...)* to incorporate modeled variables in the title), and column sorting. You can manually style the grid using CSS.

IMPORTANT: note that the jsgrid part will not be visible on a PDF due to the way it is rendered. Instead, use a report-item node to present a collection in tabular form (utilizing the value template feature of that part).

### Editor Fields

| Tab             | Field Name            | Description                                                                                                                                                          | Type/Options                 | Optional/Mandatory |
| --------------- | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- | ------------------ |
| Basic           | Collection            | This is where you specify the path of the variable that contains the array to be shown in the table.                                                                 | Data Object                  | Mandatory          |
| Basic           | Grid Caption          | Enter a title for the table here. This can include $(..) constructions.                                                                                              | Text                         | Mandatory          |
| Basic - columns | Name                  | This is where you enter a variable name from those defined in the collection.                                                                                        | Data Object                  | Mandatory          |
| Basic - columns | Title                 | Enter the title for the column here. This can include $(...) constructions.                                                                                          | Text                         | Mandatory          |
| Basic - columns | Type                  | In this field, choose the variable type from the dropdown menu.                                                                                                      | Text \| Number               | Mandatory          |
| Basic - columns | Width                 | In this field you can specify a width for any/all columns in percentage or pixel terms. Any columns without a predetermined width share the remaining width equally. | \[percent %] \| \[pixels px] | Optional           |
| Basic           | Allow column sorting  | Check this box to allow the user to sort on any column by clicking the title.                                                                                        | Yes \| No                    | Optional           |
| Basic           | Allow column resizing | Check this box to allow the user to drag and drop column separators to expand or collapse the width of any selected column.                                          | Yes \| No                    | Optional           |
| Basic           | Use paging            | Check this box to limit total number of rows shown on the screen. Subsequent rows are shown when the user selects a different page via a dropdown menu.              | Yes \| No                    | Optional           |

### Example of a Completed Part Editor

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-f6ff69f7ba24cada974de2b0a1624fe3a239c75f%2F7731cf88-3990-47f9-bc50-33dca73a104d.png?alt=media)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/form-node-parts/jsgrid-report-part.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.