I think you'll need to make an AutoEnter Timestamp field (on Modification) in the table of related records, then you can display it, if needed, in the portal. That will make a TimeStamp for any modification of that record. If you only need it for the modification of a particular field then you'll likely need an elaborate Case ( ) statement so that the AutoEnter is only triggered for that field.
I haven't tested this but it should work.
The issue with this is the timestamp will trigger when the other items are modified... Just want want to track the modifications on one field...
Then use three triggers on the related field that you need to monitor.
1. On Object Enter to Get (ActiveFieldContents) to set a Global Var say $$original.
2. On Object Save to set another Global Var, say $$Changed, to 1 when the contents of the field have changed.
3. On Object Exit is a longer script which will test for $$Changed = 1 and then set the TimeStamp. If the $$Changed is ≠ 1, then $$Original is put back into the field and no TimeStamp is set.
Numbers 1 and 2 are single line scripts. Other developers may well have a simpler process.
1 of 1 people found this helpful
Auto enter calculation with replace existing value option
Evaluate ( "Get(CurrentTimestamp)" ; fieldForTrigger )
You need script if you want to set timestamp on front-end when back-end changes, but you don't.
Thank you John and user1952....going to try your feedback and repot back.... !!!
User19752 thank you....just finish testing the evaluate function and it work great !!! no need for triggers or scripts....thank you so much !!!