Is it advised to only have unique records only in a record type lookup schema?
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.