I worked around – see LastHumanModifcation field – the fact that my automation itself updates the modification date of the items but now my problem is that whenever we change the structure of the Database of these items, their modification date gets modified and thus identified as “active” items…
Is it a design choice to update the “Modification Date” of each entity or just a “side effect”?
Could you elaborate what you mean by change the structure of the Database?
If I understand correctly, you have created a field “Last human modification”. If you set up your automation such that it updates this date field whenever fields of your choice get updated, the hard programmed modification date should be irrelevant.
I have a very simple, similar automation which updates the “Updated” date field to today, whenever a status info is updated.
This did not seem to be a specific Feature Request so I’ve moved it to “Get Help”. If it evolves into a more clear needed new feature (or bug), it can be moved again. Apologies if I’ve misinterpreted, I am happy to move it back right now if you’d like.
As I want to capture any changes on fields and links – like new commits, PRs, etc… – I figured it would be easier to base my logic on the Modification Date
But you approach could be better than the ugly hack I’m putting in place – I would need 3 automations to make it work but at least I would have full control.
Thanks for your help!
There’s still the update of “Modification Date” when adding or removing fields but not really sure it’s an issue.
I guess so yes, that’s why I hide that field and use an extra field. Just add all triggers you want to update your field and you should be good to go
Working with the modification date for this use makes it unnecessarily complicated.
Unfortunately it is not possible to combine linking, unlinking, and updating automations, so you would definitely need quite a few automations (and yes, one per relation ).
Also, there is no way to directly monitor ‘rich-text field’ updating I’m afraid (you could make an ugly workaround that checks for changes on a schedule, but it’s not easy/pleasant).
There used to be a ‘modification date’ but making it aceesible introduced too many risks of endless loops. Also, there is no universal agreement on what counts as a modification when there is so much connectivity.
If A is linked/unlinked to B, have they both been ‘modified’? What if formulas are defined that recalculate based on other field / relation changes? Does an update to a formula count as a modification?