Forum Discussion
BrianSeymour
2 years agoQrew Assistant Captain
Hey Amy, I'm not sure if this is applicable to your use case, but there have been times where we've created an "Activities" child table to help track history. For example, when a given field changes on the parent, trigger a Pipeline to its copy values to the child table. This would include the date/time and User who made these changes. This sets up more straightforward reporting, such as summarizing (counting) the number of changes.
And you could leverage a "reverse relationship" to pull the most recent changes to the parent record, such who made the last change and when.
------------------------------
Brian Seymour
------------------------------