I've got the following scenario: SyncProvider A operates on a table with a certain primary key column. SyncProvider B operates on another table where the primary key column is other than the Provider A's PK column. With other words, both tables' PK columns
don't match.
Provider B's table has got another column (no key column) that can have values of the same type and range as Provider A's PK column. But this column in Provider B's table has no unique constraint, meaning that values in that column can appear more than once.
With other words, between Provider A's table and Provider B's table there is a 1:n relation. That means that during synchronization, updating a record in Provider A's table should lead to updating all the corresponding records in Provider B's table.
Apparently, Sync Framework doesn't support this one-to-many synchronization, but nevertheless I'm searching a solution for this problem. Do you have any idea for solving this problem?
P.S.: I know that both providers' tables should have the same primary key columns, but in my case this is impossible to reach.
