Avoiding Common Replication Index Errors

Many common replication index errors occur when you reuse or swap corporate data records—such as profiles, products, recipes, shipping types, or currencies—and replicate them to ship databases that already have those values assigned to different records. Direct updates to existing identifiers create duplicate key collisions during replication file ingestion.

Best practices to avoid replication index errors

You can keep data consistent across your fleet by following key update guidelines.

• Do not directly reuse or swap names, numbers, or codes for any data type previously replicated to ships in the fleet
• Execute data identifier modifications using a staged two-step procedure

How to execute a staged data update in Corporate EMW

When a name, number, or code change is required for an existing data record, use a staged update procedure to avoid duplicate key collisions.

1. Append a temporary identifier. In Corporate EMW, add a temporary unique identifier such as xx, zz, or _TEMP to the field you are editing to make the record unique
2. Generate and process initial replication files. Create outbound CORP replication files and process them into all ship databases across the fleet
3. Apply the final field changes. Once the files process successfully on every ship, rename the field in Corporate EMW to your desired final name, number, or code while removing the temporary suffix
4. Distribute the final replication files. Create a second set of CORP replication files and process them across all ship databases to finalize your changes

Warning: Modifying existing data identifiers directly without temporary suffixes causes duplicate key collisions on ship databases and disrupts fleet data synchronization.