Dirty Fields and useFieldsArray

[Daneng66]

Is it a known behaviour that changing the indexes of records in a field array (e.g. via append or delete) will report fields as dirty even though the data behind the record hasn't changed?

[Moshyfawn]

I believe so, yeah. By manipulating array fields you're updating the array field value (adding / removing / moving elements inside the array). Only the newly appended / removed value is marked as dirty. See this CSB
#6448 discussion might be related, check it out

[Daneng66]

That's fine I won't create a bug then, it just means that I have to sanitise the dirty fields information and check equality before creating my patch requests to the server.

[Daneng66]

BTW really appreciate how quickly you guys reply 🙌

[Moshyfawn]

You can also try reset your form with the current values after manipulating the array (append / remove etc); it will set all fields to unmodified (isDirty: false)

[Daneng66]

You can also try reset your form with the current values after manipulating the array (append / remove etc); it will set all fields to unmodified (isDirty: false)

I don't rely on isDirty, I only look at the content of dirtyFields to determine if I can submit and what data has changed

[Moshyfawn]

reset resets dirtyFields form state as well. See this CSB.

1. Append a new field
2. See at the bottom of the form "Dirty Fields" is empty, "Values" has a new field value added