Hello Monish,
You are facing a known limitation tracked under MDM-8925, planned long-term.
If you let me know the customer who needs this feature, I'll add it there.
I'll convert this topic in a ticket, for me to link the internal request there, for you to be able to follow-up its R&D status.
You might need to reach out to the consulting team to find another way to address your needs.
Talk to you over on ticket.
Have a good day
Alexia
Hello, I think Im asking same type of question (https://support.semarchy.com/support/tickets/62397)
Can u tell me, please, if you have got any solution about your issue ?
Do you have to create a new element in ur database as a view or any else ?
Take good care of yourself.
Hello Frédéric,
Yes indeed, it sounds to be the same need.
An agent has taken your ticket into account and is providing you the elements there.
Have a good day.
Alexia
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
2 people have this question