@KevinHere is a situation. Customer table has customerId and crmId. Customer preferences are stored in a Preferences table with preferenceId and customerId. If we model both Customer and Preference as XDM Individual Profile Schemas, then it becomes a cartesian product of records from both datasets. Records from both datasets are considered as separate profiles even though customerId field is primary identity in Customer schema and secondary identity field in Preference schema. If I define an arr...