Hello community,
I have been playing around with the Data Cloud and have done a few experiments. I found out that - for example - the primary key “Individual Id” is not unique for the important DMO “Individual”.
This confuses me and I'm wondering whether a check for uniqueness is simply missing here, or whether there is an intention or a use case for this.
Especially since I have no possibility to resolve the data records via “Individual Id” in the Identity Resolution and merge them with identical Id and therefore I cannot even bundle these data records in a Unique Profile.
Is it purely up to the Data Cloud Administrator to perform a unique check in advance?
The whole thing seems error-prone or even suspicious to me. I would be pleased to hear your opinion.
Regards,
Thomas
It sounds like you've encountered a perplexing situation with the Data Cloud, Thomas. The lack of uniqueness in the primary key "Individual Id" indeed raises concerns about data integrity and identity resolution. It's essential for the Data Cloud Administrator to ensure data quality by performing unique checks to avoid errors and maintain trust in the system. Your observation highlights the importance of robust data management practices in ensuring reliable data processing and analysis.
