The path component identifies the linkage from one table to another so columns from multiple tables can be used in the same match rule set.
I don't understand the use case for wanting to match to the xref records. Those values are all represented in the consolidated base object.
Thank you for your response.
I believe the consolidated base object has cell records either with the highest trust score or the one with most recent source update(SRC_LUD). In our case, there are certain new records that would not match with the consolidated BO data but could still match with the XREF data that did not survive the merge process. I see that Path Component can be used as a source table(XREF in my case) and I'm not sure if I could match BO data against it.
This is likely against best practice. If a value is important enough to be matched on, it should survive the match and merge process. You're not matching XREF data against BO data, you're matching XREF data against other XREF data. However, in a very simple case it appears the answer to your question is yes.
- Record A with 2 XREFs, the First Name values are "Bob" and "Sally", "Bob" is the surviving value, and consolidation_ind = 1
- Record B with 1 XREF, the First Name value "Sally", consolidation_ind = 4
- Match path from C_PARTY to C_PARTY_XREF
- Exact Match Column on C_PARTY_XREF|First Name
- Exact Match Rule consisting of only that column
- Record A will match with Record B.
You should consider the effects of this as now every new XREF will be compared to every existing XREF. This could create false matches and possibly affect performance.
Okay, thank you