Hi,

One of our customers found a possible & serious logical problem that
might result banning the offline -functionalities from users.

When users sync data from offline db to online database the data gets
evaluated and the most fresh data by timestamp wins.

Any data inputted online will use timestamp value from 'on save'
-events 'modified on' -field for possible future evaluation. Problem is
that data typed offline will get the evaluation timestamp from "Synced
On" rather than "Modified On".

Example:
User 1 modified account "XYZ" yesterday in offline -mode. User 2
modified the same field on the same account "XYZ" just an hour ago in
online -mode (So as a matter of data freshness, the data supplied by
User 2 is more valid). User 1 comes now back to office to synchronize
her's/he's offline database. Data by User 1 will win the evaluation
race (because its comparing 'synced on' -event timestamp instead of
'modified on' -events)

If this is so the system considers any data inputted in offline to be
more valuable than data inputted in online, despite the 'modified on'
-stamp. I Hope I got it somehow all wrong but it does not look that
good now. Any thoughts are greatly appreciated!