Feature Request: Extra features on Editable Grids

RE: Feature Request: Extra features on Editable Grids

Peter Lewis — Wed, 21 Jul 2021 12:35:52 GMT

In posts like this, can you provide more information about your use case for these features? What kind of application do you have? What do your users need to do? How does not having this impact the business? What kind of work around have you implemented?

There are many possible solutions to add sorting / filtering to editable grids, and understanding more about your use case could help us prioritize which solution would be best.

Like others have mentioned above, there may also be tradeoffs with a feature like this that could make it more difficult to validate or edit data, so there may also be current features that could still meet your use case (depending on why you need to be able to sort / filter).

RE: Feature Request: Extra features on Editable Grids

Stefan Helzle — Tue, 20 Jul 2021 18:22:04 GMT

And we would be flooded with Appian based Excel implementations ...

RE: Feature Request: Extra features on Editable Grids

Mike Schmitt — Tue, 20 Jul 2021 18:20:41 GMT

My fear for this approach is that such an implementation would very likely have to sacrifice either flexibility, or design simplicity, or even both of those.

RE: Feature Request: Extra features on Editable Grids

davel001150 — Tue, 20 Jul 2021 18:12:17 GMT

If there were a way to make paging super smart, like auto page to the one with an error, it could be awesome and possibly a differentiator between Appian and other platforms. Solve the inherent nightmare of sorting and filtering, and it could be a game changer.

RE: Feature Request: Extra features on Editable Grids

davel001150 — Tue, 20 Jul 2021 18:10:42 GMT

I suppose similar might be why we can't have paging by default.

Just imagine 1000 cells, that is 10 pages of 10 rows each or 100 entries with 10 columns, not unreasonable. Now, one of them has a validation pop up and needs to be fixed, but which one? We don't want to do that to users.

RE: Feature Request: Extra features on Editable Grids

Mike Schmitt — Tue, 20 Jul 2021 17:22:53 GMT

Agreed with the above, implementing a delete row link is trivially easy using an additional column and a rich text display field.

Filtering and sorting are a trickier issue - the problem is, the inherent capability of the editable grid is based on having an array of data on-form stored in a consistent order. If sorting were implemented it would be super tricky to determine how to keep track of which data in which row(s) has moved where at any given instant. Filtering would be even more complex based on the fact that you might have new or edited, but unsaved, data stored in a row that your filters now prevent you from seeing. These are reasons why sorting and filtering aren't even very often implemented manually on editable grids by even experienced developers - it turns into a complicated mess.

RE: Feature Request: Extra features on Editable Grids

t v s satyanarayana rao — Tue, 20 Jul 2021 16:43:47 GMT

Hi gayathris0003,

Hope this might be helpful

For deleting a row in Editable Grid you can use a!richTextDisplayField()

Example:

a!richTextDisplayField(
labelPosition: "COLLAPSED",
value: {
a!richTextIcon(
icon: "times",
size: "MEDIUM",
linkStyle: "STANDALONE",
link: a!dynamicLink(
saveInto: {
a!save(
/*CDT (local/rule input)*/
remove(
/*CDT (local/rule input)*/
fv!index ()
)
)
}
)
)
}
)