If you can't save inline edits, what's the point of having them?
Who said you can't save inline edits with the bottom bar suppressed?
There's two use cases I can think of:
- Perform some sort of auto-save mechanism as I answered in your
Programmatically / Automatically Save Inline Edits on
- Give the end user the flexibility to create their own button to
handle the save themselves if they have specific UI considerations
Since the changes are stored in
draftValues - users can handle that information as they wish outside the bottom bar "save" mechanism when leveraging
let draftValues = this.template.querySelector('lightning-datatable').draftValues;
//pass to server-side apex method to do actual updating.
Since you're going around the standard
save mechanism and implementing your own, you'll also have to explicitly clear out the
draftValues attribute yourself so the table displays as if the standard
save button was processed and you only get the changes that haven't been saved when the user inline edits the next time (or clicks the button).