Best practices to update parent “Last Modified On” when child assets are added?
Summary: Manasa K is seeking advice from the community regarding a challenge in Collibra concerning the "Last Modified On" timestamp of parent assets, which does not automatically update when a child asset is added. They are contemplating a custom workflow to address this issue and are specifically interested in examples of implemented solutions, triggers or conditions used, and any tips to avoid unnecessary updates. The author is also requesting any insights on potential pitfalls or performance concerns.
Hi Community,
In Collibra, when a child asset is added under a parent, the parent’s “Last Modified On” does not update automatically. We have a requirement to run daily queries on parent assets based on this timestamp. Because the parent timestamp isn’t updated on child creation, we’re considering a custom, domain-scoped workflow that detects new child assets and updates the parent’s timestamp accordingly.
Questions:
Have you implemented a similar approach (workflow or API-based automation) to keep parent timestamps in sync with child additions?
What triggers/conditions did you use (e.g., specific child types, relationship changes), and how did you avoid unnecessary updates?
Any pitfalls, performance considerations, examples, or lessons learned you can share?
Thanks in advance for your insights
