Preventing replication triggering from overactive table columns

When creating or updating records in forms that trigger replication, you might occasionally run into a situation where the system appears to be generating an excessive amount of replication traffic. In cases like this, you can, perhaps, resolve the problem and reduce the amount of replication triggering by designating certain columns in the table as overactive (or "noisy") replication columns.

During runtime, if the only value changed in a given record is in a column that has been designated as "noisy", then no replication is triggered for that record. But any changes that involve both the designated column and any other column (that is not so designated) still triggers replication for both columns.

Note: This procedure affects only non-transactional replication. Transactional replication is not affected.

Open the Application Schema Tables Metadata form.
From the Table Name drop-down list, select the table that has the column of concern.
From the Module drop-down list, select the module to which the table belongs.
In the Skip Replication Noisy Columns field, list the table columns to exclude from replication.
You can designate one or multiple columns for the selected table. To do this, list the column names separated by commas.
Note: If you are not sure of the column names, use the Site Column Name drop-down list to view the column names for the designated table.
Save your changes.

The next time you run the form that uses that table, replication is not triggered if the changes to a given record are only in the listed columns. Replication for that table is triggered only when changes are in unlisted columns.