Hi Priyam,
This is working as designed because user 1 in your example did not actually make any changes to the actual profile. He or she just raised a data change request, and when user 2 approved that data change request, the changes were applied to the record. Hence, it shows user 2's ID in the audit logs as "updated by".
------------------------------
Thanks,
Snehil Kamal
Senior Staff Forward Deployed Engineer
Reltio
Bangalore
------------------------------
Original Message:
Sent: 03-16-2026 01:15
From: Priyam Shukla
Subject: Title : DCR request raised by "tester1", DCR approved by "tester2". Records in reltio are reflecting under tester2 521 id.
A Data Change Request (DCR) was raised by user "tester1" and later approved by "tester2". However, the records created/updated in Reltio are reflecting under tester2's user ID (521) instead of the original requester.
Sample Example
- Requester Action
- User tester1 raises a Data Change Request (DCR) to update the Parent of Node 918 from Parent 200 to Parent 371.
- At this stage, the change is only stored as a pending request in the workflow and no actual update is made in the Reltio record.
- Approval Action
- User tester2 (Approver) reviews the request and approves the DCR.
- System Behavior
- Once tester2 approves the request, the system applies the change to the record in Reltio.
- The record is updated in the system at the time of approval.
- Audit Result in Reltio
updatedBy / createdBy → tester2 (User ID 521)- Because tester2's approval action triggered the actual data update in the system.
Summary
- DCR Raised by: tester1
- DCR Approved by: tester2
- Record Updated By in Reltio: tester2 (since approval executes the change)
Please look into this and cofnirm once is this OOTB in Reltio.
------------------------------
Priyam Shukla
EPAM
------------------------------