The reason for keeping Address and Document as separate child entities is that:
Multiple customers can share the same address.
A single customer can have multiple documents/proofs.
Now, I want to create a match rule on the Customer entity, but the matching logic needs to use:
Attributes from Address (like Address Line 1, City, State)
Fields from Document (like Proof Type, e.g., Driver’s License)
I understand that match rules are typically written within one entity, so I’m trying to understand if it is possible to include columns from both child entities in the match rule for Customer.
If this is achievable, could you please suggest how I can approach this? If not directly possible, are there any recommended workarounds or best practices to handle this scenario?
Monish Kanth
Hi Team,
I’m working on a Semarchy xDM model where I have three entities:
Customer (parent)
Address (child entity)
Document (child entity – contains proofs like Driver’s License, Passport, etc.)
The reason for keeping Address and Document as separate child entities is that:
Multiple customers can share the same address.
A single customer can have multiple documents/proofs.
Now, I want to create a match rule on the Customer entity, but the matching logic needs to use:
Attributes from Address (like Address Line 1, City, State)
Fields from Document (like Proof Type, e.g., Driver’s License)
I understand that match rules are typically written within one entity, so I’m trying to understand if it is possible to include columns from both child entities in the match rule for Customer.
If this is achievable, could you please suggest how I can approach this? If not directly possible, are there any recommended workarounds or best practices to handle this scenario?
Any guidance would be greatly appreciated.
Thanks in advance!
Monish Kanth