How to Move a Organization nodes from One Parent to Another Parent
S
Subramani SIVARATHNAM
started a topic
2 months ago
We have a requirement to move an Organization Node record from One Parent to Another. ie. A >---Node 1 ---> B We have to move to i,e, A >--Node 1 --> C and also (Remove the A >---Node 1 ---> B) We want to know what kind of parameter we have to pass in the UM_Organization_Node table before proceeding. Need an Example for UM_Organization_Node table
Best Answer
A
Alexia SIMOND
said
2 months ago
Hello Subramani,
I'm not sure to fully understand the use case.
Are you talking about organizations relationships?
Meaning that A was linked to B? But there is a "transfer" and now A needs to be linked to C?
When I say "linked" it can be through a simple foreign key (reference) or via an association table.
If so, then this can be achieved through integration, by deleting the previous association and integrating the new one (or the other way around based on the need).
But if those nodes that you are describing are master/golden links, thus meaning that the master A should not be associated to the golden B but to the golden C, then we might need to dig the need to know how to address this.
It might mean that the match rule may need to be reviewed to better suit the matching reality.
Or if it is a one time case, this can be achieved directly through the UI (by merge/split type actions) or "mimicked" via sql.
Please let me know if I can assist further on this topic.
Have a good day.
Alexia
1 Comment
A
Alexia SIMOND
said
2 months ago
Answer
Hello Subramani,
I'm not sure to fully understand the use case.
Are you talking about organizations relationships?
Meaning that A was linked to B? But there is a "transfer" and now A needs to be linked to C?
When I say "linked" it can be through a simple foreign key (reference) or via an association table.
If so, then this can be achieved through integration, by deleting the previous association and integrating the new one (or the other way around based on the need).
But if those nodes that you are describing are master/golden links, thus meaning that the master A should not be associated to the golden B but to the golden C, then we might need to dig the need to know how to address this.
It might mean that the match rule may need to be reviewed to better suit the matching reality.
Or if it is a one time case, this can be achieved directly through the UI (by merge/split type actions) or "mimicked" via sql.
Please let me know if I can assist further on this topic.
Subramani SIVARATHNAM
We have a requirement to move an Organization Node record from One Parent to Another.
ie. A >---Node 1 ---> B
We have to move to
i,e, A >--Node 1 --> C and also (Remove the A >---Node 1 ---> B)
We want to know what kind of parameter we have to pass in the UM_Organization_Node table before proceeding.
Need an Example for UM_Organization_Node table
Hello Subramani,
I'm not sure to fully understand the use case.
Are you talking about organizations relationships?
Meaning that A was linked to B? But there is a "transfer" and now A needs to be linked to C?
When I say "linked" it can be through a simple foreign key (reference) or via an association table.
If so, then this can be achieved through integration, by deleting the previous association and integrating the new one (or the other way around based on the need).
But if those nodes that you are describing are master/golden links, thus meaning that the master A should not be associated to the golden B but to the golden C, then we might need to dig the need to know how to address this.
It might mean that the match rule may need to be reviewed to better suit the matching reality.
Or if it is a one time case, this can be achieved directly through the UI (by merge/split type actions) or "mimicked" via sql.
Please let me know if I can assist further on this topic.
Have a good day.
Alexia
Alexia SIMOND
Hello Subramani,
I'm not sure to fully understand the use case.
Are you talking about organizations relationships?
Meaning that A was linked to B? But there is a "transfer" and now A needs to be linked to C?
When I say "linked" it can be through a simple foreign key (reference) or via an association table.
If so, then this can be achieved through integration, by deleting the previous association and integrating the new one (or the other way around based on the need).
But if those nodes that you are describing are master/golden links, thus meaning that the master A should not be associated to the golden B but to the golden C, then we might need to dig the need to know how to address this.
It might mean that the match rule may need to be reviewed to better suit the matching reality.
Or if it is a one time case, this can be achieved directly through the UI (by merge/split type actions) or "mimicked" via sql.
Please let me know if I can assist further on this topic.
Have a good day.
Alexia
-
Can we reset Matches and run again on match rule change or add a new match rule?
-
"Unmerge" records
-
Turn off match rules to speed up an integration job
-
Can anyone tell me how to load a Fuzzy-Matched entity ... but skip the matching happening auto-magically?
-
Importing CSV in Fuzzy Matched Entity Does Not Trigger Consolidation
-
How can I trigger a "match on child records"?
-
How can I Configure Most Frequent Values in Survivorship Rules?
-
Deterministic or probabilistic matching
-
Machine Learning and AI for matching
-
Prevent loads from replacing values overridden by users
See all 55 topics