Understanding Discrepancies in DX Import Summary vs. Error Logs

Overview

This article explains why imported item counts in DX summaries may not always match error logs, particularly when items appear in multiple locations or outside the hierarchy.

1. Common Issue: Import Summary Shows No Failures, but Logs Indicate Missing Items

✔ Observed Discrepancy:

• The DX summary report shows zero failed imports.

• However, the error logs indicate at least two items were not created.

✔ Possible Causes:

• Duplicate items appearing in multiple locations in the hierarchy.

• Text objects or unstructured items being excluded from the hierarchy.

• Items failing to be created but not counted as "failed" in the summary due to calculation logic.

2. How DX Calculates "Failed" Imports

✔ The DX import summary uses the equation:

ini

CopyEdit

Failed = Detected - New

✔ This calculation can become inaccurate if:

• Items appear more than once in the tree.

• Extra text objects or unstructured data are present.

• Some items were expected but not mapped correctly.

3. How to Resolve the Discrepancy

A. Review the Full Log File for Missing Items

✔ Check the full DX import log to see which items were detected but not created.
✔ Look for error messages related to hierarchy mismatches or missing parent elements.

B. Check for Duplicate Items in Different Locations

✔ If an item appears in multiple locations, DX may count it differently in the summary than in the detailed logs.

C. Verify Text Objects and Non-Hierarchical Elements

✔ If extra text blocks are present outside the main hierarchy, DX may not count them properly in the summary.

4. Best Practices to Ensure Accurate Import Summaries

✅ Always review the full DX log file to check for unaccounted items.
✅ Ensure that all items are properly structured within a hierarchy before import.
✅ Check for duplicates in different locations that may be counted differently.
✅ Exclude non-hierarchical text objects if they are not needed in the import.

5. Conclusion

• DX import discrepancies can occur due to duplicate items, extra text objects, or non-hierarchical structures.

• The "Failed" count in the summary may not always reflect missing items if they are not structured properly.

• Reviewing the full DX log and verifying item placement in the hierarchy can resolve most discrepancies.