Normalize Columns During Excel Import Adds Unexpected Extra Column in Toad Data Point (4383006)

Customers importing Excel (.xlsx) files into a database using the Import Wizard and enabling Normalize Columns report that the resulting table structure includes an additional, unexpected column.

In scenarios where:

• An Excel file contains one or multiple worksheets
• The Normalize Columns configuration defines:
  • Label column (for example, Code)
  • Value column (for example, CodeValue)

Expected behavior (older versions, e.g. Toad Data Point 3.8):

• The import results in exactly three columns:
  • Identifier column (Date_)
  • Label column (Code)
  • Value column (CodeValue)

Actual behavior on newer versions:

• An additional column is inserted between the identifier and label columns.
• The extra column commonly corresponds to the first data column from the Excel source.
• This behavior breaks existing workflows that rely on the historical normalization output.

The issue has been reproduced internally using the latest version of Toad Data Point and has been reported by customers as present across multiple product releases.

At this time, there is no workaround that fully restores the legacy behavior observed in Toad Data Point 3.8.

The defect is currently being considered for resolution in Toad Data Point 2026 R3. Release targets are subject to change based on development planning and validation, but the issue is actively tracked.

Recommendations:

• Monitor future Toad Data Point release notes for a fix related to defect QAT‑22248.
• If further updates are needed, open a new service request through the Quest Support Portal and reference the defect ID.