I'm checking whether I may have missed something in my research to answer whether one can implement a custom conflict viewer (e.g. to be used within the application as opposed to going through the SSMS).
I see that there are options for creating custom conflict resolvers either using stored procedures or business logic handlers but neither feel right -- for one thing, the samples I have so far has no interactive components so I'm not sure they were meant to be used interactively, and secondly, it would be a PITA since they can only evaluate a single conflict at a time, not in bulk.
Therefore, I think what I am actually after is using the appropriate system stored procedure to load and view the data in the conflict tables to then show to the users (with some customization & hiding away superficial details). But I am not able to find anything that's a programmatic equivalent to changing the resolution as one would do via the conflict viewer. One could use the default conflict viewer and for certain conflicts, override the original conflict resolution to submit a losing row instead. But what is actually happening in the background when the resolution is overridden? I want to replicate that.
I suppose it might be just simple as re-playing the original transaction but I want to be sure that it is all what happens when one uses the conflict viewer to override the original conflict resolution.
TIA.