Improve auto-sync behavior when editing parent and child features

[joonaris]

Description:
When automatic synchronization is enabled, the app starts syncing as soon as I open a layer form and add features

It seems that the current logic triggers synchronization immediately after it detects any edits, even if the parent feature is still being edited and the child feature is not yet fully saved.

This can be a bit distracting and also feels premature. A better approach would be:

Only trigger synchronization after the parent feature has been saved, not already when a child feature is being added to it.

Use case:
When I add features to a layer with a 1-N relation, auto-sync pushes changes while I am still saving the child feature’s data.
This interrupts the workflow and feels unexpected.

Expected behavior:
Sync should only start after completing the parent save action.

auto_sync.mp4

[MF-Aichinger]

So, synchronization only occurs when the parent object is closed, correct? That would be absolutely brilliant. We are currently testing the first manhole inspection including a 1:n relationship, and when I enter something in the child element, “Sync successful” appears, and then again in the parent element. That's a lot. It would be perfect if it were simply done when confirming/closing the parent element.

[Withalion]

Yes that is true. However the sync might be triggered even while you are filling out the form as the previous work introduced 1 minute threshold for autosync.

[MF-Aichinger]

Would it be technically possible, and of course without too much effort, to prevent Autosync from running while the form is open? I'm not sure if I'm thinking this through correctly, but you'll have to think about it yourselves.

[Withalion]

I just want update you also here. We made some modifications to the logic and the autosync will be now "blocked" while feature forms are open and will "resume" when all forms are closed.