Forum Discussion
Laura_Thacker
7 years agoQrew Commander
Joey - I would build a child table to capture the history of changes. Trigger notifications each time a new date is created by the automation/webhook/qb action; pointing back to the parent-record. This way you get a true-history of the changes as well.
Snapshots only work on lookup fields; and only when a record is created.
Snapshots only work on lookup fields; and only when a record is created.
- ZintJoseph7 years agoQrew CaptainThanks Laura....I have started down that path but went down the path of first creating a record for a when a project is created and then change that record. I have a max/min set of fields looking at the related date changes....I will revamp this as the first step is to create a project with a blank date so maybe I take that out and just have it create the record when the date is populated/repopulated each time.
- Laura_Thacker7 years agoQrew CommanderIf you create a new one each time; the trigger will be more effective on the email and you get the benefit of the history in an easy to see embedded report; rather than a text-append type of visual.