Tool for Conversion of Local Data to Replicated Data
In a replication process, the source system (the data owner) sends data to the target system (which receives and stores the replicated data).
In certain scenarios, the data in the target system is intended to mirror the data in the source system. To facilitate this requirement, particularly in cases where selective replication is necessary, replication lock is introduced to govern which data elements within the target system are eligible to participate in the replication process.
The replication lock serves this purpose by enabling designated data in the target system to be explicitly marked for replication. This mechanism ensures the preservation of data integrity throughout the replication operation.
The table below illustrates how replication behaves under different conditions—when the replication lock is applied, partially applied, or not applied at all.
|
Source System
|
Target System (Before Replication)
|
Locked for Replication
|
Target System (After Replication)
|
Replication Behavior
|
|---|---|---|---|---|
|
PartP1 A1
|
PartP1 A.1 (local)
|
PartP1
|
PartP1 A.1 (replicated)
|
Only PartP1 A.1 is replicated. Links between parent and child parts (L3 and L4) are removed from the target system.
|
|
ChildC1 A.1
|
ChildC1 A.1 (local)
|
ChildC1 A.1 (local)
|
||
|
ChildC2 A.1
|
ChildC2 A.1 (local)
|
ChildC2 A.1 (local)
|
||
|
PartP1 A.1
|
PartP1 A.1 (local)
|
PartP1, ChildC1, ChildC2
|
PartP1 A.1 (replicated)
|
All parts are replicated. Links L3 and L4 are removed, and links L1 and L2 are successfully replicated.
|
|
ChildC1 A.1
|
ChildC1 A.1 (local)
|
ChildC1 A.1(replicated)
|
||
|
ChildC2 A.1
|
ChildC2 A.1 (local)
|
ChildC2 A.1 (replicated)
|
||
|
PartP1 A.1
|
PartP1 A.1 (local)
|
Not applied
|
PartP1 A.1 (local)
|
A non-overridable exception occurs. None of the parts are overwritten.
|
|
ChildC1 A.1
|
ChildC1 A.1 (local)
|
ChildC1 A.1(local)
|
||
|
ChildC2 A.1
|
ChildC2 A.1 (local)
|
ChildC2 A.1 (local)
|
||
|
PartP3 A.1
|
Not applicable
|
PartP3 A.1 (replicated)
|
PartP3 A.1 is newly created in the target system.
|
Important Replication Rules
• Strong-side links are removed during replication
• Weak-side links are retained during replication
For more information, see Replication Behavior When Locking Strong-side and Weak-side Links.
 |
• Replication locks cannot be applied to — Managed baselines, electrical parts, and objects that are not supported for replication.
• Even with a replication lock and no version mismatch, some objects may still be ineligible for overwriting to preserve data integrity.
For example, if a family table contains four CAD parts but only three are eligible for replication, none of the parts are replicated when the lock is applied.
|