Recording history of changes
Wondering if there is a straight forward way for recording a succession of dates that might have changed in a record, much like logged field where instead of recording the modified date, versions of d...
Forum Discussion
The most straight forward way to do this is to have the user record the dates in a child table, and then use a reverse relationship to foot up the most recently changed date up to the Parent record.
A second method is to have a form rule that fires when the record is saved and the date has changed and it will duplicate the date field into a field which will log the history of the changes in a text field set to log changes. That format is more difficult to read, so it's probably best if that method is used only if the date history will be accessed rarely, like for an audit trail. It looks very messy if displayed in the regular form.
The second last way is to set up a Webhook.
Lastly, there are ACTIONs which can record a record when a parent record is saved and certain conditions are true. ACtions become generally available on the next release which I think is this wekeend, April 23.
A second method is to have a form rule that fires when the record is saved and the date has changed and it will duplicate the date field into a field which will log the history of the changes in a text field set to log changes. That format is more difficult to read, so it's probably best if that method is used only if the date history will be accessed rarely, like for an audit trail. It looks very messy if displayed in the regular form.
The second last way is to set up a Webhook.
Lastly, there are ACTIONs which can record a record when a parent record is saved and certain conditions are true. ACtions become generally available on the next release which I think is this wekeend, April 23.