Currently there is no way to determine in real time when replication/save conflicts occur. I would like to have the following:
1) An event that gets triggered at the database level so we can resolve these in real time.
2) Some way to determine which fields triggered the conflict.
3) Replication/save conflict rules that could automatically fix the problem rather than having to write code. This would allow application owners to manage how this is handled.
This isn't particularly difficult to write myself, but for a product that has had replication since 1985 you'd think there would be better built-in tools to handle it.