Hi @Karthik Santosh 

To answer your questions one by one:

1. It is best to use the built-in change tracking provided by Wijmo FlexGrid, which is exposed through API_Data\GetChangedLines.

2. The grid includes a built-in configuration for tracking changes called trackChanges. I believe this is enabled by default in the OutSystems Data Grid. Reference: Tracking Changes in CollectionView.

3. Based on my testing, API_Data\GetChangedLines also tracks reverted changes. The dirty indicator reflects this behavior as well.

4. I also tested this scenario using a dropdown column. When the value is changed and then reverted back to its original value, GetChangedLines does not report it as a change.

(!) An important aspect to be aware of is how the grid (including Wijmo FlexGrid) registers changes by default. Changes are only committed once the edited row loses focus (is deselected). As a result, updates are not registered immediately when a value changes, the column’s OnChange event alone does not mark the row as changed by default.

I'll look for a way to register the changes automatically and come to you with a possible solution.

There is a DataGrid feature called GetChangedLines that returns the rows that were modified in your DataGrid. However, there is a problem: if there are fields without values, they are not included in the JSON result.

What I did was create a JavaScript snippet that receives the JSON returned by GetChangedLines and merges it with a default JSON structure. Example:

const defaultStructure = { 
 field1: null,
  field2: null,
  field3: null
};

I assign the GetChangedLines JSON to a variable (for example, const jsonData = ...) and then merge it with this default structure. This way, even if a field is empty, the structure is still filled with null values and keeps a consistent format.

After that, I use JSONDeserialize in OutSystems to convert the JSON into a record list, and then I loop through the list with a For Each to save the data.

Hi @Karthik Santosh 

Save the original data on load and compare it with the current grid data on change to enable or disable the Save button. 

while this may not be the optimal approach, it is a workable solution. Sharing the oml would allow us to review it and potentially offer more refined guidance.

hello @Karthik Santosh hope you find this well, 

This is a pretty common DataGrid behavior, so you’re not alone 🙂 The short answer is that Reactive DataGrid doesn’t automatically “unmark” a row as changed when you revert a value back to its original one.

Best practice is to store a copy of the original data (for example in a Client Variable) when the screen loads. On OnCellValueChange, compare the current row values with the original ones. If all fields match, manually clear the “dirty” state for that row and recalculate whether any row still differs before enabling the Save Changes button.

There’s no built-in way today to detect “net-zero” changes. Even GetChangedLines will still report changes if values were modified and reverted, so custom comparison logic is the reliable approach.

thankyou,