- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
Hi Everyone,
I am trying to create an Identification rule on cmdb_ci_service_auto table; its label has recently been updated to service instance after the Yokohama patch updates. The identification rule was created successfully, but there is a RED mark on it, and another error occurred.
"Rule entry under cmdb_ci_service identifier using non-existent table is ignored during identification!"
I am using the Robust transform map for this development and trying to fetch the data by import set number. In the staging table records, there is a comment,
"IRE payload is empty, there are no records to insert or update."
Even when we already have 20+ records in the Payload. I assume that this empty payload comment might be related to the IRE issue.
Can someone please guide me on this?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I was able to reproduce the issue in my Personal Developer Instance and apply a fix.
Since you mentioned that the Identifier is written on the cmdb_ci_service_auto table, the same value should also be reflected in the Identifier entry.
Solution
Please update the Identifier field in your configuration to cmdb_ci_service_auto. Once done, the error should no longer appear.
I’d also recommend running an Identification Simulation afterwards—this will allow you to validate and test your identifiers effectively.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
The issue appears to be with a Related Entry linked to this identifier. A table seems to be missing, which is causing the error.
I found some articles describing similar problems—please review them and let me know if they help resolve it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello @Laveena-Agarwal
We don't have activated discovery on our instance, and the suggested article plugins are already up to date. Can you provide any other suggestions?
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
I was able to reproduce the issue in my Personal Developer Instance and apply a fix.
Since you mentioned that the Identifier is written on the cmdb_ci_service_auto table, the same value should also be reflected in the Identifier entry.
Solution
Please update the Identifier field in your configuration to cmdb_ci_service_auto. Once done, the error should no longer appear.
I’d also recommend running an Identification Simulation afterwards—this will allow you to validate and test your identifiers effectively.