Hi,
This is the expected behavior to prevent a cloned profile from getting merged with the original profile that it is cloned from. Usually cloning is used to create a new profile that shares a set of common values with an existing profile, but will be a different in certain key aspects.
Can you explain your scenario? Why do you want the cloned profile to merge with the original profile?
------------------------------
Venki Subramanian
Reltio
------------------------------
Original Message:
Sent: 10-28-2024 02:54
From: Utsa Das
Subject: Automatics matches for Cloned profile
Hi team,
We have enabled the clone option at entity level from UI and we created a potential match rule .Any duplicate records created separately from UI or API , the match rule are considering them as potential matched.
But when we are creating same records by Clone option ,they are not matching and we have checked this is actually taking them not matches and somehow it seems Reltio is expecting them to match manually.
Is it the expected behaviour for Clone option? If yes please let us know how to enable automatic a matches when duplicate records are being created by Clone option?
------------------------------
Utsa Das
Novartis
------------------------------