General Debug Process
Detail examples for each process’ solution
1. Are all IRE required identifier fields mapped?
Go to “Class Manager”
Click “Open Hierarchy”
Find corresponding class and click “Identification Rules”
Make sure all required identifier fields are correctly mapped
2. Are all IRE required dependent relationships added?
Go to “Class Manager”, find corresponding class, and click “Dependent Relationship” if it exists
If “Dependent Relationships” section does not exist, it means there is no required dependent relationship
Make sure all dependent relationship is added
3. Is the discovery source allowed by IRE reconciliation rules to insert?
Go to “Class Manager”, find corresponding class, and click “Reconciliation rule”
Make sure current discovery source is allowed by reconciliation rules if any exist
4. Is source native key required? If required, is it mapped?
If mapping involves relationship or lookup or reference class, then source native key is required and must have unique value for each CI record.
Go to field mapping step, and check for “Source Native Key” field
5. Does IRE identifier field/combination have unique value?
Example 1, if 2 CI records have the same source native key value, then IRE will merge those 2 CI records together which overwrites each other and cause data not inserting correctly. Please make sure each record has unique source native key value.
Example 2, when mapping a computer and this computer’s software packages and software instances, there is a common mistake that user tends to use same software package name and software instance name because in reality those two names tend to be the same. But this will cause the CI to have exactly same value combination for computer field + software package field + software instance field. Then, during insert process, IRE will de-duplicate these identical records.
Additional Resources
