Product Updates

Today, we’ve released an updated data source provider for Excel. Note: Today’s release contains the TDI version only. 20.10 BU and 20.10 ODX versions will follow.ExcelVersion: 23.2.0.0 (TDI)Added ‘_ResourceURI’ column as an available metadata column. This column is automatically populated with the filename of the Excel file for that row. Added default file types. Changed some file management behavior to avoid locking files. Fixed a bug related to aggregation of files and sheets and infer data types.

Today, we’ve published a minor release of TimeXtender Data Integration (v. 6963.1) that contains the changes listed below.ImprovedImproved the Ingest logic that manages data source providers to no longer try to download deprecated providers which caused confusing error messages. Renamed display names to no longer include "Semantic" Removed the limitation of reserved words for custom field validations and custom conditionsFixedFixed a wrong icon for super natural key fields in data lineage and Perpare table selection. Fixed various typos in the TDI application. Fixed an issue where the Metadata Manager in Ingest would produce a change notification for columns without the ‘original data type’ metadata. Fixed an issue with deploying Hierarchy tables with ‘Null check approach’ set to ‘Record Based’ Fixed an issue in Ingest on Fabric Lakehouse storage where tables were not transferred correctly  if they contained ancient dates. Fixed an issue where the ‘StepODXDataFactoryExecute’ was not cleaned up when the last table was removed from an execution package that allowed that step to exist. Fixed an issue where Convert to Mapping Set was incorrect for fields with custom transformations. Fixed an issue where Integrate Existing Objects was affecting existing views. 23785: Primary key check is getting skipped when a table has no mappings This issue was corrected - It affected tables with no mappings but having custom data, table inserts, and/or related records.

Today, we’ve released updated data source providers. See the changes below. CDATA Added a CData Placeholder Data Source (only valid for TimeXtender 20.10.57 and earlier)CSVVersion: 23.2.3.0 (TDI) / 1.0.1.0 (20.10 BU) / 16.4.2.0 (20.10 ODX)Added support for different character encodings. Updated labels of settings related to null value handling. Updated data type detection. Fixed issue with columns when doing file aggregation. Updated root folder logic for all cloud location connectors. SharePoint: Updated error message handling. Azure Data Lake: Updated to skip empty files when reading metadata.Excel, XML/JSONVersion: 9.1.0.0 (TDI) / 1.0.1.0 (20.10 BU) / 16.4.1.0 (20.10 ODX)Updated root folder logic for all cloud location connectors. SharePoint: Updated error message handling. Azure Data Lake: Updated to skip empty files when reading metadata.ODATAVersion: 9.1.0.0 (TDI)Fixed small issue with metadata discovery.ParquetVersion: 9.1.1.0 (TDI) / 1.0.1.0 (20.10 BU) / 16.4.1.0 (20.10 ODX)Updated root folder logic for all cloud location connectors. SharePoint: Updated error message handling. Azure Data Lake: Updated to skip empty files when reading metadata.REST, Exact Online, HubspotVersion: 9.1.0.0 (TDI) / 1.0.1.0 (20.10 BU) / 16.4.1.0 (20.10 ODX)Fixed issue with SQLite being unavailable in some cases. Fixed bug in Table Builder when using current endpoint.

Today, we’ve published a minor release of the TDI Portal that contains the changes listed below.ImprovedWhen adding a Prepare instance from a blueprint, you can now map the Ingest instances at the same time. That saves you the additional work of remapping the instances the first time you open the Prepare instance in the TDI desktop application. FixedIt was possible to try to create firewall rules for deleted instances, though the attempt would fail. Deleting a firewall rule for a deleted instance would fail. Rules related to deleted instances are now read-only until they are automatically permanently deleted along with the instance. In the Table Builder on a REST data source, clicking Get Schema would result in a "not implemented" error.

Today, we’ve published a hotfix release of TimeXtender Data Integration (v. 6935.1) that contains the changes listed below. FixedCorrected a problem with adding instance variables to Deliver instances. Addressed an issue where an incorrect DLL was loaded during data source execution.

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.SummaryThis 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.GeneralAccess to Previous VersionsUsers 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 QualityAzure Databricks PackageThe 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 UpdateThis 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 ManagementRequired columns in web applicationMDM 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.TurnkeyNot 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.

Two months into 2025 we're ready with the second major release of the year. Even though it's only been a month since the last major release, we have a lot of good stuff for you, including access to instance metadata for analysis, new data source providers, and a couple of much-requested features for Deliver and Ingest instances. And especially for partners, the new blueprints feature can be a real timesaver.When you upgrade to the new release, the Ingest service and data sources must be upgraded at the same time (i.e. you cannot upgrade the ingest service without upgrading data sources or vice versa). The reason is that we’ve redesigned the data sources architecture to enable the TDI TimeXtender providers in both V20 and Classic. See Compatibility of Data Sources and TDI/TIS Versions for an overviewNewCollect metadata and logs from instances for analysis (public preview)If you'd like detailed statistics on execution times, or any other metadata created by TimeXtender, this release is good news for you. With the new meta-collection feature in the Portal, you can analyze TimeXtender metadata and logs - in TimeXtender! 24 hours' worth of metadata and logs from the instances you select are exported to a data lake hosted by TimeXtender once a day. Using a regular TimeXtender data source, configured for you with the click of a button, you can copy the data into TimeXtender just like any other data source. Note that you'll need to be on the latest version of TDI.Three new data source providersIn our quest to provide high-quality first-party data source providers for basically everything, we've added three new providers:XML & JSON joins the CSV, Parquet and Excel providers for common data files.  Azure Data Factory - SAP Table enables connection to SAP through Azure Data Factory. Infor SunSystems makes the existing business unit data source available in TDI in an updated form that supports SunSystems version 5 and up.TimeXtender Enhanced data source providers replace CDataFrom this release, the TimeXtender Enhanced data source providers replace the third-party 'Managed ADO.net' providers from CData. As we're no longer distributing CData providers, they will not receive updates and no new providers are available for use. If you have data sources that use CData providers, we recommend that you begin migration to the TimeXtender Enhanced providers. For more information on how to change a data source provider please see: Data selection for Deliver endpointsWe've added support for data selection, instance variables and usage conditions in deliver instances. These features have long been available in the Prepare instance and make data selection rules on tables much more versatile. Adding these features to the deliver instance, makes it possible to, for example, use the same Deliver instance to deploy endpoints with different data (e.g. departmental data) in each endpoint.Add timestamp to tables in the Ingest instanceIf you'd like to know when data has been copied from a specific source, you can now have the good old DW_Timestamp column added to tables in the Ingest instance. For now, this is supported when you use Azure Data Lake Storage, Fabric, or SQL as your Ingest instance storage.Partners - share instance blueprints between customers  (public preview) As a partner working with many TimeXtender customers with roughly the same setup, you might feel a slight deja vu when you create the same data warehouse structure for the third time. Because time matters, we've created the blueprints feature to save you from that repetitive work.A blueprint is an instance where anything remotely sensitive, such as logs and usernames, is removed. In the new version, you can, with the consent of the customers, share a blueprint of Customer A's instancewith Customer B. Once a blueprint has been shared, Customer B can add a new instance based on that blueprint instead of starting from scratch.ImprovedImproved UI for setting up REST data source connectionsWe've improved the experience when setting up TimeXtender REST data source connections so that you can show and hide the sections that matter to you, as well as adding additional validations for essential fields. In addition to that, based on feedback that the old name could be misleading, the “global values” setting has been renamed to “connection variables”.Edit deleted instancesYou can now edit deleted instances. If this sounds like something you’re not likely to do, you’re right, but it can be useful in a few edge cases. For example, you can rename a deleted instance if you want to create a new instance with the same name.FixedTDI PortalIt wasn't possible to rename an environment to the same string with different capitalization (e.g. "Prod" -> "PROD") On the Instances page, fixed an issue with deleting environments containing only deleted instances Fixed a bug that would allow a mapped data source connection to be deleted after upgrading it to the most recent version Filters are now still applied after deleting a data source connection. Fixed a bug in the REST provider where the connection variables were not applied to the dynamic values from endpoint query. We now take into consideration the value of ‘Empty fields as null’ when finding data types. This can help find the correct data types when the data is a mix of values and empty values/null. Updated the look of the 'Multi-factor sign-in' card on the 'Basic info' page to fix a visual inconsistency. When you migrate an Ingest instance from one environment to another, we've made the error message more useful should the validation of the data source mappings fail.TimeXtender Data IntegrationIn the Create Index window, it was impossible to see all fields if you had a lot of fields on a table since the list did not have a scroll bar. Using the Skip option when loading tables for the Ingest data source query tool failed with a null parameter exception.

We've published a hotfix for TimeXtender Orchestration, introducing the following improvements: Changes:Optimized Execution in SaaS: Executions in the SaaS environment can now be configured to run on dedicated execution virtual machines Configurable Execution Mode: A new configuration variable allows customers to choose between execution virtual machines or the previous execution method.Fixes:Executions Stuck in Running State: In the SaaS environment, orchestration executions would sometimes remain in a running state indefinitely, even after their underlying tasks had completed.Note that this issue is fixed by changing your execution mode to use execution virtual machines. For further details please reach out to your TimeXtender contact Consistent Task Execution in O&DQ Desktop: In the SaaS version, tasks executed from the O&DQ Desktop client will now run in the same location as the customer's scheduled executions, rather than executing locally.

This week, we’ve published a hotfix release of TimeXtender Orchestration 24.3.0.53 that contains the changes listed below.FixedWhen packages/processes go to an idle state that exceeds their timeout, users will now be able to rerun those packages/processes without clearing the job queue after the configured timeout has passed.

Today, we’ve published a hotfix release of TimeXtender Master Data Management  (v. 24.2.0.24 and 24.3.0.21) that contains the changes listed below.FixedResolved an issue where opening a table that referenced a deleted lookup table caused the application to display an error message.  

Today, we’ve published a hotfix release of TimeXtender Desktop (v. 6898.1) that contains the changes listed below. FixedResolved an issue that occurred when adding conditional lookup fields with joins on fixed values in a Snowflake prepare instance. Optimized data cleansing procedure to improve performance in a Snowflake prepare instance. Fixed an issue with out of memory exception when changing schemas after migrating. Fixed an issue where Jobs would say they were invalid due to unsupported version.

The first major release of 2025 brings new time-saving features for data source connections, an improved REST data source provider, less "simple" Fabric Prepare instance storage, and a whole lot of smaller changes. Check out the full list below! New Import and export data source connectionsYou can now import and export data source connections to use in different accounts, save for later, or share with coworkers. You can of course use import to create new data source connections, but you can also override the data of an existing connection. In case some fields cannot be mapped to the connection when you import, the mismatched fields will be listed so you can decide what to do.Two import/export formats are supported: The connection string ("key=value;key2=value") used by the ODX in TimeXtender 20.10, and a JSON-based connection profile that includes more extensive information. No matter the format, passwords, and other sensitive fields, will always be excluded from the export.  Change data source providerWe added the option to change the provider of a data source connection. While you can change freely between providers, changing from one SQL provider to another is obviously less of a hassle than changing from SQL to a REST provider. If the old and new providers don't have exactly the same fields, you'll be able to review the mismatches and make adjustments before committing the change. Customize code for Prepare instances on Fabric Lakehouse (Public Preview)When you're using Microsoft Fabric Lakehouse as Prepare instance storage, you can now add inline scripts that are executed along with the Fabric Notebooks created by TimeXtender Data Integration. With this, the customize code feature is now also supported for Prepare instances on Fabric. Improved Improved REST data source providerWe've made a ton of improvements to the REST provider to make it more flexible and able to support more data sources. You can now import connection information that follows the OpenAPI/Swagger Specification which can be a real time-saver. The new 'Authentication endpoint' authentication type allows you to get authentication data, e.g. a token, from an endpoint and use that for authentication, e.g. by adding it to the header of all requests. We've also eliminated the requirement to select a table in TimeXtender Data Integration from all endpoints that the endpoint you actually wanted data from depended on. The new 'Endpoint query' dynamic values source lets you create dynamic values that combine data from multiple endpoints with a SQLite query. On top of that, the REST provider now supports data in CSV format in addition to JSON, XML, and plain text. Other changes included the following:New option on endpoints to set a delay before the first request to the endpoint as well as a delay between requests. Global values, i.e. variables that can be set once and used across endpoints. Dynamic values created by pagination are now available outside of pagination. New built-in dynamic values: TX_ExecutionTimestamp, TX_XmlFileName, TX_TableFlatteningFileName. Support for OAuth response with 'accessToken' instead of 'access_token'. Support for a custom header prefix for OAuth token. New option for setting the data format (JSON/CSV/XML/Text) explicitly instead of relying on the automatic selection logic. After converting from JSON to XML, tables with an ID column only are now removed from the metadata result. The endpoint path can now be overridden by a complete URL. Pagination can replace both the URL and the post body at the same time. New option to set empty fields to null. New option to enable debug logging. Prepare instance on Fabric Lakehouse no longer "simple" (Public Preview)When we added support for Microsoft Fabric Lakehouse as Prepare instance storage in our last major release, functionally was limited to what's possible with simple mode enable. With this release, that's no longer the case. We've added support for transformations, conditional lookup fields, supernatural keys, and aggregate tables.However, we still have some work to do since the following features are still not supported: History, custom data, custom views, junk dimensions, related records, table inserts, and hierarchy tables. While incremental load is supported, it is currently necessary to manually define an incremental selection rule on the Prepare instance. Incremental settings from the source are not automatically applied. Remember instance migration settingsYou can now save your settings when migrating an instance between environments, making it easier to reuse them later. Saved settings will automatically apply when you migrate the same instance again, but can be modified as needed before migrating.  Fixed (TDI Portal)Fixed more than a dozen smaller issues and inconsistencies in the look and feel of various tables in the Portal to create a more streamlined and user-friendly experience. Fixed an issue where right-click was disabled in tables even when there was no custom menu defined, preventing users from, e.g., opening an instance in a new tab. Fixed an issue with changing Prepare storage type. Values could visually overlap on the instance overview page. Fixed an issue where uncategorized instances could not be added when creating a new environment. Fixed an issue where timeouts were treated as shorts instead of integers on some instance pages. The Data Source Mappings section would shift when opening a dropdown. On the Instances page, the Uncategorized Instances section would be displayed even when empty. The Edit Environment modal couldn't handle long instance names. When adding a data source connection, sometimes an error message would only pop up after you had been redirected away from the page. Unclear wording in successful update message on data source connections. Removed ":" from data source connection checkboxes with no description. Fixed an issue where customers could not change basic info for their organization. In the activity log, some values related to firewall rules and restoring an instance would not be displayed correctly.  Fixed (TimeXtender Data Integration) Fixed reference to old instance type names in the job log. Fixed issue where editing a snippet-based script action could cause a "Label not found" error Fixed an issue where you could add an execution package with failure handling set to retry steps while having multiple threads enabled and managed execution disabled. Fixed an issue in Snowflake where the deployment of a table would fail if the raw schema was different from the error/warning schema. Fixed a null reference exception when deleting a table referenced in a custom data selection rule across multiple data areas. Fixed an issue where the Metadata Manager did not pick up changes when tables and columns match on an identity other than name. Fixed an issue when execution of a table in Ingest when the storage type is Fabric Lakehouse with schema and the source of the Deliver table is TimeXtender OneLake Finance & Operations Data Source would fail with "name 'PATH' is not defined" and/or "name 'FULL_LOAD' is not defined"

Today, we’ve published a hotfix release of TimeXtender Desktop (v. 200.0.6848.1) that contains the changes listed below. Fixed Fixed an issue where a deadlock could occur for the Ingest Service, when refreshing the authentication and repository connection at the same time. We know this has been a big issue, and would like to thank the partners and customers who helped incrementally test and provide feedback and knowledge so we could solve the issue.  Fixed an issue where starting a windows server in Fast Boot / Hiberboot mode with an Ingest service installed could cause the DNS issue fixed in version 6823.1. This happens as the Fast Boot mode skips the regular windows service startup flow and ignore the ingest service network validation logic. Fixed an issue when transferring data from Ingest to Prepare, where an invalid cast exception would be thrown on a decimal data type. Fixed an issue when executing a Deliver instance when the table is based on a view from a Prepare instance, where the Post Valid Table option is enabled. Fixed issue with a misleading error message when executing a transfer task for PostgreSQL data source, when incremental rules were set up and no new data was present in the source. Fixed an issue where the database cleanup tool would mark the table message functions as objects to drop. Fixed an issue where the system incorrectly attempted to drop a regular SQL table using the syntax for external tables. This led to errors during table deletion operations.

Today, we’ve published a hotfix release of TimeXtender Ingest Service (v. 6823.1) that contains the changes listed below. FixedFixed an issue when importing Metadata in the Ingest when using ADO, OleDB, and CData providers, where it would stop reading meta data if a table without columns was found. Fixed an issue where the Ingest service would cache the DNS host of the authentication and gateway service forever. This caused issues for Ingest services automatically started before a valid internet connection was established where the cached DNS would cause the "The remote name could not be resolved" issue.

Today, we’ve published a hotfix release of TimeXtender Desktop (v. 6822.1) that contains the changes listed below. NewSupport for Fabric SQL Database as Prepare storage. FixedFixed issue with Ingest Incrementally loaded tables that was added to a Prepare instance, which caused errors during deployment and execution. Fixed issue with Database Clean up tool wanting to delete _I tables because of the error above. Fixed issue with wrong syntax when deploying objects in Snowflake. Fixed issue with wrong syntax when deploying objects in SQL Synapse.

We hope you've had time to put the pumpkins away because now it's time for a new major release of TimeXtender (v. 6814.1). The release has a focus on data ingestion with improved synchronization from data source to Ingest instance, new data source providers, and better orchestration and scheduling, but that's not all - check out the list below! NewRedesigned metadata synchronization and table selection: We've completely reimagined how you manage metadata and select tables in the Ingest layer. With these changes, we aim to make it easier to combat schema drifts, e.g. when you change data source providers, and put you in firm control of what goes into your Ingest storage. 'Synchronize Tasks' are now known as 'Metadata Import Tasks' and will no longer do a full synchronization of the data source. Rather, it will import the metadata from the data source and store it in the data storage of the Ingest. The Data Source Explorer has become the Metadata Manager and is now the place for synchronizing data sources - selecting and mapping tables in the data source to tables in the Ingest storage - all based on the metadata imported by the Metadata Import Tasks.  Easier orchestration with synchronization from TDI: Your transfer tasks and execution packages in TimeXtender Data Integration can now be synchronized with TimeXtender Orchestration for more feature-rich orchestration and scheduling than possible with Jobs in TDI. To get started, grab an API key from the TDI portal and use it to create a new "TimeXtender Data Integration" data provider in TimeXtender Orchestration. Warning: Jobs have been deprecated. Please schedule TDI execution packages via TimeXtender Orchestration rather than using jobs Redesigned Instances page: We've redecorated the Instances page to make it easier to use. Among the changes are a new list view to complement the card-based view, collapsible cards to help you focus on the environments you're working on, and a consolidated "toolbar" with a Search box and buttons to add instances and manage environments. Prepare instance on Microsoft Fabric Lakehouse: You can now use Fabric Lakehouse as Prepare Instance storage. However, in this first version, the functionality for Prepare instances on Fabric Lakehouse is limited to what's possible with Simple Mode enabled.   New data sources: In our quest to make connecting to data sources easier and more consistent, we're ready with three new TimeXtender-branded data source providers:  Parquet (similar to the existing CSV and Excel providers), OData (similar to the existing REST provider) and Finance & Operations OneLake which supports transferring data to Ingest instances using Azure Data Lake Gen 2 or Fabric storage. If both the Ingest and Prepare instances use Fabric storage, the data will bypass the Ingest storage and be transferred directly into the Prepare storage, leading to better performance and saved storage space. Bring instances back from the dead: Possibly inspired by the recent Halloween spookiness, we've implemented a soft delete feature for instances. You can now restore a deleted instance for up to 30 days after deletion. ImprovementsThe Migrate Instance modal has been restructured into steps, includes a review section, and lets you select the source instance and environment in the modal.  In the top-right corner of the TDI Portal, you'll now find a nine-dot menu for easy navigation to TimeXtender MDM, TimeXtender DQ, and TimeXtender Orchestration. A banner on the Home page will now let you know about upcoming system maintenance. The Upgrade data source page has received a new coat of paint to match the new TDI Portal design. On CSV data sources, you can now define custom null values, such as "N/A" and "-",  in the aptly named "Null Values" field. On SAP Table data sources, we have added a Table name filter that makes it possible to filter out some of the irrelevant tables before you can even see them in TDI. This can make importing metadata from the source much faster and makes it easier to manage the notoriously large amount of tables in SAP. To prevent accidental password leakage, we've applied password protection to more relevant fields in the TimeXtender-branded data source providers. You can now connect to Azure Blob Storage (or ADLS) using principal user credentials. This applies to the TimeXtender-branded CSV, Excel, and Parquet data sources.  We've made the Ingest authentication refresh logic more robust to prevent potential issues. We've changed SQL queries to include a 30-second command timeout, preventing client lockups during cloud database issues, and improved Timextender Data Integration logging for clearer task tracking. When you upgrade TimeXtender Data Integration, you can now see more information about what is being imported from the old version in the first run of the new version. FixedOn the Migrations page in the TDI Portal, cards now accommodate longer instance names. On the Instances page in the TDI Portal, a non-data estate admin user would sometimes get "User not authorized" or "Missing data estate permission" errors. In the TDI Portal, Test Connection would return "successful connection" for non-existing paths in cloud-type locations (AWS, Azure, GCS). In TimeXtender Data Integration, we have improved the visualization of invalid data sources under Ingest instances. They'll now have "(invalid)" postfixed to their name which will be displayed in red. Fixed a "Task was canceled" error when opening TimeXtender Data Integration with over 250 instances and adjusted the HTTP timeout settings to improve loading. Using the integrate existing objects feature in TimeXtender Data Integration would sometimes cause a "duplicate key" error due to unfiltered duplicate keys. Duplicate keys are now properly handled to prevent this error. In TimeXtender Data Integration, we fixed an issue with a radio button that prevented you from switching between the Valid and Raw tables when you created indexes.   In the Filter Rows window in TimeXtender Data Integration, you could click the Preview button even when the data source did not support preview. In TimeXtender Data Integration, we fixed an issue where changes in Edit SQL Snippet Transformation were not being saved. In TimeXtender Data Integration, we have improved the message displayed when an error is thrown on Reports > Errors. In TimeXtender Data Integration, tables with selection rules would fail when dragged from one data area to another on a Prepare instance that uses Snowflake as storage. In TimeXtender Data Integration 6766.1, SAP data sources experienced degraded performance due to the accidental release of a 32-bit version of the TXIntegrationServices component. We updated the stored procedures for executing Prepare instances to sort data by 'DW_ODXBatchNumber' for insertion into the valid table during a full load. If 'DW_ODXBatchNumber' is not available, it will default to sorting by [DW_Id] in ascending order. The execution of execution packages would sometimes fail with the error "terminated unexpectedly". To solve the issue, we made the access token refresh logic more robust.  It now permits refreshes up to 4 hours before expiration, incorporates retries for failed attempts, and includes an automatic refresh when the execution service restarts. The Execution Service would ignore proxy settings when executing packages, which could result in misleading error descriptions for the end-user.  The TimeXtender REST data source provider now handles empty property names, property names that start or end with a colon, and property names with more than one colon.

It’s our pleasure to announce the release 24.3 of TimeXtender Orchestration & Data Quality and TimeXtender Master Data Management, featuring exciting new updates and enhancements.SummaryThis release brings several enhancements to boost usability, flexibility, and user experience across TimeXtender's platforms. Key highlights include improved integration with TDI, new capabilities for optimizing cloud resources, better time zone management, and easier access to previous versions. We have also updated product naming and expanded database permissions for users. These updates demonstrate our commitment to meeting customer needs and delivering a more seamless, intuitive experience. GeneralAccess to Previous VersionsUsers can now easily download executable versions of O&DQ and MDM through 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 required to access the links, and further details are available in this support article.Product RenamingWe are excited to announce that we are in the process of renaming our products as part of our ongoing efforts to better align our offerings with the needs of our customers. As part of this transition, you may notice some changes in product names, labels, and documentation across our platform.Please be aware that this renaming is an ongoing process, and while some updates have already been implemented, others will roll out over the coming months. During this time, both old and new product names might appear in certain areas.We appreciate your understanding and patience as we work towards a smoother and more consistent experience. Data Orchestration and Data Quality (DG)TimeXtender Execution OverhaulWith the latest release of TimeXtender Data Integration and TimeXtender Orchestrator and Data Quality(DG), the Orchestrator can now connect directly to Data Integration tasks and execution packages. This update reduces execution overhead, enhances control over execution order and parallelism, and provides a more visually detailed status of each task and execution package.We’ve also added a Sync button in the TimeXtender Data Provider that auto-generates Data Integration tasks and execution packages, along with a default process and process map for each Data Integration environment. This feature reduces repetitive setup across both Data Integration and Orchestrator, allowing you to create tasks in Data Integration and simply Sync in the Orchestrator to generate everything you’ve added.Cloud Optimization packageThe option to create a package to scale, switch on or switch off Azure resources as required before and/or after processes that rely on these resources are run, has been added to TimeXtender Data Orchestration. In order to use this package type an Azure data provider in Data Orchestration with sufficient Azure privileges to update these resources is required. Read more about Cloud Optimization packages in TimeXtender Data Orchestration here. Updated Folder Structure for Improved ClarityAs part of our ongoing efforts to improve usability, we have reorganized the folder structure within our system. To make it clearer which functionalities belong to specific modules, we have created two new parent folders:Orchestration Data QualityAll existing folders have been moved into these parent folders based on their respective functionality. This updated structure will make it easier for users to navigate and find relevant features under the appropriate modules.Please note that while the structure has changed, all existing functionalities remain intact.Supporting Time ZonesWe are excited to announce that users can now change the time zone for their service in Data Orchestration and Data Quality (DG). This update ensures that schedules will run according to the user's selected time zone, making it easier to configure schedules based on their specific location and environment. This feature also accounts for daylight saving time, ensuring that schedules always run at the correct time, without being shifted an hour forward or backward during certain months of the year. Read more about this new feature here.Azure Functions Data ProviderAzure Function packages now use Data Provider for authentication. Additionally, the user interface has been updated to ensure consistency in appearance and functionality with other packages. Master Data Management (DM)Expanded Permissions Options for Database UsersWe have made an update to our database user management capabilities. Previously, users could create a database user and assign various permissions. We are pleased to announce that we have expanded the selection of permissions available.The following permissions have now been added to the selection:View Database State Create Schema References Bug fixes and smaller improvements TurnkeyQuick navigation to rules or datasets directly from exception details. Exception overview now updates URL parameters with filter and search changes, enabling easier linking with specific filters. Gateway Data Providers now supported in Turnkey. "Report Error" button in Turnkey now automatically creates a ticket in the ticketing system. Enhanced email preview functionality. Rule filter preview improvements: hidden columns are now indicated with an icon in the header. Better mapping of rule owners. CC users are now correctly mapped in email notifications. Improved dataset preview functionality. Enhanced error handling for Data Providers creation. Improved overview and management of Data Providers. Browser tab titles now dynamically reflect the current page.Data Orchestration and Quality (DG)Email notifications were empty when a query was moved to another system or duplicated. Updated icons. TimeXtender packages could be created with wrong setup. UI was also updated. Folder could not be deleted. Excel attachment is now only created when configured in Quality & Process configuration. Added error message for Powershell packages. Email notifications were missing from Email Preview. Azure Powershell package failed in on-prem setup. Process could not be deleted. Redis cache logic enhanced to prevent error in compare queries. Moving object groups between folders was not possible. Duplicating a process with execution steps resulted in execution steps not working correctly. Limited TimeXtender version did not have user groups visible. Package parameters extended. Query snippet could not be deleted. Execution of Fabric packages failed on PROD. Limited TimeXtender version showed objects on process maps that are not a part of the light version. UI for Data Providers in Gateway was incorrect.Master Data Management (DM)Flat view in hierarchy was not working as expected. Disabled users were able to login to the portal. Format of number columns for single row editor fixed. Error when a role of a user was changed. Issues when adding new users. Changing a field to a Item list sometimes resulted in an error. Renaming a table using hierarchy resulted in lost data. Added information to user regarding limitation of changing Data type of Item List. Error when adding a new user or new user group. Error when unchecking/checking filter in desktop. How to upgrade?In Master Data Management, users in versions 22.5 and above can complete the upgrade themselves through the Desktop client. See the Guide.Contact help@exmon.com to upgrade from Exmon 22.4 or below. 

Today, we’ve published a hotfix release of TimeXtender Data Integration and TimeXtender Ingest Service (v. 6766.1) that contains the changes listed below. FixedReplaced the lock with a mutex to prevent thread conflicts in the workspace. Fixed a syntax error in the generated Snowflake script caused by an incorrectly placed semicolon in the data cleansing procedure. Fixed an issue where the max degree of delivery instance parallelism reset to 1 after reloading the execution service configuration. Resolved an issue preventing new fields from being added to a DW table with existing mappings. Fixed migration errors between Prepare Instances due to missing extended properties. Updated fiscal week calculation to fix a month comparison issue. Fixed a loading issue with the Custom View Tracing Object when views were split across multiple data warehouses. Updated the instance list order in the Ingest Service Configuration Tool. Fixed an issue in Synchronize with Ingest Instance where fields weren't auto-selected if field names had changed. Fixed a UI issue where the persist view info box was visible by default, and the icon misaligned when resizing the dialog. Resolved an issue where the parameter rename dialog in the custom view script was partially obscured by Windows scaling. Resolved an issue where job statuses failed to update after task completion by implementing retry logic.  We fixed an issue where the dynamic role-level security table was not included in "end-to-end" Dynamic Perspectives Fixed an issue with missing command timeout for Dynamic Security queries against the "Deliver" storage Fixed an issue when adding a private data source (ADO.NET), where an error saying assembly file was not found was thrown.

This release primarily contains important bugfixes, along with some infrastructure changes to how we create and handle instances.NewAdded infrastructure support for handling multiple SQL servers for instances. Once the limit on our existing instance SQL server (sql-instances-prod.database.windows.net) is reached, new instances will be created on a different SQL server (sql-instances-prod-002.database.windows.net). This may require users to add a firewall rule for the new server. It is hosted on the same region as our old server (EU West) and should not require any new IPs to be whitelisted.FixedCloning instances now handles copying passwords and secrets correctly Moving instances to the same environment they're already in no longer creates a backend call Changed data source name limits on the portal to be compliant with our other services Fixed refresh tokens in the portal Fixed issue where the uncategorized environment could be edited Fixed issue where "add user" button disappeared from organization page

Today, we’ve published a hotfix release of TimeXtender (v. 6745.1) that contains the changes listed below. FixedFixed a bug where incorrect schema would be applied to custom views

Today, we’ve published a new release of TimeXtender (v. 6744.1) that contains the changes listed below. NewProduct renaming:TimeXtender desktop is now known as TimeXtender Data Integration (TDI) TimeXtender ODX service is now known as TimeXtender Ingest Service (TIS)ODX is now known as Ingest.MDW is now known as Prepare.SSL is now known as Deliver. String aggregation as an option for aggregation tables. The output will be separated by a comma and will be ordered by the content of the column Added persist view functionality, which will persist a view as a table. Introduced a filter for available data providers to improve data source selection. Added a feature that allows users to clone instances for more efficient management. Added hidden fields support in data source connection forms. In the Execution Service Configuration tool it's now possible to set up how many parallel executions of Deliver instances should be possible at a time. Default is set to 1.ImprovedThe TimeXtender database cleanup tool can now run without the need of a data area to exist. The solution explorer in TDI client will now remember if a node is collapsed when refreshing the solution tree  Changed the error message for opening incompatible instances. Environments page renamed to 'Migrations' page at /migrations and all non-transfer related functionality removed. The Instances page has been merged with the Environments page, now accessible at /instances, featuring drag-and-drop functionality for moving instances between environments. A new design has been implemented for data tables. Improved the loading speed of the organization table.FixedDouble clicking a view field in data lineage would not select the view field node  Shutting down TDI (TimeXtender client) with step in the execution queue would ask you if you wish to exit, but exit would happen if you clicked No instead of Yes Resizing the column width in the TIS (ODX) incremental load dialog was disabled Dragging a table node from the semantic source database browser to the semantic tables node did not work Dragging a field node from the semantic source database browser to a semantic table node did not work The context menu for editing an environment was shown on the default environment in the TDI (TimeXtender client) The buttons for showing schemas on the TIS (ODX) ADO and OLE.DB data source advanced settings were hidden. Null reference error when validating Deliver (SSL) Qlik endpoint of the type Qlik View while using Snowflake as the source Prepare instance (MDW) Wrong label for the table distribution setting for Dedicated SQL Pool Synchronizing the Prepare instance (MDW) with an Ingest instance (ODX) would show tables as missing when the data source had "data on demand" enabled and no execution tasks were added on the data source Searching for tables for the mapping sets in the Prepare instance (MDW) would not find tables where the data source had "data on demand" enabled and no execution tasks were added on the data source Listing constraint suggestions on the Prepare instance (MDW) would not find tables where the data source had "data on demand" enabled and no execution tasks were added on the data source Adding new view fields to a standard view was blocked after selecting a field in the overview pane Some Ingest instance (ODX) execution logs sometimes went missing due to a timing issue in the Ingest instance (ODX) execution logic Potential null reference error when two users concurrently committed a change on an Ingest instance (ODX) data source or Ingest instance (ODX) task  Some Semantic dialogs could only resize horizontally Tabular Security DAX was incorrect when having more than one setup Moving Ingest instance (ODX) data type override rules up and down sometimes caused an index out of bounds exception A circular reference in data lineage with history tables caused the data lineage to run forever.  Label in warning and error reports dialogs shows database instead of data area When adding a private data source (ADO.NET) an error saying assembly file was not found was thrown When right-clicking on a table with a mapping type of the Integration Table, the client sometimes crashed. Updated the layout of the Deliver Instance (SSL) Role Dialog  Fixed an issue where the TIS (ODX service) would get stuck in 'Starting' state if the authentication token could not be renewed. Addressed alignment issues with dropdowns and the search icon in multi select filters. Corrected the incorrect tooltip displayed for the delete instance button. Resolved an issue where the hand cursor appeared on mouse over an instance in the Environment page, but clicking did not trigger any action. Fixed an issue where it was not possible to save a prepare (MDW) instance after previously experiencing an error. Fixed a bug that caused the customer table to not refresh after deleting a customer. Resolve an issue that made it impossible to delete some data source connections because of hidden double spaces in the name. Fixed an issue where important setup properties were accidentally overwritten during updates, and ensured that the connection string is securely encrypted when edited. Fixed an issue to ensure that repository information and related secrets stay properly aligned and consistent. Resolved an issue that caused organization creation to fail due to incorrect data handling. Ensured that comments are now properly added to the activity log when removing a company and removed duplicate comments that appeared when deleting an organization

Hotfix release of TimeXtender Desktop (6718.1) and TimeXtender ODX Server (6718.1) that contains the changes listed below. FixedDesktop21779: Add internet connection check on ODX service and Job Executions startupFixed an issue where the ODX and Execution services would get stuck at the 'Starting' state when there is no internet connection available. It will now retry for 5 minutes and if there is still no internet connection available, then it will shut down the services.21738: Null reference error when adding One-To-Many relations to SSL modelFixed an issue where One-To-Many relations on SSL wasn't created correctly and would cause an error when re-opening the project.21748: Authentication settings changes trigger job execution service restart.Fixed an issue where the execution server would restart when the authentication settings file was modified.

We are excited to announce the latest version of XPilot, packed with significant improvements and new features to enhance your experience. Here are the highlights:5x Faster Responses: With a new and improved Index, XPilot now delivers responses five times faster, ensuring you get the information you need without delay. 10x More Intelligent Responses: Powered by GPT-4o, XPilot's responses are now ten times more intelligent. Additionally, XPilot now has the capability to remember previous interactions, providing more contextually relevant answers. A response not quite hitting the mark? Ask XPilot to clarify or provide a correction. More Knowledgeable: XPilot is now more knowledgeable than ever, incorporating all the latest knowledge base articles and Exmon user guides. And now even YOU! can help make XPilot smarter, as it's also trained on "answered" user community questions.  Improved Usability: The user interface has been completely rebuilt from the ground up, significantly improving usability and making it easier to navigate and find the information you need. Responses now include images and GIFs when needed, making it easier for users to understand complex information. This visual enhancement aims to provide a more intuitive and engaging user experience. Code Generation: XPilot can now accurately generate SQL and DAX code, making it a valuable tool for users who need precise and efficient coding assistance.Try it out for yourself at https://xpilot.timextender.com/ 

 Hotfix release of TimeXtender Desktop (6698.1) that contains the changes listed below.FixedDesktopFixed issue where token expired after 24h and was unable to refresh in the execution engine.

Hotfix release of TimeXtender Desktop (6691.1) that contains the changes listed below. Fixed Desktop 21596: Can't deploy DWH with service principal authentication Fixed an issue where service principal authentication was failing when deploying a SQL data warehouse 21604: SaaS Data Selection Rules - source vs destination fields Fixed issue where the data selection rule pane showed destination field names instead of source field names in table mappings. 21641: Implement 'WITH RECOMPILE' in Direct Read procedures All data movement procedures for moving data between data areas are now created with 'WITH RECOMPILE'. This will be picked up by the differential deployment. 21673: Issue when connecting to MDW SQL Storage when it is a Azure SQL Database This has now been fixed. 21679: Duplicated advanced features on SQL/Azure DWH Fixed and issue where some Advanced DWH features were listed twice 21706: SSL instances upgrade from 1.0.0.0 to 2.0.0.0 are missing extended properties on one table Fixed an issue in the SSL repository which will not copy semantic notifications when using "Copy instance" in the portal. This results in the SSL not being able to open if references to semantic notifications are made in one or more semantic execution packages. 21650: Integrate Existing Objects wizard Fixed an issue which caused the wizard to fail when the MDW used a case-sensitive collation. Fixed an issue where having multiple objects with the same name, but in different schemas would cause errors when running the wizard.  Fixed missing command timeout for the MDW when running queries.