---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Discrete replication

# Discrete replication {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Distinguish consumers in Instance Data Replication (IDR) using discrete mapping in a producer replication set.

Every producer replication set has a unique relationship with each consumer subscription. One
way of distinguishing this relationship is by mapping discrete field values for producer
replication sets.

Once you enable discrete mapping, you can define for each outbound entry of a replication set a
discrete value field. An administrator of the producer replication set can define the mapping of
each consumer subscription by the setting this discrete value.

For example, you might have an ACME corporation as the producer instance, and have consumer
subscribers of ACME US and ACME Europe. You could set a discrete value of
region on the outbound replication entries for the incident table. While
both of these entries reference the same company table, a rule set for the discrete value can
display US for ACME US, and Europe for ACME Europe.  
If you have bi-direction enabled with discrete mappings, different consumer subscriptions:

* Should never receive records sent from other consumer subscribers
* Should never receive records from a producer intended for other consumers subscribers
{#discrete-producer-replication-sets__ul_amx_4n4_qlb}

With bidirectional replication, records created on a consumer instance are replicated to the
producer instance and vice versa. When the consumer replicates a record to the producer, the
consumer's discrete field value that you defined in the producer replication set overrides the
discrete field value in the consumer record if it's different. For example, say you define a
discrete mapping using separate regions for each consumer instance as follows:
{#discrete-producer-replication-sets__table_dpv_kcy_dwb__entry__2}

| Consumer instance | Region |
|-|-|
| Consumer instance A | Asia |
| Consumer instance B | Europe |
| Consumer instance C | USA |
[Tabelle : 1. Discrete mapping using the Region field]

{#discrete-producer-replication-sets__table_dpv_kcy_dwb}

When a record is manually added to consumer instance B with the Region field set to Asia,
bi-directional replication sends the record from the consumer to the producer to be inserted, but
the region field is overwritten and the value is changed to Europe. The discrete value that is
defined in the producer replication set is used instead.

For details on the implications with discrete mappings and data transfer between instances, see
[data privacy in IDR](https://servicenow-prod.fluidtopics.net/iB5soFtcwLrub_0IqJvtBw "The ability of replication sets to host multiple remote consumers in Instance Data Replication (IDR) means that there are potential data privacy issues to consider.").