Make the DataTable Save button label configurable

[cropredy-twa]

Is your feature request related to a problem? Please describe.
Users get confused that when clicking the Save button, that the changes don't flow into the database. Rather, they commit the changes to the local variables in the Flow

Describe the solution you'd like
An option to provide a different label for the Save button

Describe alternatives you've considered
Messaging on the Screen element within the Flow

Additional context
For example, I think "Apply" is a better label than "Save"

[cropredy-twa]

posted to wrong repo.

[cropredy-twa]

I guess this was the right repo

[ericrsmith35]

I have a translatable custom label for anything that can be configured including Cancel and Save where I am able to control the buttons. Unfortunately, the Cancel/Save for Datatable edits is controled by the base component provided by Salesforce and I'm not able to override it. You can hide those buttons however with the Suppress Bottom Bar setting in the CPE.

[cropredy-twa]

@ericrsmith35 - If I hide Cancel/Save

• What is the impact on the various output variables if the Save button is hidden?
• If I progress to a succeeding Screen with a Next button and then do Previous back to the Screen element with the DataTable, are the values entered in the DataTable still as last edited?

[ericrsmith35]

The output variables are not impacted if the Save button is hidden. The OutputEditedRows attribute will be updated each time the user clicks out of en edited field.
The edits will not be retained when clicking the Previous button from the next screen. Yu would have to apply the edits to the input collection variable between the 2 screens.