Avoid data loss on unsuccessful synchronization

Hi mobile gurus!

I'm currently developing a mobile solution on MI 7.0 SP14. I have observed that when an unsuccessful synchronization occurs, the persistence layer throws an exception 'The data is inconsistent please reset the data to ensure consistency' when I try to add a new syncbo instance. I understand that this is the default behavior of the MI platform to ensure data consistency, but when a client reset is done, all mi client tables are deleted. As new local data not synced could exist on the client (for example a new invoice in our case), the data will be lost.

Is there any way to keep the good data on a client reset?

Thanks All!

Regards,

Juan José Cruz