- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-23-2023 12:52 AM
It is a record that I created manually as a test, by pressing "New" button in the CI table, not something created by the discovery.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2023 02:36 AM
Did you add the custom CI class to the "List of CI Types to Pattern" in the pattern Designer?
You can open this by clicking on the button next to the ci class dropdown list..
Michael
Please mark the suggestion as helpful/like, if you find it useful to you or others who wants to refer similar content.
Please mark the solution as correct, if the answer provided has resolved your query.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-19-2023 05:16 AM
Yes, already added as shown below
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2023 11:25 PM
Hi @Au_an
I came across this while trying to fix a similar issue. Mine was due to creating a new CI class and pattern in one instance, and migrating it to another instance.
The pattern I created works in the source instance but not the one I migrated to.
I found that the target instance was missing a cmdb_class_info record for the new class I created. Migrating this record from the source instance fixed my issue.
If you've only been working in a single instance, perhaps just check if there is a cmdb_class_info record for your new class, and if there isnt create one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2023 09:12 AM
I know this is old, but we just experienced the same problem, and all of the suggestions here did not work. What finally did work was actually restarting the MID server - just synchronizing the patterns with MID was not sufficient.