@Luca_Lattarini Two very different things:
Class is used to create a Schema and defines the essence and behavior of the Schema
Field Group is then used to extend the Schema (i.e. add more than the b...
Sounds like a data quality issue in your source system that needs to be fixed
If a duplicate _id for an Event is loaded into the same dataset (as part of a subsequent Event), it will be ignored or cause an error.
@Luca_Lattarini A challenge to keep in mind (the speed of which both the Profiles are updated and the segments are updated, they both could be streaming):
Open a few Sample Profiles and spot checkQuery Service to look at Segment Membership in the Profile Snapshot Export xxx dataset (if latency is no...
@Luca_Lattarini Remember that the ID Graph and Profile store are separate. While two identities being sent in an Event marked for Profile should appear in both, I'd check both when troubleshooting.
@Luca_Lattarini @chetanyajain When using the UI to look for Events, remember it caps at some point ...
@Luca_Lattarini Another thing to consider is if a Purchase Order would ever change (e.g. status)? If so, remember:
Events are immutable.It will need to be ingested as a new Event
Any _id strategy will need to accommodate this (e.g. concat(purchaseId + latest updated date) )