Integrations > Third Party Integrations > Import From Excel Workbook Discovery > Troubleshooting and Limitations – Import From Excel Workbook Discovery

Troubleshooting and Limitations – Import From Excel Workbook Discovery

  • Problem: The Import from Excel Workbook job compile time errors and problems working with the Excel files.

    Solution: Verify that you have performed the instructions in the Prerequisite section of the this discovery. For details, see Prerequisite - Set up permissions.

  • Problem: Importing a CI with the qualifier RANDOM_GENERATED_ID_CLASS, but without defined reconciliation rules, leads to duplicating such CIs.

    Solution: Currently this problem is not resolvable on the job side. This can only be resolved by defining reconciliation rules.

  • Problem: The Import from Excel Workbook job date errors.

    Solution: The date cannot be imported if it is represented in text format. This issue is not resolvable because of localization. Represent the date in numerical format.

  • Limitation: The DFM Probe breaks down the imported data into 20 KB chunks. This can cause identification issues.

  • Problem: The integration using the Import from Excel Workbook job fails when using the integration probe and the Run In Separate Process property is set to true.

    Solution: In case of using integration service, for the Import from Excel Workbook integration, the JDBC driver should be specified in the classpath as well.

    If your UCMDB server uses Oracle, you need to add ../lib/mcoracle.jar to the remoteJVMClasspath field as Adapter Properties when configuring the integration point; If your UCMDB server uses MS SQL, add ../lib/mcsqlserver.jar to the remoteJVMClasspath field.