3587012 - Configuring National ID Allowlist for Multi-record Relationship

This article describes different configurations and behaviours of the feature "National ID Allowlist for Multi-record Relationship" which is universally enabled post 1H 2025 release. This feature allows to maintain National ID cards with validity periods.

Q: Is it mandatory to configure Allowlist Configuration Details for National ID with Validity Period in Manage Data for each country's national ID card type?
A: No, it's not mandatory. You should configure it if you want to maintain validity periods for national IDs. Also, this feature allows you to have multiple national ID records under one card type or across multiple card types.

Q: Is it possible to disable this feature?
A: This feature is universally available to all customers post 1H 2025 release and it cannot be disabled. If no allowlist configuration is done for a specific national ID card type, multiple records related to this card type will not be allowed and validity periods cannot be maintained.

Q: What are some use cases where national ID with validity period may be needed?
A: In the case of changes in gender or other country/region-specific identification information, you need to renew your National ID number. Then, you can configure an allowlist to update multiple national ID records under one national ID card type. There should be no gaps or overlaps in the validity periods of these multiple national ID records.

In some countries/regions, you can have multiple national ID card types whose validity periods must follow a specific sequence based on the legal requirements. In this case, you can configure an allowlist to update sequential national ID records across different national ID card types. There should be no gaps or overlaps in the validity periods of these multiple national ID records.

Q: What are different Multi-Record Relationship?
A: There are 2 Multi-Record Relationship. They are:

• Multiple Records under One Card Type: This option allows you to select only one card type for the selected country. You can have multiple entries of this card type with validity periods that do not overlap or do not have gaps in between them. For example, you select this option for United State's national ID Social Security Number (SSN). For a user you can have 2 entries: first SSN with Valid From 01.January.2010 and Valid To 31.December.2010 AND second SSN with Valid From 01.January.2011 and Valid To 31.December.9999. The second SSN cannot start after 01.January.2011 (for example,  02.January.2011) as date gap between entries is not allowed. Also, since overlap is not allowed, second SSN cannot start before  01.January.2011 for example  30.December.2010. 
• Sequential Records across Card Types: This option allows you to select maximum 3 card types for the selected country. You can have one entry of each card type for the country for a user. For example, you select this option for India's national ID Aadhar ID as National ID Card Type (First) and Permanent Account Number as National ID Card Type (Second). For a user you can have 2 entries: Aadhar ID with Valid From 01.January.2010 and Valid To 31.December.2010 AND Permanent Account Number with Valid From 01.January.2011 and Valid To 31.December.9999. The second national ID card type's start date cannot be before the first national ID card type's start date as it's defined as the second national ID card type in allowlist configuration. Also, there cannot be any gap or overlap between these 2 entries. 

Q: Is it allowed to configure both Multiple Records under One Card Type and Sequential Records across Card Types for the same country?
A: No. You can configure only one Multi-Record Relationship for a country. There is a system validation in place for preventing the configuration in question. 

Q: Is it mandatory to enter all the configured national ID card type values for a user when the country's allowlist is configured with option Sequential Records across Card Types?
A: No. It's not necessary to enter values for all configured card types of the country. You should be able to save national ID card value with one/multiple card type(s).

Q: Are Valid From and Valid To values are mandatory when allowlist is configured?
A: Yes. There is a validation that ensures that both Valid From and Valid To values are entered for each national ID card entry when allowlist is configured. 

Q: Is it possible to have different Is Primary value for multiple entries of a country's same/different national ID card(s)?
A: For both sequential and multiple records allowlist configuration, the Is Primary value of the entered sequential or multiple records must be same. However, there must be at least one entry (need not be for the same country) with Is Primary value set to Yes. 

Q: Where can I find different validation message details for National ID with Validity Period feature?
A: You can find details here: Troubleshooting for National ID with Validity Period

Implementing National ID with Validity Period

New National ID Information with Validity Period - General Availability

2093378 - National ID validation issues - Employee Central

2668688 - National ID Card: How to create custom Regular Expression and Display Format

b2505, ECT-242645, NID, multiple, sequential, multi-record, validation, FAQ, validate, ECT-176715 , KBA , LOD-SF-EC-PER-NAT , National ID - Config, Rules, RBP, UI , LOD-SF-EC-PER , Person Data (All Person Data Types) , LOD-SF-EC-BCI , Manage Business Configuration (BCUI) & Data Models (XML) , How To