- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-13-2015 05:12 PM
I have to be missing something incredibly simple here. I can run a glide record query for active=true:
var rec = new GlideRecord('cmdb_ci');
rec.addQuery('active',true);
rec.addQuery('name', 'foobarbaz');
rec.query();
while(rec.next()){
gs.print(rec.sys_id);
gs.print(rec.name);
}
...Yet when I want to set active=false, there doesn't appear to be an attribute on the record, nor a column in the cmdb_ci table that I can set.
Questions:
1. What the heck am I missing?
2. Am I completely off my rocker to want to set a CI to active=false? Maybe I'm violating some core ITIL principle?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-13-2015 05:38 PM
Active is not an oob field on the cmdb_ci table. Most use the Status field.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-13-2015 05:38 PM
Active is not an oob field on the cmdb_ci table. Most use the Status field.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-14-2015 09:06 AM
Ahh, its the silent failure of us "thinking" we're querying on active (since records are being returned), but there's actually no field on the records.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-13-2015 05:41 PM
I think it ignores that line. There is no active field on cmdb. I have had to add it everywhere I have worked, and have often asked myself this question. Setting a CI to inactive seems logical to me, too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-13-2015 06:54 PM