display the result of a view in an editable grid

Question

I am planning to display the result of a view in an editable grid . Can anyone please give me an example ? 
 The number of rows is fixed but i dont want to write a!gridRowLayout() 44 times as shown in the example of 2 rows 
 =load(
 local!items: {
 {item: "Item 1", qty: 1, unitPrice: 10},
 {item: "Item 2", qty: 2, unitPrice: 20}
 },
 a!gridLayout(
 label: "Grid Layout",
 instructions: "This is a grid layout",
 headerCells: {
 a!gridLayoutHeaderCell(label: "Item"),
 a!gridLayoutHeaderCell(label: "Qty", align: "RIGHT"),
 a!gridLayoutHeaderCell(label: "Unit Price", align: "RIGHT"),
 a!gridLayoutHeaderCell(label: "Total", align: "RIGHT")
 },
 rows: {
 a!gridRowLayout(
 contents: {
 a!textField(
 value: local!items[1].item,
 saveInto: local!items[1].item
 ),
 a!integerField(
 value: local!items[1].qty,
 saveInto: local!items[1].qty,
 align: "RIGHT"
 ),
 a!floatingPointField(
 value: local!items[1].unitPrice,
 saveInto: local!items[1].unitPrice,
 align: "RIGHT"
 ),
 a!textField(
 value: dollar(tointeger(local!items[1].qty) * todecimal(local!items[1].unitPrice)),
 readOnly: true,
 align: "RIGHT"
 )
 }
 ),
 a!gridRowLayout(
 contents: {
 a!textField(
 value: local!items[2].item,
 saveInto: local!items[2].item
 ),
 a!integerField(
 value: local!items[2].qty,
 saveInto: local!items[2].qty,
 align: "RIGHT"
 ),
 a!floatingPointField(
 value: local!items[2].unitPrice,
 saveInto: local!items[2].unitPrice,
 align: "RIGHT"
 ),
 a!textField(
 value: dollar(tointeger(local!items[2].qty) * todecimal(local!items[2].unitPrice)),
 readOnly: true,
 align: "RIGHT"
 )
 }
 )
 }
 )
)

Josh · Accepted Answer

If you are not on 17.2 you will need to use a!applyComponents(). You will also need to create a rule for your grid row layout. The following SAIL recipe gives an example of how to do this: docs.appian.com/.../recipe_add_edit_and_remove_data_in_an_inline_editable_grid.html

Josh · Answer

You can leverage a!forEach() to avoid hardcoding the grid rows: 
 
 =load(
 local!items: {
 {item: "Item 1", qty: 1, unitPrice: 10},
 {item: "Item 2", qty: 2, unitPrice: 20}
 },
 a!gridLayout(
 label: "Grid Layout",
 instructions: "This is a grid layout",
 headerCells: {
 a!gridLayoutHeaderCell(label: "Item"),
 a!gridLayoutHeaderCell(label: "Qty", align: "RIGHT"),
 a!gridLayoutHeaderCell(label: "Unit Price", align: "RIGHT"),
 a!gridLayoutHeaderCell(label: "Total", align: "RIGHT")
 },
 rows: a!forEach(
 items: local!items,
 expression: a!gridRowLayout(
 contents: {
 a!textField(
 value: index(fv!item, "item", null),
 saveInto: fv!item.item
 ),
 a!integerField(
 value: index(fv!item, "qty", null),
 saveInto: fv!item.qty,
 align: "RIGHT"
 ),
 a!floatingPointField(
 value: index(fv!item, "unitPrice", null),
 saveInto: fv!item.unitPrice,
 align: "RIGHT"
 ),
 a!textField(
 value: dollar(tointeger(index(fv!item, "qty", 0)) * todecimal(index(fv!item, "unitPrice", 0))),
 readOnly: true,
 align: "RIGHT"
 )
 }
 )
 )
 )
)

aloks0189 · Answer

There can be a use case, when your view returns duplicate Primary Key value (which is rare), when you go for pagingGrid, it will throw an error, because pagingGrid expects unique identifier, so in such cases we need to go for editable grid with readOnly field. 
 
Now when we talk about hardcoding, as per my understanding a!forEach() function which was released in 17.2 version, will be the best choice as Josh already have explained above. 
 
Hope this will help you.