This issue is a follow-up of the fix/improvement done in the scope of MGNLUI-3633. The situation is far from ideal - even though the underlying datasource does not get overridden as a consequence of the fields not being in synch with the model, the fields still don't get updated if the underlying data changes.

Vaadin's ValueChangeEvents should be sent in appropriate situations and fields, especially MultiFields must react on such changes and update their state/UI.

For the future assignee:
One should delete the workarounds (markAsDirty() calls) which were introduced with MGNLUI-3844.
If this ticket solves the root problem, those shouldn't be needed anymore.