A data owner creates a one-way replica parent-to-child for a single feature class to share...

Scenario Overview:

A one-way replica from parent to child geodatabase is created for a single feature class.

The data owner adds anew attribute fieldin the parent geodatabase, calculates values, and attempts to synchronize the replica.

The new field and its values do not appear in the child replica, even after manually adding the field to the child geodatabase.

Why Recreate the Replica?

The issue arises becauseschema changes(e.g., adding new fields) are not automatically propagated in one-way replication workflows. Synchronization only applies to data changes, not schema updates.

To ensure the schema changes are recognized, thereplica pair must be recreatedwith the updated schema.(ArcGIS Documentation: Geodatabase Replication and Schema Changes)

Steps to Resolve the Issue:

Unregister the Replica:Remove the existing replica pair from both the parent and child geodatabases.

Recreate the Replica:Create a new one-way replica between the parent and child geodatabases. This new replica will include the updated schema.

Synchronize Changes:Perform synchronization to transfer data, including the new field and calculated values, to the child geodatabase.

Alternative Options:

Option A:Enabling replica tracking does not address schema synchronization and would not resolve the issue.

Option B:Running Feature Compare is helpful for analyzing schema differences but does not propagate schema changes.

Thus, the data owner mustunregister the replica pairs, recreate the replica with the updated schema, and synchronize changesto resolve the issue.