I'm having to make edits to every record in a record type.
When I click on the first row of data - it takes me to a summary view, and I can now update the information without having to click on the Related Actions first (thank you for that btw)
However once I've edited my record I want to go to the next record in the dataset.
Is there a way I can include a "next / back" function so that I don't have to keep going back to the list view first?
Discussion posts and replies are publicly visible
This is not a OOTB pattern supported in Appian but technically you could put a record link on the Record summary view that points to a next record. You would have to do a query to get the next id. Hopefully, you can match the ordering that you have on your list view.
Here are the docs for the Record Link:
This seems to be some kind of mass-editing scenario. Why not include the editing record actions directly into the list?
I think adding the recordAction in the list will impact the performance. It might not be as performant as it will be without it.
Moving to the next record has only one challenge. How do you know which column has the user sorted on and which way. If yo are able to identify that, then you can just apply the same sorting, query the record and get the next or previous element,
is there a way to do that? - this is thing where you have to go to the summary information rather than just edit in place is highly inefficient. If there is a way to edit data directly in the list other than going to the database directly I would love to know how to enable that.
There are 2 ways you could do this:
1. Either using a master detail view
2. If you don't have a large number of fields, you might be able to use an editable grid.
But how about race condition, Don't we need to handle that in this ?If that is the case, we shoudl consideer that as well
Now we are talking. Appian has no built in way to support real data locking. There are several ways to do it and all of them are discussed here already.