???synchronize changes??? doesn???t update the values of the target geodatabase,
A replica is built between an ArcSDE geodatabase (SQL Server database) and a file geodatabase with the settings below
[ATTACH=CONFIG]25146[/ATTACH]
Some changes occur on the file geodatabase and then the ???synchronize changes??? applied from the ArcSDE geodatabase to the file geodatabase as shown in the screenshot below:
[ATTACH=CONFIG]25147[/ATTACH]
The issue is that the feature classes of the file geodatabase (which participate in the replica) are not updated according the values of the ArcSDE geodatabase
The takeaway is that for this 1-way parent-to-child replica, the assumption is that the child is read only. If you perform edits on the child, the replication process will not inspect your data on the child to see what has changed, as it is expected to be read-only. If however on the parent, you edit the same data that was 'mistakenly' edited on the child, you should see those child records replaced by the edits from the parent when you perform a synchronize.
The requirement for the child to be a read-only goedatabase is not enforced by replication; the onus is on the user to decide if they want to proceed with editing the child data and risk subsequent data overwrite.
"In one-way, parent-to-child replication, the data in the parent replica is editable, but the data in the child is considered read-only. If edits are performed on the data in the child replica data, the edits are overwritten if they conflict with edits applied during synchronization"
Hope this helps
Cheryl
Many thanks Cheryl for the contribution.
This is the thing that I couldn�??t figure it out myself.
In case edits occur on the child geodatabase then these edits will not be updated when synchronized with the parent geodatabase through one-way replica.
With the comments of Marco, Vince and yours it is quite clear now
