Hi All,
I have a few observations regarding the source_id column in matching step of an entity in a MDM project.
For context, source_id is a column with unique values (Primary Key in most cases) that we define to uniquely identify each record in a source system, connected to mdm hub.
I was recently trying to test the match logic on OneDesktop using plan files. I used a very small subset of records from each source.
Load Component
In the project, source_id column(defined in load component) for one of these source system is “SOURCE_SYSTEM_NAME~^~pk_id”
where SOURCE_SYSTEM_NAME is as string value and pk_id is the primary key.
match component
When we defined a match component in mdm project, we do not define standalone bindings but assumably “Id Column” would be mapped to source_id column if we are testing on OneDesktop as a plan.
So, when I created a plan to test the match logic, I mapped “Id Column” to source_id (with source_id having string values as mentioned above). But when I run the plan with this Matching step, I get IllegalNumberFormat Error, because the source_id has string value.
It looks like this happend because the matching step converts the Id Column value to integer/long. However, we do not encounter this issue when mdm-hub takes care of match component without standalone bindings.
Can someone give their insights into why this happens? Is mdm engine handling this?
adding References to
