You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my opinion it does not make sense to log an associated object with all it's members. This is clogging up the database unnecessarily. An option I implemented for this is to per AuditTrailSuperClass specialisation, populate an extra to be created attribute in the ModelReflection.MxObjectReference called KeyAttribute.
Only show this KeyAttribute to the user if a LogLine for a reference is shown.
The text was updated successfully, but these errors were encountered:
We recently released a new version of the Audit Trail (v7.5.0) that significantly improves the logging of references and reference sets. While it still logs attributes of references, it no longer does so as a single text field in the log line entity and it is now possible to filter which references have been unchanged, added or deleted. We believe this already significantly reduces the number of logged objects.
Please try this new version, and feel free to open a new issue if you believe this to be insufficient.
In my opinion it does not make sense to log an associated object with all it's members. This is clogging up the database unnecessarily. An option I implemented for this is to per AuditTrailSuperClass specialisation, populate an extra to be created attribute in the ModelReflection.MxObjectReference called KeyAttribute.
Only show this KeyAttribute to the user if a LogLine for a reference is shown.
The text was updated successfully, but these errors were encountered: