Retain Site
To replicate _all table data for an insert to a site in a different database, select this field. (You would never replicate _all table data to a site in the same database.)
To replicate data for most master tables that do not end in _all, clear this field, even if inserting to a site in another database. There are some exceptions for tables in the ExtFin replication category (custaddr_mst, customer_mst, vendaddr_mst, and vendor_mst), which always replicate to an external application.
This field is enabled only for Table object types.
If this field is cleared for a table, then replication triggers change the site_ref column of the target site record to the target site value and set the RowPointer column value as a new GUID. RowPointer must be unique in a table. If you copy a record from one site to another site in the same database, a new RowPointer GUID is required. When you clear this field, the replication is considered a new record for the target site, as opposed to a copy of the record from the source site.
- If you try to replicate a table where RowPointer is part of the primary key, and you clear the Retain Site field, inserts would occur with a different RowPointer to the other site, so updates would never find that record. No failure would occur, but replication updates to the other site would simply not occur.
- Replicating a table which has an identity column in the primary key should not be attempted between Mongoose sites. Since the identity column changes with every table insert, this means that data inserted in site A and copied to site B would no longer have a matching primary key. This would lead to incorrect updates and deletions later on.