Is it advised to only have unique records only in a record type lookup schema?

[SahuSa1]

Hi,

For a Record type custom class lookup schema, will there be any issue if the Primary key field has multiple entries? Is it advised to only have unique records only in a record type lookup schema?

For Example- 

custom class - Product

Key Field - Product code

and for one product code, there will be one or more products.

Product code - P1 will have 3 products under it, i.e., P1 code will have 3 rows of data in a single batch load. 

[kautuk_sahni]

@Rite18 @AtulChavan @ccg1706 @_Manoj_Kumar_ @akshaykapil23 @Sneha-Parmar @ChetanyaJain Request you to please look at this question and share your thoughts.

[_Manoj_Kumar_]

Hello @SahuSa1 If the key is Product Code, then you can't have more than 1 records with the same PK.

Also, Can you please share details on the use case?

[SahuSa1]

Hi @_Manoj_Kumar_ , Thanks for your reply. 

For the use case, there were more than one product code which were mapped to a product group. So a certain product code could have more than one product group mapped to it. In that case, I was not sure how the mapping would happen to a profile. Incase of conflict which product group a particular profile would consider and this would have probably affected segment result.

For that reason, we removed duplicates from source and now only distinct records are being ingested to the lookup schema. 

[akshaykapil23 · Accepted solution]

Hey @SahuSa1 

It is advisable to have unique records.

You can retrieve the corresponding schema definition for a data record from a schema registry or database.

This process is essential for understanding the structure and data types of the record, enabling you to interpret and utilize the data effectively.

[SahuSa1]

Thanks @akshaykapil23 , for your reply. Now my understanding is clear