Best Schema Design for Shared Identity across Multiple ExperienceEvent Schemas

[JoeSa1]

Hello, 

I have a question about ExperienceEvent Schema design regarding how to handle one unique identity across 1 XDM Profile Schema and 2 XDM ExperienceEvent Schemas. 

Let's say that the unique identity of the XDM Profile Schema is labeled "COMPANY_UNIQUE_IDENTIFIER". 

Can I use "COMPANY_UNIQUE_IDENTIFIER" in 2 separate ExperienceEvent Schemas, that both use "COMPANY_UNIQUE_IDENTIFIER" as a primary key, or would this mess up Profiles? 

Thank you all in advance!

[_Manoj_Kumar_ · Accepted solution]

Hello @JoeSa1 

Yes, You can use the same key across schemas

if you mark this identified as a primary identity in schemas then all the profiles with similar attribute values will be linked via this identifier.

If you don't want this to happen then you can just define it as an attribute and use its foreign key to link with a lookup table.