How do I avoid creating duplicate application records in CMDB based on a field?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-14-2025 05:14 PM
Hi,
There was a custom field created in our CMDB application table to show an application's install target (e.g. install in Windows or Android etc). This custom 'install target' field only allows the selection of one install target. The problem this has now caused us is that we're having to create multiple entries for an application to show the different install targets.
e.g. Application A can be installed in a Windows or iOS machine
We're currently creating two entries in the table for Application A where one entry shows its install target is Windows and the other is iOS.
This has created a mess in our CMDB with all the "duplicates" and we're thinking what's the best way to show that an application has multiple install targets.
The results we're looking for is we only have one entry of Application A showing both possible install targets.
Is there an out of the box field that can be used or will this require a new field to be created on the table?
Does anyone have something similar with their applications in CMDB?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-14-2025 06:03 PM
one way is defining a business rule on the table, that runs on Insert and Update. Click Advanced and add script logic to check for a duplicate and abort the transaction if found. Details on the table and what fields indicate a duplicate are needed.