Original Message:
Sent: 05-13-2025 01:22
From: Chetan P
Subject: Data Validation Function | Before and After Save
Hi Radhakrishnan,
I agree to the point that reltioLoadDate reflects actual load timestamp. And also i have noticed another case (issue) - Since we are considering DVF at Entity level, reltioLoadDate focuses only on Crosswalk level - So when multiple crosswalks are available - then confusion may arrise.
So, to avoid that we have considered "Updatetime". But it is still not satsifying requirement. And apologies for confusion on "Publish Date" it is just another timestamp column where external source populates. Please treat the column as another Timestamp column and not Reltio's system values.
I have added Validation function as - lte(attributes.Publish_date.value, 'updatedTime.value') \\ Not Working
Looking for a way to - Use UpdatedTime of the entity to compare against Publish_date(Simple attribute and user defined value)
Any help on this?
Thanks,
------------------------------
Chetan P
Tech Mahindra
------------------------------
Original Message:
Sent: 05-12-2025 13:31
From: Radhakrishnan Ramalingam
Subject: Data Validation Function | Before and After Save
Chetan,
The Publish Date is already available in the Crosswalk as sourcePublishDate or crosswalk's updateDate, which can be used to store the actual update date from the source system.
That said, if you map the source system's lastUpateDate to Reltio's sourcePublishDate, keep in mind that Reltio's load Date always reflects the actual load timestamp. Therefore, this requirement becomes theoretically invalid when loading from a legitimate source system into Reltio, since source systems typically maintain proper audit fields like lastUpdateDate. Issues generally arise only when data is manually entered (e.g., via Excel), which increases the risk of errors
Please reach out to me if you have more questions
------------------------------
Radhakrishnan Ramalingam
Majix Solutions
San Ramon, CA
https://majixsolutions.com