I have found the article to be more informative than some of what MS has put out there regarding conflict resolution!
I do have a scenario where I know I need a custom resolver but just don't know how to impliment it. Here is my scenario if anyone is able to help or push me in the right direction please do...
I have one table (TagMstr) with one PK (TagId), several FK's, a rowguid column, and several other columns. A record for TagMstr can already be in the SQL2005 database but not replicated to the end-users filtered set of data yet (because it does not have their UserId associated to it). What happens on the device is a new TagMstr record is written with the same PK as what is in the server database. When I come to do a sync I get a duplicate record error. Although it is doing what it should, I need to make it take the insert performed on the device and perform an update on the server.
For instance in the tables below I need to update the server record with the yellow fields from the device record and remove the rowguid or rewrite the rowguid on the device. Is there already some type of conflict resolver which would do this or what type of resolver would I need?