Duplicated record is considered "modified" by AT function and this is a problem

Topic Labels: Automations
606 1
Showing results for 
Search instead for 
Did you mean: 
4 - Data Explorer
4 - Data Explorer

I have written a script that gets triggered when a record enters a View, and that entrance into the View is supposed to happen just after any field in the record is modified. The script itself creates or deletes records in another table based on the event-speaker combinations in the original record. Well, I find some interesting behavior when I duplicate a test record. Specifically, the duplicate AND the original records both enter the View triggering the script twice. I would like to know why the original record is considered modified according to the LAST_MODIFIED_TIME() function, and if there is anyway to stop this from happening. Thank you.

1 Reply 1

Try comparing a Created Time vs the Modified Time. You may be able to set the view’s filter to not include records where the created time and modified time are the same.