Abhimanyu, it kind of feels like the Project Description attribute should be controlled by RDM. No? In other words, if multiple projects are allowed to leverage the value "R&D Pharma" for their Desc. then I think controlling the attribute values via RDM is something to think about. On the other hand if the Project Description is required to be unique for each Project, then I'm reminded of what @Gino Fortunato was discussing and it gets a bit dicey because as he mentioned, somebody could type a variation of "R&D Pharma" but with the same semantic meaning -- thus there would need to be some authoritative body (might be a person) who would review descriptions as they are created and determine if they are different or semantically the same (leading to a consolidation of the values). And match logic can help automate this review process.
Curt
------------------------------
Curt Pearlman
------------------------------
Original Message:
Sent: 01-12-2024 18:14
From: Abhimanyu Kumar
Subject: Data Validation Alert
Hi Gino
how to achieve the below option that you mentioned.
3) Make the attribute a pivot. Then when the user saves, they can hover over the value to see if there are other entities with the same attribute value
------------------------------
Abhimanyu Kumar
GSK
Cary NC
Original Message:
Sent: 12-19-2023 11:43
From: Gino Fortunato
Subject: Data Validation Alert
That's a bit of a dicey business rule. Suppose they type "Research and Development" instead of "R&D" for example. Or there is a misspelling....
In Relational databases, unique indexes make such requirements very easy. This is one of the VERY few capabilities that Reltio gave up by not using a relational database. Alternatively, you have several options:
1) Create an automatic match rule that merges the two records if the attribute is identical.
2) Create a recipe in Reltio Integration Hub (or other suitable tool) that looks for new project entities and searches for that string in that attribute for the other project entities and if found, does whatever you want: deletes the entity, sends an alert, merges them, etc
3) Make the attribute a pivot. Then when the user saves, they can hover over the value to see if there are other entities with the same attribute value
4) Periodically check the Data quality dashboard for the uniqueness of that attribute.
Original Message:
Sent: 12/19/2023 11:18:00 AM
From: Abhimanyu Kumar
Subject: RE: Data Validation Alert
Sorry for not making it clear in the first place.
Suppose we have an attribute called, "Project Description" in the "Project" entity.
We have one project(profile) already created with the value "R&D Pharma" for the "Project Description" attribute.
so I want to put up an alert that says "Project already exists" in case the curator is feeding the same value("R&D Pharma") while creating a new project using reltio UI.
------------------------------
Abhimanyu Kumar
GSK
Cary NC
Original Message:
Sent: 12-19-2023 11:01
From: Gino Fortunato
Subject: Data Validation Alert
Hi Abhimanyu,
Can you expand on the requirement, please? If the value of what already exists?
------------------------------
Gino Fortunato
Senior Solution Engineer
Reltio
Original Message:
Sent: 12-18-2023 15:55
From: Abhimanyu Kumar
Subject: Data Validation Alert
Hi Team,
I have one requirement to show the alert and should not allow the creation of the profile if the value already exists in any already created profile.
This means, that while creating the profile from UI, validate that attribute with the already/existing created records.
I tried the DVF but I do not see any option to compare it with the existing record.
------------------------------
Abhimanyu Kumar
GSK
Cary NC
------------------------------