Why Your Field Changes Are Not Showing In The Activity Log
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago - last edited an hour ago
Ever feel like you are playing hide and seek with your Configuration Item (CI) data? You know you changed a field, but the activity log is acting like it never happened. Whether you are in the standard form or poking around the CMDB Workspace, not every field shows up by default.
Here is get those missing fields to show their faces.
The Standard Fix
Most of the time, this is a quick fix. Just look for the filter icon in your activity section and click on "Configure available fields." Pick the ones you actually care about, save it, and you are usually good to go.
When the System Plays Hard to Get
Sometimes, you add the field, you change the value, and the activity log remains stubbornly silent. I learned this the hard way when I tried to track the IT Application Owner field. I updated it, refreshed the page, and got nothing.
The culprit is the no audit attribute.
How to bust it:
Navigate to your list of Dictionary Entries.
Add the Attributes column to your view if it is not already there.
Find your field and peek at the attributes.
If you see no_audit=true sitting there, delete that part entirely.
Once that attribute is gone, the system will finally start keeping track of those changes. Just keep in mind that this only works for future updates. Anything you changed while that audit blocker was active is still going to be a mystery.
CSA | CAD | DF | DISCO | ITIL4