Save multiple changes to a record at once

Options
Iain Ashley
Iain Ashley Member Posts: 9
5 Likes First Anniversary Name Dropper First Comment

If a user needs to make multiple updates to a record, they currently have to hit the save button after each change or lose the other changes. This is annoying and anti-intuitive. A secondary problem with this is that after every save, a "Record Changed" webhook will trigger, causing subsequent api floods with essentially out of date payloads. Why can't there be a single save button so that all changes can be made and then saved?

In the above example, if a user needs to make 3 changes and add a note, if they save one of the items, the page refreshes and the other changes are lost. In addition, 4 payloads will be sent in quick succession, with only the last one being the complete/accurate record. This means that effectively every payload needs to be processed as such as there is no way to pre-emptively discard invalid hooks.


Thanks

2
2 votes

Active · Last Updated