A matcher can be defined for the entity, for detecting potential duplicates when manually creating records in the hub.
Does it mean : Match rule ( based on non ID fields) will be activated only during Direct Authoring from hub but not through Integration Job load ( get newload> submit load route). Please confirm.
Regards,
Kousik
Best Answer
H
Hitha Kishore
said
over 1 year ago
"A matcher can be defined for the entity, for detecting potential duplicates when manually creating recordsin the hub.
means: For entities where the match rule is based on a business ID (ID-matched entities), Semarchy xDM allows you to define additional matchers (rules based on non-ID fields) to help detect potential duplicates when users are manually creating or editing records via the MDM (the hub UI).
You are correct:
Non-ID-based match rules are only activated during manual authoring in the Hub UI.
During integration job loads, only the business ID is used for matching.
This is by design, to ensure performance and consistency during large-scale data loads.
1 person has this question
1 Comment
H
Hitha Kishore
said
over 1 year ago
Answer
"A matcher can be defined for the entity, for detecting potential duplicates when manually creating recordsin the hub.
means: For entities where the match rule is based on a business ID (ID-matched entities), Semarchy xDM allows you to define additional matchers (rules based on non-ID fields) to help detect potential duplicates when users are manually creating or editing records via the MDM (the hub UI).
You are correct:
Non-ID-based match rules are only activated during manual authoring in the Hub UI.
During integration job loads, only the business ID is used for matching.
This is by design, to ensure performance and consistency during large-scale data loads.
Kousik DAS
Hi,
I can see below statement for ID matched entity in Semarchy documentation:
Entities :: Semarchy xDM Documentation
A matcher can be defined for the entity, for detecting potential duplicates when manually creating records in the hub.
Does it mean : Match rule ( based on non ID fields) will be activated only during Direct Authoring from hub but not through Integration Job load ( get newload> submit load route). Please confirm.
Regards,
Kousik
"A matcher can be defined for the entity, for detecting potential duplicates when manually creating recordsin the hub.
means:
For entities where the match rule is based on a business ID (ID-matched entities), Semarchy xDM allows you to define additional matchers (rules based on non-ID fields) to help detect potential duplicates when users are manually creating or editing records via the MDM (the hub UI).
You are correct:
Non-ID-based match rules are only activated during manual authoring in the Hub UI.
During integration job loads, only the business ID is used for matching.
This is by design, to ensure performance and consistency during large-scale data loads.
1 person has this question
Hitha Kishore
"A matcher can be defined for the entity, for detecting potential duplicates when manually creating recordsin the hub.
means:
For entities where the match rule is based on a business ID (ID-matched entities), Semarchy xDM allows you to define additional matchers (rules based on non-ID fields) to help detect potential duplicates when users are manually creating or editing records via the MDM (the hub UI).
You are correct:
Non-ID-based match rules are only activated during manual authoring in the Hub UI.
During integration job loads, only the business ID is used for matching.
This is by design, to ensure performance and consistency during large-scale data loads.
-
LOV label in Named Query
-
How we can set Dynamically changing Form field Description?
-
Is it possible to have a conditional survivorship rule based on a SemQL filter (akin to the filter on privileges)?
-
Where Do I View 2 Merged Records?
-
Show/hide an attribute in a form
-
Restrict access of attributes
-
Is it possible to manage visible/invisible value in List depend on user role??
-
Why am I unable to merge duplicates?
-
How are child records selected when parent records are manually merged?
-
Can the response from the API Call Response can be formatted differently in the JSON output?
See all 178 topics