Unable to insert record into table alm_hardware
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2025 02:21 AM
So, basically I was creating an ATF script where I was creating new hardware items as a part of test data creating for a test case. Below are my test steps
So, initially in the morning it was working fine but some an hour ago, it is showing this error particularly for the alm_hardware table. Although the previous steps are passing.
I have discussed with my Team as well, it seems nobody made any changes to the business rule and as per the business rule the record should trigger with following condition :
current.sys_class_name != 'alm_consumable' &&
current.sys_class_name != 'alm_license' &&
current.ci.nil() &&
current.substatus != 'pre_allocated' &&
current.model_category.cmdb_ci_class != ''
My step is satisfying all conditions but still failing. Please help to resolve this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2025 02:40 AM
Hi @SangyM check the CMDB as Asset and CMDB are synchronised and it seems that CMDB is blocking the creation as per your log error
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2025 02:45 AM
clearly the business rule is blocking the insert.
Did you try to disable the business rule and see if it works?
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2025 05:53 AM
Not working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2025 05:58 AM
@SangyM check the alm_asset record and compare it in the cmdb_ci table, most likely it exists there and create a blocker
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */