ALM no_audit attribute issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-14-2018 12:52 PM
Our Asset Management team has a requirement to have multiple ALM tables' fields set to be audited. Simply changing no_audit=true to no_audit=false does not work, only removing the no_audit attribute completely seems to work. However, as these are base system tables, the attributes are repopulated on those fields every upgrade. Is there a problem with this particular attribute? Has anyone found a lasting resolution?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-29-2018 01:26 PM
I found the same that setting no_audit=false does not work either. Only removing the attribute seems to have the desired effect. Also it seems like date fields are forced not to audit regardless of what we do.
Anticipating the update issue you mentioned, I opted for a dictionary override instead. Haven't upgraded yet so cannot confirm if this solves the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-30-2018 07:32 AM
Just found that instead of leaving the property out completely, you can do "no_audit=". If you're not doing dictionary overrides, maybe this will prevent the property to change on upgrades. This also appears to help with date fields because just omitting the property doesn't do it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-07-2025 09:22 AM
It seems to be more complex and confusing, see KB0869832
