It’s our pleasure to announce release 25.1.0 of TimeXtender Master Data Management and TimeXtender Orchestration and Data Quality, featuring exciting new updates and enhancements.
Summary
This update introduces Azure Databricks integration, enabling job execution via orchestration packages. The Data Transfer package now supports SQL MERGE for updating destination tables, with new UI options for primary keys, custom values, and column collation. MDM web enforces desktop column restrictions with clear error indicators. Bug fixes enhance hierarchy limits, lookup columns, scheduling, data imports, and dataset publishing.
Our releases follow a phased rollout to ensure stability and performance. We begin by upgrading a select set of services for initial testing. After that, we gradually roll out the update to all customers, starting with low-risk environments and expanding systematically. Customers who prefer an earlier upgrade can request one at any time, by sending a request to our support, and we will schedule their update on an agreed date.
General
Access to Previous Versions
Users can now easily download executable versions of O&DQ and MDM via the provided links to TimeXtender's SharePoint. These versions don't require installation, allowing for seamless switching between different versions as needed. No special permissions are needed to access the links, and further details are available here.
TimeXtender Orchestration & Data Quality
Azure Databricks Package
The option to connect to and run Azure Databricks jobs from TimeXtender Data Orchestration has been added. To use this option the user must first create an Azure Connection Data Provider with the authentication information for the Databricks job to be executed by the package. Then, an Orchestration package can be created to connect to and run the Databricks job. Read more about Azure Databricks packages here.
Data Transfer Package Update
This release includes an update to the existing Data Transfer package. Enabling the 'merging' option will prompt the Data Transfer package to create a staging table, which will be used as a source for an SQL MERGE query, allowing updates to existing entries in the destination table. The O&DQ UI will also offer options to select the Primary Key, use a Custom Value to replace values in a destination column, and define collation at the column level when selecting data from the source. Read more about this new feature here.
TimeXtender Master Data Management
Required columns in web application
MDM Web now enforces the column restrictions set up in MDM Desktop. This version ensures that all column restrictions are applied in the web interface. The Web will prevent you from saving changes until all restriction violations are resolved. A small red 'X' will indicate which cell requires attention, and hovering over it will explain the rule being violated—just like in Desktop.
Bug fixes and smaller improvements
TimeXtender Master Data Management (MDM)
- The maximum height in Hierarchies has been increased to 10.
- Disabling users prompted them to update their subscription.
- Hierarchy attributes used as lookup columns did not work.
- Import failed for decimal columns.
- Saving an existing "Import from Database" action caused the action to break.
- Pre/post execution did not work when importing from the database.
- Importing from the database into a lookup column did not work.
- The schema drop-down was not ordered alphabetically.
- If the Embedded view was in "Recently Used," the start page showed an error.
- Users could not open tables with a lookup column if the lookup table had been deleted.
- Added support for availability group connection strings.
TimeXtender Orchestration and Data Quality (O&DQ)
- Compare query column names were updated when the column type was changed.
- New schedule groups were automatically assigned holidays.
- Running the schedule manually did not work.
- The SharePoint Data Provider did not work.
- The Data Transfer package could not create a table with two or more unique fields.
- The Help page was unusable.
- The Data Transfer package was not using the configured timeout.
- The schedule overview was shown as empty for TX-only customers.
- No holidays were displayed for TX-only customers.
- The sync process in the process map did not work for packages.
- The next run for a schedule did not update when changes were made to the schedule and saved.
- Creating a cloud optimizer package did not work.
- Active Directory queries did not work when they returned zero rows.
- The schedule for a package was not displayed in package properties.
- When a package's Windows process died, the package could not be executed again.
- Users stopped being able to execute tasks after having the Desktop application open for a while.
Turnkey
- Not all drop-downs order their values alphabetically.
- Columns added to a data source were defaulted to hidden in datasets.
- Preview did not work when a dataset column had a comma in the name.
- Filter in the rule automatically changed from "is not blank" to "does not equal null."
- An existing rule stopped working if the dataset name was updated.
- Links in the Exception action did not work properly.
- A published rule did not run if it was edited unless it was published again.
- Publishing a dataset was not possible from the column settings tab.
