After editing a cell, the grid normally inserts the new value into your data using the column definition field
attribute. This covers the most common case, where the grid owns the data state and treats the data as mutable.
This page discusses alternatives to this approach.
Value Setters provides an alternative to using field
for setting the data. Use valueSetter
if you want the grid to manage the data (ie update the data inline) but you want to update in a way other than using field
. This is useful if you are not using field
, or somehow need to manipulate the data in another way (e.g. the data item isn't a simple key / value pair map, but contains a more complex structure).
Read Only Edit stops the grid from updating data, and relies on the application to make the update after the edit is complete. Use this if you want to manage the grid data state externally, such as in a Redux store.
Value Setter
A Value Setter is the inverse of a Value Getter. Where the value getter allows getting values from your data using a function rather than a field, the value setter allows you to set values into your data using a function rather than specifying a field.
const [columnDefs, setColumnDefs] = useState([
// Option 1: using field for getting and setting the value
{ field: 'name' },
// Options 2: using valueGetter and valueSetter - value getter used to get data
{
valueGetter: params => {
return params.data.name;
},
valueSetter: params => {
params.data.name = params.newValue;
return true;
}
}
]);
<AgGridReact columnDefs={columnDefs} />
A value setter should return true
if the value was updated successfully and false
if the value was not updated (including if the value was not changed). When you return true
, the grid knows it must refresh the cell.
Function or expression. Custom function to modify your data based off the new value for saving. Return true if the data changed. |
The example below demonstrates value setters working alongside value getters (value setters are typically only used alongside value getters). Note the following:
All columns are editable. After an edit, the example prints the updated row data to the console to show the impact of the edit.
Column Name uses
valueGetter
to combine the values from the two attributesfirstName
andlastName
(separated by a space) andvalueSetter
is used to break the value up into the two same attributes.Column A uses
field
for both getting and setting the value. This is the simple case for comparison.Column B uses
valueGetter
andvalueSetter
instead of field for getting and setting the value.Column C.X and C.Y use
valueGetter
to get the value from an embedded object. They then usevalueSetter
to set the value into the embedded object while also making sure the correct structure exists (this structure creation would not happen if using field).
Read Only Edit
Read Only Edit is a mode in the grid whereby Cell Editing will not update the data inside the grid. Instead the grid fires cellEditRequest
events allowing the application to process the update request. To enable this mode, set the grid property readOnlyEdit=true
.
Value has changed after editing. Only fires when readOnlyEdit=true . |
const readOnlyEdit = true;
const onCellEditRequest = event => {
console.log('Cell Editing updated a cell, but the grid did nothing!');
// the application should update the data somehow
};
<AgGridReact readOnlyEdit={readOnlyEdit} onCellEditRequest={onCellEditRequest}></AgGridReact>
The example below has Cell Editing enabled, however the editing does nothing because readOnlyEdit=true
is set. The application listens for cellEditRequest
event and prints to the console. As the application does not try to update the data, the cell keeps its old value, giving the impression that editing is not working.
This next example extends the above by getting the application to update the data.
- The application listens for
cellEditRequest
and updates the Row Data. - The Row Data has IDs and
getRowId
is implemented. This allows the grid to only refresh the desired row after new Row Data is set.
This final example is similar to before, except it uses Transactions to update the data after the edit rather than updating the whole Row Data.