Changeset differences between v5/v6

[H9FFDC]

Hey there

Noticed a difference in behaviour between v5 and v6 and wanted some clarification on if this was the desired / expected behaviour going forward

After modifying a grid cell and changing a value from something to nothing, is it intended that when updating the row with a changeset that does not include that field.
The field that has been modified isn't updated and stays showing as modified / dirty

Previously applying a changeset where the field wasn't included it would be treated as null

See screenshot for example code to replicate in the current version. previously this would have resulted in "team" being not marked as dirty

Cheers H9

[alex.l]

Hi,

What demo is that? Regarding to steps, you cleared "team" field value and didn't see anything in changeset, right?

[alex.l]

I tried with Gantt demos, clear value and I see it in changes, as well as see it applied. But of course it won't be updated if the field is not included. This moment is not clear to me.

[H9FFDC]

Hey there.

This was using the https://bryntum.com/products/grid/examples/celledit/ example

To confirm the scenario so that its a little clearer, We are attempting to "save" a row in the grid, if we modify one of the fields so it is null and then do not include it as a part of the applyChangeset then it remains flagged as dirty.

Previously in Version 5 this would have removed the dirty flag.

• is the new behaviour the intended behaviour and was this previously not working as intended

[tasnim]

Could you please share a video showcasing that behavior?

[H9FFDC]

Hey,

attached is a video showcasing the different behaviour between the two versions

Thanks
H9

[alex.l]

Thank you for the clarification!
I talked to tech team, this is a fix for not intended behaviour that we had in previous versions. So please rely on this logic, we will adhere to a similar behaviour scenario.

[H9FFDC]

Thank you.

Just to clarify, is what is happening in the current version the expected behaviour? So if we apply a changeset, it will only reset the tracking on the fields actually present in the changeset?

If so, is there a recommendation for how we can effectively reset the dirty state for an entire record in the store? Our use case is that we are manually persisting changes to the server, and then applying a changeset based on the data that the server returns after the save. However, not all of the fields are necessarily present e.g. null values are not included in the serialized response. We are not able to commit the entire store, since have implemented a partial save functionality where we allow for only saving some records, or possibly the server might fail the save on certain records.

[alex.l]

Hi,

Just to clarify, is what is happening in the current version the expected behaviour? So if we apply a changeset, it will only reset the tracking on the fields actually present in the changeset?

Correct

If so, is there a recommendation for how we can effectively reset the dirty state for an entire record in the store?

Return full record data set