Skip to main content

Timextender Classic 26.3.0.1

Related products:Timextender Classic
  • Oct 28, 2026 10:33 AM UTC
  • 0 replies
  • 11 views

Thomas Hjermitslev
Community Manager

Today, we've published a minor release of Timextender Classic (v. 26.3.0.1) that re-enables upgrading from TimeXtender 20.10.84 to Timextender Classic. In addition to that, the release includes a handful of fixes for the Dynamics AX adapter, a fix that surfaces data source provider installation errors, and a fix for an issue with SSIS packages.

Fixed

  • Due to changes in the repository structure, TimeXtender 20.10.84 could not be upgraded to Timextender Classic. This is now possible once again.
  • While porting the updated Dynamics AX adapter, we found some issues with the support for Lakehouse through the Microsoft Fabric SQL Provider which have now been fixed.
    • Data type overrides would not be applied after enabling Uppercase table and field names and synchronizing since they'd use case sensitive matching for column names.
    • Importing a project from XML left Dynamics AX adapters that use the Microsoft Fabric SQL Provider without a provider.
    • Source scope variables, such as server name, database and timeouts, didn't resolve in scripts, usage conditions and SSIS.
    • With Column metadata set to Enhanced, selecting tables before the AX table dictionary was stored left a repository connection open on every click, until the connection pool ran out.
    • With a Fabric global database, the SSIS setting and timeouts on the Microsoft Fabric SQL Provider could get out of sync with the data source, and changing the provider settings didn't prompt you to synchronize.
  • When an enhanced data source provider failed to install, the dialog only showed "One or more errors occurred", without the actual errors. The dialog now lists every error, and you can click Details for the full technical information.
  • With several data sources that share a prefix, Classic could generate SSIS packages for the additional data sources with a double underscore in the name, while execution looked for a single underscore. The data load then failed because the package couldn't be found.
This topic has been closed for replies.