Using the Logs in Board to Troubleshoot Load Errors

When data loads fail in Board, whether it’s an entity hierarchy or cube population, the logs are your best friend. The logs pinpoint where and why the process failed.

🧭 How to Access the logs

  1. The logs can be downloaded from the Cloud Administration Portal.
  2. Open the log and scroll to view detailed system messages and error flags.

 

🔍 What to Look For

  • Line Numbers
    Identify which row in your CSV or data source caused the error.
  • Error Types
    Look for:

    • Orphan node: Indicates a missing parent in a hierarchy
    • Duplicate code: Same code listed multiple times in an entity
    • Invalid date format: Date does not match the expected format (e.g., DD/MM/YYYY)
  • Execution Summary
    At the end of the log, you’ll see the number of errors encountered and whether the load was terminated.

✅ Pro Tips

  • Use the logs immediately after any failed execution; don’t rerun before reviewing the log.
  • Copy and paste the specific error lines into a text editor for debugging or import them into Excel.
  • Cross-reference the line number with your original file to correct issues directly.
  • If you’re loading hierarchies, verify parent-child logic before re-importing.

🧩 Example Scenario

You attempt to load a department hierarchy, and the Data Reader fails. In the logs, you see:

pgsql

CopyEdit

[ERROR] Line 24: Orphan node ‘Dept_501’ has no valid parent.

You open the file, find row 24, and notice the parent column is blank. Fix it, reload, and the error is resolved.

🔄 Related Articles

  • How to Use the Data Reader Preview Function in Board
  • Error Handling – Common Hierarchy Loading Errors (coming soon)

👉 Next Step:

Need help diagnosing a persistent error? Contact QueBIT Support