Queued updating subscriptions
With transactional replication, replicated data should be treated as read-only; however, you can modify replicated data at a Microsoft SQL Server Subscriber by using updatable subscriptions.If you need to modify data at the Subscriber, choose one of the following options depending on your requirements.Transactional replication enables changes made at a Subscriber to be propagated back to the Publisher using either immediate or queued updating subscriptions.
A transaction in a queue maintains the old and new row version values.Replicate Subscriber changes Select the check box in the Replicate column for each Subscriber that should be able to make updates.Note This feature remains supported in versions of SQL Server from 2012 through 2016.The new GUID in the publication indicates that two different row versions exist: one in the transaction being submitted by the Subscriber and a newer one that exists on the Publisher.In this case, another Subscriber or the Publisher updated the same row in the publication before this Subscriber transaction was synchronized.
Search for queued updating subscriptions:
The following conflicts can occur: When creating a publication and enabling queued updating, replication adds a uniqueidentifier column (msrepl_tran_version) with the default of newid() to the underlying table.