Timextender Data Integration 26.3 is here, and it's a big one: full support for Fabric Warehouse and much improved support for Fabric Lakehouse as Prepare instance storage. In addition to that, we have a bunch of other improvements and fixes. The one you’ll notice first might the the smallest, though - we’ve aligned the versioning with the other Timextender products so this release is simply ‘26.3’ and not a four-digit number. A big thank you to everyone in our Early Access program who've surfaced a lot of the issues we've fixed in this release.We hope you’ll like the new release - dive into all the news below!New & ImprovedFull Support for Fabric Warehouse as Prepare Instance Storage (Public Preview)You can now use Microsoft Fabric Warehouse as Prepare instance storage, with feature support generally on par with SQL Server today. Warehouse is T-SQL based end to end, so it fits naturally into how Timextender already models, deploys, and scripts your Prepare layer. If you've been wanting to run Prepare on a T-SQL-based Fabric engine instead of learning Spark notebooks for Lakehouse, this release is for you.When we released support for Warehouse, it was limited to simple mode, but with this release, Warehouse is functionally equal with the other storage types, though still in Public Preview until we've confirmed it as production ready.Snowflake Hosted on Google Cloud PlatformSnowflake hosted on Google Cloud Platform is now supported as Prepare instance storage, alongside Snowflake on AWS and Azure. If your organization runs Snowflake on GCP - because that's where the rest of your cloud footprint lives, or simply where your team chose to host it - you can now point Prepare directly at it. There's nothing GCP-specific to configure or learn: Prepare treats it exactly like any other Snowflake account.Transforms for JSON and XML Data SourcesEnhanced JSON and XML data sources now have a built-in transform editor, so you can reshape a document into the tables you actually want before it lands in Ingest. Simple mode lets you pick a row path and drag fields out of the schema tree, SQLite mode lets you write SQL against the parsed document.Streaming for Large XML and JSON FilesLarge XML and JSON files are now processed as a stream instead of being loaded into memory in full. Memory use stays flat regardless of file size, so files that previously failed with an out-of-memory error during import now load.Full Load for Data-on-Demand SourcesYou can now trigger a full load on a data-on-demand data source. The flag is set per data source and carried end to end, from the step execution setup in Prepare through to the on-demand transfer in Ingest. Previously it was ignored on this path, so a full load quietly ran as an incremental one.The Metadata Manager Tells You What Actually ChangedWhen a source schema changes, the Metadata Manager now shows which fields changed, in the Edit dialog and in a tooltip on the warning triangle itself. It also tells you why the Edit button is disabled instead of leaving you to work it out.Smart Synchronization Now Treats Spaces and Underscores as EquivalentSmart sync now matches fields between Fabric Lakehouse on Ingest and Prepare even when one side uses underscores and the other uses spaces (for example, Company_Currency vs. Company Currency). Previously this mismatch meant smart sync couldn't match these fields automatically, forcing manual mapping for every affected column.Remap Source Data Warehouse in One GoA new Remap source Data Warehouse... command lets you point all cross-data-area mappings in a data warehouse at a different source Prepare instance in one operation. Right-click the data area and select Advanced → Remap source Data Warehouse..., pick the Prepare instance to remap to, and review the suggested table and field matches before applying the change.Manual Object Dependencies on Fabric LakehouseThe Object Dependencies feature - for manually documenting relationships Timextender can't infer automatically - is now supported on Prepare instances using Fabric Lakehouse storage.Cleanup Tool Now Removes Orphaned Fabric Lakehouse Temp FilesThe DW cleanup tool now finds and lets you remove orphaned temporary files left behind in Fabric Lakehouse by notebook executions - including execution artifacts from runs that failed partway through and stray leftover parquet files - the same way it already handles obsolete tables, views, and notebooks.Frozen Header Row in PerspectivesWhen you work with a long list of perspectives in Prepare and Deliver, the perspective name row now stays pinned in place as you scroll - just like freezing rows in Excel. Previously the names scrolled out of view, making it easy to lose track of which perspective you were editing."New" and Aligned Name and VersionAs you might have noticed, the naming of this release, "Timextender Data Integration 26.3", contains two changes from previous releases. We're now using the same version numbering format as the rest of the Timextender product line and the spelling of "Timextender" - with a lower case "x" - has been aligned with our updated branding.FixedFabric Lakehouse as Prepare Instance StorageFabric Lakehouse and Fabric Warehouse workspace names containing special characters (for example spaces or punctuation) could cause errors in Timextender Data Integration; those names now work correctly. Workspace names containing a forward slash (/) or backslash (\) are still not supported - this is a limitation in Fabric itself, not something this fix addresses. Merging a Fabric Lakehouse Prepare table across many source mappings scaled execution time with the number of sources instead of the data volume. Prepare tables with multiple source mappings now run as a single notebook execution per table instead of one per mapping, fixing the issue. Fixed an issue where executing a Fabric Lakehouse instance with many tables would fail once the generated notebook exceeded Fabric's 20 mb size limit. Business Central fields containing a forward slash in the name (e.g. "Country/Region Code") would come through correctly in Ingest but return NULL once processed in Prepare on Fabric Lakehouse. Lookups using NONE aggregation from the same source table could break the generated Fabric Lakehouse notebook with a code reference error. Fixed an error during incremental load with hard deletes enabled on Fabric Lakehouse when a Prepare table merges multiple source tables. A selection rule filtering on a column with special characters in its name would fail on execute. A custom transformation referencing a field with special characters in its name would fail on execute. A date table with a custom period would fail on execute due to a type mismatch between the generated notebook and the underlying parquet file. Running Data Profile on a table whose name contains special characters failed immediately instead of opening the dialog. Hash fields on a Prepare table would become null once a lookup was added to that table. Incremental load could fail with a KeyError when the incremental column was mapped from a system field. SQL snippet transformations applied to a Fabric Lakehouse table could fail deployment before it even started, even though the same logic worked as a custom value transformation. Opening a data area containing a field with the image datatype failed with an "Unsupported data type" error on Fabric Lakehouse. Remapping a table parameter in a notebook view (custom script) using "Set as..." generated an incorrectly formatted object name, breaking the mapping. The Query Tool didn't account for the _P suffix on persisted Lakehouse views, so running a generated query against one failed with "Invalid object name." Lookup transformation templates failed to deploy on Fabric Lakehouse with a null reference error. While still not supported on Fabric Lakehouse, the error is now handled. Enabling "Postfix valid tables with _v" on a Fabric Prepare instance broke direct data-area-to-data-area transfers with a "table not found" error. While still not supported on Fabric Lakehouse, the error is now handled. A boolean field with a fixed transformation could fail on Fabric Lakehouse when the source value was null, due to a data type mismatch in the generated expression. After pointing a Prepare or Ingest instance at a different Fabric workspace, generated notebook code kept referencing the old workspace name even after a full redeploy. Incremental load for the Dynamics 365 Finance & Operations connector failed in Fabric Lakehouse notebooks with an unresolved column error.Fabric Warehouse as Prepare Instance StorageHistory-enabled tables on Fabric Warehouse could fail on execution with a data type conversion error. Date tables on Fabric Warehouse generated using small batched insert statements instead of a single set-based insert, causing generation of a multi-year calendar to take significantly longer than on other storage types and dominate total refresh time on smaller Fabric capacities.Fabric Lakehouse as Ingest StoragePrepare read stale delta logs when queued immediately after Ingest, so a run could work from the table's previous state. Opening the Query Tool crashed DynamicProcessEngine_x64, which the client reported as "Service request failed: Buffer cannot be null". Outbound transfer threw a DirectoryNotFoundException when Handle Deletes was enabled, and did not use the primary key files to filter rows. Table paths for the Dynamics 365 Finance & Operations OneLake CDS source were built from workspace and lakehouse names rather than OneLake GUIDs, so they broke whenever either was renamed. Virtual sources reported an incremental state they could not honour, so Lakehouse incremental loads completed successfully having loaded zero rows. Generated notebooks are now written to a dedicated Timextender folder instead of the workspace root.Snowflake as Prepare Instance StorageFixed an issue on Snowflake where configured default column values were ignored, leaving nullable source values as NULL instead of applying the default. Aggregate table fields in Snowflake couldn't always be related to fields in a normal table, even with matching datatypes, due to a casing mismatch between the two. History-enabled tables in Snowflake could end up with multiple rows sharing the same DW_Id, and a deleted row could silently show another row's values instead of being marked as deleted.Snowflake Data SourcesSome dates were converted to values in the 1800s on the way into Prepare, and loading a NUMBER(38,0) column failed with a FormatException. Fetching views metadata over ODBC failed with "Column 'TABLE_SCHEMA' does not belong to table Views". The username was not quoted in SHOW GRANTS TO USER, so accounts whose names require quoting failed. Transient connection failures against Snowflake on AWS failed the execution outright; they are now retried.REST and Enhanced REST Data SourcesThe REST connector could return 401 for a correctly configured request that the API itself accepted, and failed against APIs requiring TLS 1.3. Type inference in the Enhanced REST connector cast numeric-looking string values to integers, so a field such as "0012" arrived as 12 and broke key matching. Enhanced REST could not use the SharePoint scope, and decimal type overrides were ignored in favour of the source's own type. Setting a debug log path on an Enhanced REST data source cleared the global database settings. Using dynamic values in the REST connector - query parameters populated from another endpoint's table - caused execution to fail with "Cannot add a SimpleContent column to a table containing element columns or nested relations" when the response contained nested elements, and produced no debug log output. Hardcoded parameters were unaffected. Cloning an NTLM REST connection did not carry the password, so the clone failed with 401 until it was retyped.JSON and XML Data SourceThe XML connector crashed with an INT64 overflow during Import Metadata on zero-padded numeric string identifiers. The XML connector grouped source tables by element name rather than by file, and promoted 1:1 nested elements into separate tables instead of inlining them. The Enhanced XML connector emitted duplicate columns per file when given a folder path, breaking creation of the raw table. XML table flattening failed on S3 ingest after the first XSLT, and the XML data source was missing from the ODX data source list. "Infer data types" on the JSON connector sized columns from the metadata file alone, causing truncation whenever real data exceeded the sample. JSON file aggregation named every table "Default". Execution hung for the enhanced JSON and XML connectors on SFTPS, and for the enhanced Parquet provider on FTPS/SFTP. The ODX XML and JSON connectors allowed several location settings to be edited when only one was in use.Business Central Data SourceIncremental load failed when the primary key columns were ordered differently on source and destination. Ingest from Business Central Online hung after a metadata change instead of picking up the new schema. The enhanced connector emitted a spurious "Selection rules are ignored on Option tables" warning for tables where the rules were in fact applied. An ADF copy failed with TypeConversionBooleanNotTreatedAsNumber when a Boolean Parquet column targeted a SQL tinyint, and the SQL Server Time type was converted to the wrong data type.File Data SourcesThe Enhanced CSV connector errored when set to include incomplete rows, and incremental load with "handle primary key updates and deletes" was broken for CSV on both SQL and Fabric storage. An empty path or / did not work at container root, and a SharePoint Excel source failed when its path was /. MySQL TIME columns failed during Parquet ingest, and previewing a Parquet source failed for tables containing datetimeoffset columns on Fabric storage. Writing Parquet files consumed more CPU than necessary.Qlik Cloud as Deliver endpointDeploying a Qlik Cloud endpoint to a shared space created the app there but placed its data connections in the requester's Personal space instead, preventing use of a Qlik Data Gateway configured on the shared space. Deploying a Qlik Cloud endpoint for the first time could fail when an app with the same name already existed in Qlik Cloud without a Timextender identifier.OtherIncremental load silently dropped rows whose incremental column was NULL. The Oracle ADF data source ignored the table and column selection and brought everything across. Opening an ODX ingest instance failed with an XML error, and editing and synchronizing a Timextender SQL Data Source 24.3.3.0 failed with "Error creating custom data source". Synchronization to Prepare failed outright if table information could not be read from a virtual source, rather than reporting that one source and continuing. A decimal-to-int conversion failed after migration, and the SQL Enhanced data source raised a null reference error in the Query Tool. Migrating a Deliver instance did not update table tooltips to reflect the correct source, which was confusing when reviewing the model afterward. Generate End-to-End Packages and Tasks ignored an execution package's Exclude Steps, and running it for a second execution package appended that package's tables to the first package's generated perspective instead of creating its own. Deploying an MDW data area could fail with a circular relation error when a custom post-deployment script added role members alongside a database role configured under Security. The Dynamic Variable Script Editor rendered with a broken layout.

Today, we've published a minor release of TimeXtender Classic (v. 26.2.1.3). It adds a small but handy usability improvement to Perspectives and fixes a few issues around authentication in the Timextender Enhanced Excel data source and the Business Central 365 data source adapter, as well as an rare issue with projects upgraded from 20.10 to Classic.New & ImprovedFrozen header row in PerspectivesWhen you work with a long list of perspectives in Prepare and Deliver, the perspective name row now stays pinned in place as you scroll - just like freezing rows in Excel. Previously the names scrolled out of view, making it easy to lose track of which perspective you were editing.FixedThe Enhanced Excel data source would fail connecting to SharePoint or OneDrive, returning a "Method not found" error tied to Azure authentication. The cause was a dependency issue that has now been fixed. When loading data from multiple tenants at the same time, the Business Central 365 adapter would sometimes mix up the client IDs and fail to authenticate. Concurrent loads across different tenants now reliably authenticate against the correct tenant. Projects upgraded from TimeXtender 20.10.x could crash TimeXtender Classic on open if they had performance recommendations saved for features than do not exist in Classic.

This release strengthens two parts of the TimeXtender AI offering: the MCP Server that securely connects TimeXtender to your data, and Xpilot Analytics, the conversational analytics experience built on top of it. The MCP Server work makes secure on-premise deployment work end-to-end and returns more trustworthy query results. The Xpilot Analytics work makes the chat experience accurate, readable, and correctly isolated per workspace. TimeXtender MCP ServerIn shortThis update makes secure (HTTPS) deployment work end-to-end, returns trustworthy query results, and keeps the service running through reboots. Previously, enabling HTTPS was blocked by a series of separate problems; an administrator can now stand the server up over HTTPS, on a standard port, with the cloud relay, and change or revert that setup later, entirely from the configurator without editing files by hand. Before and after Area Before In 2.0.1 Saving an HTTPS setup Saving an HTTPS configuration could leave the service unable to start, with a misleading "Service not found." The configuration saves correctly and the service starts; startup errors report the real cause. Running HTTPS as a service account The service crashed on secure startup with "Access denied" because the certificate was not reachable by the service account. HTTPS starts cleanly under a real service account. Using a standard port (443) Standard ports were rejected, so clean addresses like https://host/mcp were not possible. Standard-port HTTPS works, with no port number in the URL. HTTPS together with the cloud relay Enabling both caused every relayed request to fail ("no models available"). Secure HTTPS and the cloud relay work together. Changing HTTPS settings later Reopening the configurator on an HTTPS server blocked further edits without re-validating the certificate. A previously validated setup reopens ready to edit, so changes save without redoing validation. Reverting to HTTP There was no supported way to remove a certificate or switch back to HTTP from the interface. Switching back to HTTP cleanly removes the secure settings. Service recovery after a reboot After a reboot or OS update, the service stayed down until someone restarted it manually. The service starts itself after a reboot and recovers from an isolated startup failure on its own. Calculated measure results A calculated measure could draw from the wrong table and return incorrect numbers. Measures are scoped correctly and return trustworthy results, with clearer errors. Multi-field table relationships When tables were linked on more than one field, only the first was used, silently skewing totals and counts. Every field in the relationship is honored, so totals and counts match the source data. Names matching database keywords A field or metric named like a reserved database word made a query fail with a misleading "table does not exist" error. These everyday names now work normally. Record-count questions Legitimate "how many records" questions were sometimes blocked as a suspected security risk. These common questions return real answers. Failure reporting to applications Failed queries could be returned looking successful, so connected applications could not detect the failure. Failures are reported as errors, so connected applications detect and handle them reliably. Data model details The "Schema" field for each table was always blank. Returns a consistent, meaningful value. Installer package The installer included a number of obsolete and internal files. A leaner, more professional installed file set.  What this meansSecure deployment is realistic. On-premise HTTPS, standard ports, and the cloud relay work together, set up and maintained from the configurator without hand-editing files. Numbers you can trust. Calculated measures, multi-field relationships, and reserved-word names all return correct results. Honest failures. When a query fails, connected applications know it failed. Less downtime. The service recovers itself after a reboot or transient startup failure.To upgrade to MCP Server 2.0.1 you can download and run a new installer. Xpilot Analytics In shortThis update makes the Xpilot Analytics chat experience accurate, readable, and correctly isolated. The assistant now answers honestly when something cannot be resolved instead of quietly substituting a different answer, charts and tables present complete and correct data, the interface is polished (including dark mode), and a workspace-isolation gap is closed so a data source is only usable in the workspace it was assigned to. Before and after Area Before In 26.2.1 Honest answers when a query fails The assistant could quietly swap in a different column or count and present a real-looking result for a question the user never asked. The assistant surfaces the failure, offers alternatives, and does not present a substitute result until the user confirms. Correct first answer on a new chat The first question in a conversation often failed because the assistant guessed table and column names. The assistant checks the real data structure first, so the first question returns the correct answer. Tables and CSV exports For some data sources, table and CSV exports showed blank cells for totals and counts. Tables and CSV exports show complete, correct values. Charts that match what was asked The assistant offered visual changes the chart could not actually make, returning an unchanged chart with no explanation. The assistant only offers visual options the charts can deliver, and says so when one is not supported. Readable chart labels Charts combining two values showed unreadable shorthand like "1(1)" or "5(2)". Labels are shown in full, with a dedicated grouped bar chart for two-dimensional data. KPI cards Large values overflowed the card, a stray line appeared under the number, and labels were forced into ALL CAPS. Large numbers are abbreviated cleanly (e.g. 27.2M, 1.4B), the stray line is gone, and labels keep their original capitalization. Code blocks in dark mode Code shown in chat was nearly invisible against the dark background. Code has proper contrast and is clearly legible in dark mode. New data models appearing A newly added data model stayed invisible in existing conversations until a brand-new chat was started. Opening or refreshing an existing conversation picks up newly added models. Conversation history (data source) Past conversations showed "Unavailable" instead of the data source they used. Each past conversation shows the data source it actually used, including ones since removed. Refining a chart Refining a chart felt like a reply to a separate question, and it was unclear whether the chart had changed. Refinements are treated as edits to the chart in view, with a clear signal that it was updated. Clarity while the assistant works The progress panel showed a long, technical tool description on every step. The panel shows short, friendly action labels such as "Querying the semantic model." Workspace isolation of data sources A data source not assigned to a workspace could still appear and be used in that workspace's chat. A data source is only visible and usable in the workspace it was assigned to. What this meansAnswers you can trust. The assistant no longer answers a slightly different question without making that clear, and it asks for direction when something cannot be resolved. A polished, complete experience. Charts, tables, KPI cards, dark mode, and conversation history all present correct, readable information. Tighter isolation. A data source is confined to the workspace it was assigned to, closing a cross-workspace exposure gap.If your service is on version 26.2 you already have access to these new features.

Today, we've published a minor release of TimeXtender Data Integration (v. 7387.1) that includes two fixes, one for an Execution Service startup issue introduced in 7376.1 and one for Snowflake deployments using history.We recommend that you install this hotfix if you’re using the Execution Service or if you’re using history on Prepare tables on Snowflake storage. There are no changes to the Ingest Service and it remains at version 7376.1.FixedAfter upgrading to 7376.1, the Execution Service could fail to start with a Windows service error (‘Error 1067: The process terminated unexpectedly’). The cause was a token refresh issue that has been resolved. Deploying a table with history enabled to a Prepare instance on Snowflake instance would fail during the raw table structure step. This affected tables using SCD Type I regardless of column types or hashing algorithm configuration.

The summer release of TimeXtender Classic (v. 26.2.1.1) brings a refreshed look, a few usability improvements and a set of bug fixes.New & ImprovedRefreshed TimeXtender brandingTimeXtender has a new look, and Classic now reflects it. The Classic application has been updated with the new logo, a refreshed orange accent color, a new application icon, and new graphics. You'll notice the changes as soon as you open Classic after upgrading.Larger default window sizesA number of commonly used windows in Classic were too small out of the box, requiring you to manually resize them every time. We've increased the default size of the script editor, Execution Log Overview, Preview, Query Tool, Add/Edit Custom Measure, Add/Edit Custom Field, and Add/Edit Execution Package windows.Maximize button in custom script windows in Semantic modelsWindows where you enter custom scripts, such as Custom Measures and Custom Fields, in the Semantic layer now have a maximize button. This makes it easier to work with longer scripts without being cramped for space.FixedWhen upgrading from TimeXtender 20.10 to Classic, conditional lookup operators configured as SUM or MAX were incorrectly changed to TOP, producing wrong query results. In workspaces with many lookups, this was impractical to correct manually. Lookup operators are now preserved correctly during upgrade. Fixed a race condition ‘ExecutionEngine_x64.exe’ that would sometime cause the application to never exit, but stay around consuming memory. In the Options dialog, the "Look for activation file in" field now defaults to the user's Downloads folder, and a Browse button has been added to make it easier to locate the activation file.

Our second major TDI release of the year - that we initially published right in time for Xtend 2026 -  is now out of preview and generally available. Compared to the preview release, this most visible change in this one is the fresh coat of paint to align with the refreshed TimeXtender brand, but we’ve also made a handful of fixes under the hood. The headline features stay the same: Microsoft Fabric Warehouse joins the Prepare storage lineup as a Public Preview, our MCP server now allows you to access all your data on any storage through just one connection, and the file-based connectors have been rebuilt around a streaming architecture so multi-gigabyte ingests no longer blow past memory. This is just some of the exciting news in this release - dive in below! New & ImprovedFabric Warehouse as Prepare Instance Storage (Public Preview)You can now use Fabric Warehouse as Prepare instance storage, a perfect pairing with Ingest instances using Fabric Lakehouse storage. We've stamped this initial release a Public Preview as it ships with features on the simple mode level. In addtion to that, it only works with Ingest instances on Fabric Lakehouse storage in the same Fabric Warehouse.Cloud-Connected MCP Server, now with Snowflake (Public Preview)On-prem MCP servers can now register with TimeXtender Data Platform and expose secure endpoints to cloud-hosted AI tools without inbound firewall changes. The Configurator has a "TimeXtender Cloud" tab for one-click sign-in, registration, and unregistration; TDP gains a Settings page to manage registered servers and assign them to workspaces. Under the hood, an outbound SignalR relay handles the routing, so your data and credentials never leave your environment.Snowflake also joins SQL Server and Fabric as a supported database in the MCP Configurator.Streaming for Large File Data SourcesLoading large files used to mean memory crashes, multi-hour runs or splitting files just to get them through. We've reworked how our file connectors handle data, so size is no longer the blocker it used to be. Parquet files in the tens of gigabytes now load in a fraction of the time, what previously took most of the day can finish in under an hour. CSV files at multi-gigabyte scale load reliably, without the out-of-memory errors that used to stop them. XML and JSON files load steadily regardless of size, so large exports and daily file drops no longer prolong your runs. If you've been splitting files or scheduling around these limits, you can stop.Full View functionality on Fabric Lakehouse through Persisted ("Materialized") ViewsOur persisted views feature is now supported on Prepare instances using Fabric Lakehouse storage. The feature, also known by its Fabric-native "materialized views" name, allows you to reuse computed results for a performance benefit. More importantly, however, persisted views do not have the same limitations as regular views on Lakehouse storage. They can be used just like you use views in Prepare instances on SQL storage, e.g., in table inserts. This is enabled by the fact that persisted views are stored as delta parquet files in the workspace, while regular views are only available through the SQL endpoint.Direct Configuration in Metadata ManagerSetting up a data source just got faster. You can now override auto-detected data types directly in the Metadata Manager, no more XSLT workarounds. Marking primary keys is now a checkbox in the same view, so you can review fields and configure keys side by side. And once you've configured one source, you can export those settings and import them into another source of the same type, instead of redoing the work each time.Keep your Workspace Tidy with the Storage Cleanup Tool for Fabric LakehouseThe storage clean-up tool now supports Fabric Lakehouse and helps you remove outdated TimeXtender-generated files from your Lakehouse so you can stear clear of the Fabric warehouse item limit. As a further improvement to keeping your workspaces tidy, TimeXtender notebooks are now stored in a dedicated 'TimeXtender' workspace folder per default.Snowflake on AWS as Instance StorageSnowflake on AWS is now a supported Ingest and Prepare instance storage option, alongside Snowflake on Azure. If your Snowflake account runs on AWS, you can keep your data in-region instead of crossing clouds.Object-Level Security for Snowflake PreparePrepare instances on Snowflake storage now support roles and table-level access, closing the last significant feature-parity gap with SQL Server. Define security roles, assign access rights to specific tables, and let Snowflake enforce them.Qlik Cloud Spaces DeploymentDeploy directly to Qlik Cloud Shared Spaces from TDI. Pick the target space on the connection in the Portal, and apps land in the right space without manual moves. In addition to that, we've added a few other fixes. The Qlik application dropdown is now sorted alphabetically, and "Deploy to text file" settings are no longer shown when the target is Qlik Cloud, where they don't apply.Hardened MongoDB Enhanced ProviderWe've cleaned up several long-standing issues with the MongoDB Enhanced Provider. The _id field is now correctly recognized as the primary key on every load, and tables containing Decimal128 or BigInt values import cleanly instead of breaking the transfer on edge-case values.Hardened MySQL Enhanced ProviderThe MySQL Enhanced Provider has had a similar pass. SSL/TLS connections now work end-to-end, including against MariaDB with Verify CA and Verify Full modes. Query Table metadata now identifies .NET types correctly, removing a class of warnings during sync. And tables with LONGTEXT columns no longer fail with an Int32 overflow - they import like any other text column.Larger Default Window Sizes for Tasks that Require Extra SpaceA handful of windows in the application have "grown up" to open in a larger default size. This includes the default scripting editor used for custom views, stored procedures, etc., Execution Log Overview, Preview, Query Tool, Add/Edit Custom Measure, Add/Edit Custom Field, and Add/Edit Execution Package. In addition to that, the Custom Measure and Custom Field windows now have a maximize button. We how these small changes will save you a few resizes a day.FixedFabric Lakehouse as Prepare Instance Storage Conditional lookups would fail if it used object names with spaces. Data type casting in lookups handles all supported types correctly. Lookups against tables with duplicate rows no longer raise primary key violations. Transformations that reference fields with their own transformations now resolve correctly. Concurrent Prepare transfers from an Ingest Lakehouse no longer collide. Default table column value transformations did not work. The 'Source Table' column in tables with mapping sets would show "." instead of the actual table name. Building the object cache required more API calls than necessary, leading to slower performance. Notebook views were not included in data lineage for Fabric Lakehouse SQL Custom scripts were not marked as unsupported when switching from SQL to Fabric Lakehouse storage Data Sources & Ingest Business Central ingests no longer produce duplicated fields in the Dimension Set Entry table. Business Central token-handling overhead has been removed, improving throughput. Business Central tables with 100+ fields no longer error during ingest. SQL Data Source connections to Synapse Dedicated Pool succeed reliably. The AX adapter no longer drops accounts in the 010/030 range due to filter logic. Enhanced CSV no longer fails when a row is incomplete. Azure Blob ingest handles empty and root paths correctly. Parquet handling is corrected for special decimal and double cases. Preview Table works on Enhanced Data Sources. Provider v24 test connections succeed after upgrade. Data source auto-update settings persist as configured. Ingest instances no longer time out when connecting to data sources. Business Central Online ingests no longer hang after metadata changes on the source. The JSON & XML connector no longer fails on aggregated JSON transfers. Parquet preview now works for Ingest instances using Fabric storage. Snowflake as Instance Storage Incremental load from Ingest storage didn't work for tables with mapping sets. Columns with the 'Number(38,0)' data type no longer trigger format exceptions when loading data from a data source into Ingest storage. Qlik Cloud Deliver Endpoint Taking ownership of an existing Qlik Cloud app would fail which prevented visuals, bookmarks, master measures, and additional scripts from being retained when migrating from older versions. Qlik Cloud endpoints now respect the configured QVD folder instead of writing to a default location. Other Incremental loads correctly process primary key updates and deletes. Incremental subtraction supports decimal types. Deleting large data areas from a Prepare instance would crash the desktop application or cause it to hang. This is now handled properly with a loading window showing the progress. In the Execution Service Configuration tool, it was possible to accidentally signed out, and the Sign-In page would throw an unhandled exception when clicking Next without signing in. Vulnerabilities in XBI Server have been patched. Improved the Object Dependencies window with a more consistent layout and fixed some rendering issues. Fixed an issue blocking the creation of a meta collection data source in the Portal.

TimeXtender Data PlatformTimeXtender Turnkey has been renamed to TimeXtender Data Platform TimeXtender Data Platform is now highlighted as the primary product on the authentication and product landing page. Updated brand logo, favicon, color palette, and product icons are now applied across TDP The workspace switcher has been reworked to be easier to use and less in your way. An emoji and symbol picker is available when creating or editing workspaces — workspaces can now have a custom icon. Recent Executions grid on the Dashboard page gives you an at-a-glance view of what has run recently across your workspace, including status and timing, without navigating to the full Executions page. A Data Integration link has been added to the navigation bar for quick access. Grid performance is significantly improved for large datasets Initial load time of the TDP web application has been reduced  DownloadsA new dedicated Downloads page lists all installable components — Ingest Service, TDI, MCP Server, ODQ Desktop, Gateway, and more — in one place  Process MapsTask status icons on the process map now update live during execution — no refresh needed The Process Maps list view now shows execution status and last updated time instead of metadata columns Process Map detail page status area has been cleaned up A warning is shown when deleting a workspace that has associated Process Maps  Dataset Health & Quality Score Get a clearer, time-series view of each dataset's quality and health.A health score is calculated per dataset from rule pass/fail ratios across executions Trend indicators show whether health is improving or declining between executions Record counts are tracked per execution and displayed in the grid, with trend arrows for changes over time The Last Updated column replaces Last Modified for a more meaningful time reference Rule exception counts are now stored per execution, enabling historical trackingExecution OverviewThe Executions page has been significantly expanded. Instead of showing only currently running tasks, it now includes all tasks in the workspace.Duration column shows how long each execution took State column with visual icons matching the process map representation Environment dropdown to switch between Production, Development, and Test views All task types are now included — not just a subset Concurrent task executions are handled correctly Default sorting is by state for a more useful initial view  User Privileges and RolesTimeXtender Data Platform now ships with a complete role-based access control system. You can manage users and roles directly in TDP — no desktop client required.A Roles tab in Settings lets you create, edit, and delete roles with fine-grained privilege assignments A Users tab lets you view, add, and manage users alongside their assigned roles Microsoft Entra ID Groups can be linked to roles — everyone in the group automatically inherits the associated privileges Privileges are inherited from all Entra groups a user belongs to, so access is always consistent Default roles are created automatically when a new workspace is provisioned SSO users are provisioned automatically on first login — no manual setup needed Workspace Contributors and Administrators can manage Data Providers without requiring full global admin rights  Public API & API KeysTimeXtender Data Platform can now be accessed programmatically via a public REST API secured with API keys.Create and revoke personal API keys from User Preferences Workspace admins and owners can view and revoke any user's API keys Public Orchestration API v0 — execute process maps and trigger orchestration runs programmatically. Query for logs.  Data Enrichment in TDPThe Data Enrichment portal is now embedded directly in TDP, giving you a unified experience without switching tools or signing in separately.The DE portal is embedded within the TDP navigation Workspace isolation is enforced — Data Providers assigned to specific workspaces are only visible there Authentication is shared between TDP and Data Enrichment — you are signed in automatically To set it up, make sure you have a Data Enrichment data provider in settings with the “Enabled in Navigation” turned on.And much moreTDI Environment-Aware SynchronizationTDI (TimeXtender Data Integration) Data Providers now support environment-aware configuration, making it easier to manage multiple TDI instances across Production, Development, and Test.TDP can now fetch the list of TDI instances from the connected TDI service An environment mapping UI lets you map each TDI instance to a specific environment in the Data Provider editor TDI packages are deduplicated by GUID during sync to prevent duplicate entries in the process map The fetch instances table is also available in the ODQ Desktop  Data Enrichment — Access Filter OverhaulA series of long-standing bugs in the Access Filter feature have been resolved.SQL subquery access filters no longer cause all editable cells to show "Validation failed due to filter error" Function-based access filters no longer trigger the same false error Unbracketed column names in access filters no longer cause incorrect errors An access filter on a read-only column no longer prevents edits to other columns An access filter on an invisible column no longer prevents edits to other columns Importing or pasting valid values into access-filtered columns is no longer incorrectly rejected Validation behavior is now consistent between the Web and Desktop clients Fixed issues saving user access in the DE Desktop  Data Enrichment — Hyperlinks in DescriptionsMarkdown-style hyperlinks ([text](url)) in description fields are now rendered as clickable links in the Web client HTML anchor tags in descriptions are also supported for backward compatibility  Fixed Data TransferFixed Data Transfer failing when "No Column Mapping" was selected  Fixed a System.Memory version mismatch that caused Data Transfer to fail Fixed merge failures on columns with no mapping Added the ability to view the create table script for merge operations in Data Transfers  Fixed duplicated PowerBI refresh tasks that could not be openedAuthentication & SSOMicrosoft Entra ID Groups SSO is now supported for Data Enrichment, Orchestration, and Data Quality  Fixed orchestration portal access failing after a user was re-added Notifications & EmailFixed an invalid default email template causing TDP pages to crash  Fixed the link in test notification emails not working correctly   PlatformFixed an intermittent TripleDES/AES fallback issue causing the gateway to fail to decrypt queue data in rare occasions Fixed a locale-specific number formatting bug that corrupted MinValue/MaxValue constraints in the table designer  On-premisesMachine-specific configuration is now separated from application configuration so it is not overwritten during upgrade reducing risk of failed upgrades of TimeXtender ODQ Gateway and Execution Connections

Right in time for Xtend 2026, we're ready with a public preview of our second major release of the year.Microsoft Fabric Warehouse joins the Prepare storage lineup as a Public Preview, our MCP server now allows you to access all your data on any storage through just one connection, and the file-based connectors have been rebuilt around a streaming architecture so multi-gigabyte ingests no longer blow past memory.This is just some of the exciting news in this release - dive in below! This release is a Public Preview. This means that it is available for all partners and customers to try, but it is still being stabilized for general availability (“GA”). We encourage you to use it in sandbox and development environments, not production. The issues found in the Public Preview will be fixed in the upcoming GA release or a later release, depending on the priority. We will not issue hotfixes for a release in Public Preview.We’ve not replaced the download links for the current production version - use these links below to download the preview release:TimeXtender Data Integration 7361.1 TimeXtender Ingest Service 7361.1 New & ImprovedFabric Warehouse as Prepare Instance Storage (Public Preview)You can now use Fabric Warehouse as Prepare instance storage, a perfect pairing with Ingest instances using Fabric Lakehouse storage. We've stamped this initial release a Public Preview as it ships with features on the simple mode level. In addtion to that, it only works with Ingest instances on Fabric Lakehouse storage in the same Fabric Warehouse.Cloud-Connected MCP Server, now with Snowflake (Public Preview)On-prem MCP servers can now register with TimeXtender Data Platform and expose secure endpoints to cloud-hosted AI tools without inbound firewall changes. The Configurator has a "TimeXtender Cloud" tab for one-click sign-in, registration, and unregistration; TDP gains a Settings page to manage registered servers and assign them to workspaces. Under the hood, an outbound SignalR relay handles the routing, so your data and credentials never leave your environment.Snowflake also joins SQL Server and Fabric as a supported database in the MCP Configurator.Full View functionality on Fabric Lakehouse through Persisted ("Materialized") ViewsOur persisted views feature is now supported on Prepare instances using Fabric Lakehouse storage. The feature, also known by its Fabric-native "materialized views" name, allows you to reuse computed results for a performance benefit. More importantly, however, persisted views do not have the same limitations as regular views on Lakehouse storage. They can be used just like you use views in Prepare instances on SQL storage, e.g., in table inserts. This is enabled by the fact that persisted views are stored as delta parquet files in the workspace, while regular views are only available through the SQL endpoint.Streaming for Large File Data SourcesLoading large files used to mean memory crashes, multi-hour runs or splitting files just to get them through. We've reworked how our file connectors handle data, so size is no longer the blocker it used to be. Parquet files in the tens of gigabytes now load in a fraction of the time, what previously took most of the day can finish in under an hour. CSV files at multi-gigabyte scale load reliably, without the out-of-memory errors that used to stop them. XML and JSON files load steadily regardless of size, so large exports and daily file drops no longer prolong your runs. If you've been splitting files or scheduling around these limits, you can stop.Direct Configuration in Metadata ManagerSetting up a data source just got faster. You can now override auto-detected data types directly in the Metadata Manager, no more XSLT workarounds. Marking primary keys is now a checkbox in the same view, so you can review fields and configure keys side by side. And once you've configured one source, you can export those settings and import them into another source of the same type, instead of redoing the work each time.Keep your Workspace Tidy with the Storage Cleanup Tool for Fabric LakehouseThe storage clean-up tool now supports Fabric Lakehouse and helps you remove outdated TimeXtender-generated files from your Lakehouse so you can stear clear of the Fabric warehouse item limit. As a further improvement to keeping your workspaces tidy, TimeXtender notebooks are now stored in a dedicated 'TimeXtender' workspace folder per default.Snowflake on AWS as Instance StorageSnowflake on AWS is now a supported Ingest and Prepare instance storage option, alongside Snowflake on Azure. If your Snowflake account runs on AWS, you can keep your data in-region instead of crossing clouds.Object-Level Security for Snowflake PreparePrepare instances on Snowflake storage now support roles and table-level access, closing the last significant feature-parity gap with SQL Server. Define security roles, assign access rights to specific tables, and let Snowflake enforce them.Qlik Cloud Spaces DeploymentDeploy directly to Qlik Cloud Shared Spaces from TDI. Pick the target space on the connection in the Portal, and apps land in the right space without manual moves. In addition to that, we've added a few other fixes. The Qlik application dropdown is now sorted alphabetically, and "Deploy to text file" settings are no longer shown when the target is Qlik Cloud, where they don't apply.Hardened MongoDB Enhanced ProviderWe've cleaned up several long-standing issues with the MongoDB Enhanced Provider. The _id field is now correctly recognized as the primary key on every load, and tables containing Decimal128 or BigInt values import cleanly instead of breaking the transfer on edge-case values.Hardened MySQL Enhanced ProviderThe MySQL Enhanced Provider has had a similar pass. SSL/TLS connections now work end-to-end, including against MariaDB with Verify CA and Verify Full modes. Query Table metadata now identifies .NET types correctly, removing a class of warnings during sync. And tables with LONGTEXT columns no longer fail with an Int32 overflow - they import like any other text column.Larger Default Window Sizes for Tasks that Require Extra SpaceA handful of windows in the application have "grown up" to open in a larger default size. This includes the default scripting editor used for custom views, stored procedures, etc., Execution Log Overview, Preview, Query Tool, Add/Edit Custom Measure, Add/Edit Custom Field, and Add/Edit Execution Package. In addition to that, the Custom Measure and Custom Field windows now have a maximize button. We how these small changes will save you a few resizes a day.FixedFabric Lakehouse as Prepare Instance Storage Conditional lookups would fail if it used object names with spaces. Data type casting in lookups handles all supported types correctly. Lookups against tables with duplicate rows no longer raise primary key violations. Transformations that reference fields with their own transformations now resolve correctly. Concurrent Prepare transfers from an Ingest Lakehouse no longer collide. Default table column value transformations did not work. The 'Source Table' column in tables with mapping sets would show "." instead of the actual table name. Building the object cache required more API calls than necessary, leading to slower performance. Notebook views were not included in data lineage for Fabric Lakehouse SQL Custom scripts were not marked as unsupported when switching from SQL to Fabric Lakehouse storage Data Sources & Ingest Business Central ingests no longer produce duplicated fields in the Dimension Set Entry table. Business Central token-handling overhead has been removed, improving throughput. Business Central tables with 100+ fields no longer error during ingest. SQL Data Source connections to Synapse Dedicated Pool succeed reliably. The AX adapter no longer drops accounts in the 010/030 range due to filter logic. Enhanced CSV no longer fails when a row is incomplete. Azure Blob ingest handles empty and root paths correctly. Parquet handling is corrected for special decimal and double cases. Preview Table works on Enhanced Data Sources. Provider v24 test connections succeed after upgrade. Data source auto-update settings persist as configured. Ingest instances no longer time out when connecting to data sources. Business Central Online ingests no longer hang after metadata changes on the source. The JSON & XML connector no longer fails on aggregated JSON transfers. Parquet preview now works for Ingest instances using Fabric storage. Snowflake as Instance Storage Incremental load from Ingest storage didn't work for tables with mapping sets. Columns with the 'Number(38,0)' data type no longer trigger format exceptions when loading data from a data source into Ingest storage. Qlik Cloud Deliver Endpoint Taking ownership of an existing Qlik Cloud app would fail which prevented visuals, bookmarks, master measures, and additional scripts from being retained when migrating from older versions. Qlik Cloud endpoints now respect the configured QVD folder instead of writing to a default location. Other Incremental loads correctly process primary key updates and deletes. Incremental subtraction supports decimal types. Deleting large data areas from a Prepare instance would crash the desktop application or cause it to hang. This is now handled properly with a loading window showing the progress. In the Execution Service Configuration tool, it was possible to accidentally signed out, and the Sign-In page would throw an unhandled exception when clicking Next without signing in. Vulnerabilities in XBI Server have been patched. Improved the Object Dependencies window with a more consistent layout and fixed some rendering issues.

Today, we’ve released updated data source providers. See the changes below.Dynamics 365 Business Central (SQL / Navision Option Values)Version: 24.2.0.0 (TDI) / 24.6.1.0 (TDI SQL) / 24.4.1.0 (TDI Navision)Time-type column conversion now produces the correct data type. Account filtering: trim whitespace, drop empty entries, case-insensitive comparison, and accounts can now be matched by ID or Name. Bumped Jet NavMetadataPlugin DLLs to v1.25.10.2792Dynamics 365 Business Central (Online / Option Values)Version: 24.4.1.0 (TDI Online) / 24.2.0.0 (TDI Option Values)Fixed issue with 'Selection rule' warning being emitted too often, it is now only logged when there is actually a selection rule defined on an option table. Account filtering: trim whitespace, drop empty entries, case-insensitive comparison, and accounts can now be matched by ID or Name. Bumped Jet NavMetadataPlugin DLLs to v1.25.10.2792Dynamics 365 Finance & Operations (SQL)Version: 24.3.0.0 (TDI)Changed account filtering, it now trims whitespace and removes empty entries;  is case-insensitive; FNO SQL also matches accounts by ID in addition to Name.CSVVersion: 24.5.5.0 (TDI) / 1.10.2 (20.10 BU) / 16.4.25.0 (20.10 ODX)Added streaming support for large CSV files. Fixed an issue when 'Ignore incomplete rows' is false, rows with missing columns now ingest with NULL for missing fields and emit a warning, instead of throwing an error. Fixed issue with static columns Preview Table so that the data shows correctly. Fixed issue in BU so that scheduling no longer gets stuck on SFTP/FTPS source.ExcelVersion: 24.4.2.0 (TDI) / 1.10.2 (20.10 BU) / 16.4.23.0 (20.10 ODX)Fixed issue with static columns Preview Table so that the data shows correctly. Fixed issue in BU so that scheduling no longer gets stuck on SFTP/FTPS source.MongoDBVersion: 1.2.6 (20.10 BU)Removed LDAP authentication (deprecated). Password field is now consistently available for SCRAM-based authentication. Fixed issue with static columns Preview Table so that the data shows correctly.MySQLVersion: 1.3.2 (20.10 BU)Fixed issue with static columns Preview Table so that the data shows correctly.SQLVersion: 24.2.3.0 (TDI) / 18.1.1.0 (TDI ADF) / 16.4.3.0 (20.10 ODX) / 10.4.4.0 (ODX ADF)Changed ‘float’ data type to map to .NET double instead of float in order to avoid loss of information.Sun SystemsVersion: 24.1.0.0 (TDI) Changed ‘float’ data type to map to .NET double instead of float in order to avoid loss of information.ODATAVersion: 1.4.2 (20.10 BU)Fixed issue with static columns Preview Table so that the data shows correctly.OracleVersion: 1.2.0 (20.10 BU) /10.4.7.0 (ODX ADF)Added filtering to meta tables in the Oracle ADF (Azure Data Factory). Improved oracle meta data extraction query.ParquetVersion: 24.4.1.0 (TDI) / 1.8.1 (20.10 BU) / 16.4.16.0 (20.10 ODX)Added support for incremental load (TDI only). Added support for streaming large files. Fixed issue with special float values (NaN, +Inf, -Inf), they now map to NULL. Fixed issue with static columns Preview Table so that the data shows correctly. Fixed issue in BU so that scheduling no longer gets stuck on SFTP/FTPS source.Delta Parquet (OneLake)Version: 24.1.0.0 (TDI)Fixed issue with test connection.RESTVersion: 1.10.2 (20.10 BU)Fixed issue with static columns Preview Table so that the data shows correctly.SalesforceVersion: 1.0.1 (20.10 BU)Fixed issue with static columns Preview Table so that the data shows correctly.XML/JSONVersion: 24.4.1.0 (TDI) / 1.9.3 (20.10 BU) / 16.4.19.0 (20.10 ODX)Added support for incremental load (TDI only). Fixed issue with table flattening where it used incorrect name when no name was specified (BU and ODX). Fixed issue with table flattening being skipped when there was more than one flattening for some cloud based locations. Fixed issue with static columns Preview Table so that the data shows correctly. Fixed issue in BU so that scheduling no longer gets stuck on SFTP/FTPS source. 

Today, we’ve published a minor release of the TimeXtender Data Integration Ingest Service (v. 7313.1) with a fix that ensures that we support Spark Runtime 1.3 on Fabric Lakehouse as Microsoft is ending support for Spark Runtime 1.2.We recommend that you install this hotfix if you're using, or want to use, Fabric Lakehouse as your Ingest storage.FixedTimestamp columns transferred into Ingest storage on Fabric Lakehouse are now correctly preserved as Int96 when switching workspace to Spark Runtime 1.3.

Today, we’ve published a minor release of the TimeXtender Data Integration Ingest Service (v. 7312.1) that makes it possible to download CData data source providers again. Previously, you could only use the CData providers already installed on you machine.We recommend that you install this hotfix if you're using, or want to use, CData data source providers.Note: CData providers are made available as a paid add-on.FixedDownload of CData data source providers has been re-enabled.

Today, we’ve published a minor release of TimeXtender Data Integration (v. 7303.1) that includes a fix for an issue with incremental load and mapping sets as well as a handful of fixes for Fabric Lakehouse as instance storage. We recommend that you install this hotfix if you're affected by the issues we’ve fixed.FixedAfter upgrading to 7257.1, tables with incremental load configured in Ingest that was brough into Prepare though a mapping set were ignoring their incremental rules and running full loads on every execution. In Ingest instances on Lakehouse storage, if running with a user account that lacked access to certain objects, the entire table listing operation would fail. In Ingest instances on Lakehouse storage, no table is created when the table in the data source is empty. This would cause a “path not found” error when copying data to Prepare since the logic expected a table to be present even if there was no data. In Prepare instances on Lakehouse storage with multiple data areas, tables were generated with DW_Id = NULL and DW_Batch was not using the right value. Both values are now populated correctly. In Prepare instances on Lakehouse storage, the value of the Source Table column was incorrect for unmapped tables. In Prepare instances on Lakehouse storage, selection rules were not being respected during execution on aggregate tables and table inserts. In Prepare instances on Lakehouse storage, conditional lookup fields with spaces in their names would cause errors during execution. In Prepare instances on Lakehouse storage, an error would occur when creating supernatural keys in certain configurations. In Prepare instances on Lakehouse storage, failed executions in the execution queue were displayed as successful. In Prepare instances on Lakehouse storage, failed tasks were not listed in red in the Execution window, making failures harder to spot.

We're excited to announce the release of TimeXtender Classic 26.1 to carry on the legacy of on-prem TimeXtender all the way back to the first version in 2006. While TimeXtender 20.10 has been referred to as "Classic", this release marks the official debut of TimeXtender Classic as an equal sibling to TimeXtender Data Integration in the TimeXtender landscape.TimeXtender Classic has a focus on on-prem solutions based on Microsoft SQL, while TimeXtender Data Integration is built to take full advantage of cloud-based infrastructure such as Microsoft Fabric, Azure Data Lake, and Snowflake.If you're currently using TimeXtender 20.10, you should plan to upgrade to TimeXtender Classic or migrate to TimeXtender Data Integration. For more information on the process and timeline, see Important information regarding TimeXtender 20.10, TimeXtender Data Integration), and TimeXtender Classic.Compared to TimeXtender 20.10, the main changes in TimeXtender Classic are as follows:The ODX has been removed in favor of the business unit. The deployment target setting 'SQL Data Warehouse' has been removed. As a result of the focus on on-prem solutions, TimeXtender Classic does not support SQL Data Warehouse (currently known as Dedicated SQL Pool). Qlik Models and the Qlik Sense Server have been removed. All previously deprecated features have been removed, including 'Split' and 'Concatenation' field mappings, time table, data aggregations, mapping tables on the business unit, hash key options in the table, target-based incremental load, and some settings on conditional lookup fields. We've refreshed the design of the main UI with refined theme colors and a less prominent accent color. We've implemented a new activation flow to ensure that you're always up to date on important changes. The gist of it is that Classic must be activated using an activation file every six months. When you download the file from the Portal, you can review important announcements about the product. We’ve implemented support for SQL Server 2025.For more detailed information about the changes and the upgrade process, see Upgrade from TimeXtender 20.10 to TimeXtender Classic.Get ClassicClick here to download TimeXtender Classic

Today, we’ve released updated data source providers. See the changes below.MongoDbVersion: 24.7.0.0 (TDI) / 1.2.4 (20.10 BU) / 16.4.7.0 (20.10 ODX)Added PK detection. Added support for running on Snowflake Ingest. Fixed an issue with data loading where data would not appear or was in the wrong column.MySQLVersion: 24.2.4.0 (TDI) / 1.3.1 (20.10 BU) / 16.4.4.0 (20.10 ODX)Added support for SSL/TLS connections. Updated MySQL query table data type handling and selection state. Fixed an issue with longtext columns from MySQL that would overflow. 

Today, we’ve released updated data source providers. See the changes below.MySQLVersion: 24.2.4.0 (TDI) / 1.3.1 (20.10 BU) / 16.4.4.0 (20.10 ODX)Added support for SSL/TLS connections. Updated MySQL query table data type handling and selection state. Fixed an issue with longtext columns from MySQL that would overflow.MongoDbVersion: 24.7.0.0 (TDI) / 1.2.4 (20.10 BU) / 16.4.7.0 (20.10 ODX)Added PK detection. Added support for running on Snowflake Ingest. Fixed an issue with data loading where data would not appear or was in the wrong column.

Today, we’ve published a minor release of TimeXtender Data Integration. We recommend that you upgrade if you’re affected by the issue - see guidance below.FixedWhen opening a Prepare instance on SQL storage in TDI v. 7257.1, any custom hash fields, supernatural keys, key stores, etc., with the hashing algorithm set to instance default would have it explicitly set to the application default, ‘SHA-1, SQL Server 2005+’. If the instance default was not set to ‘SHA-1, SQL Server 2005+’., this would cause the objects to be marked for redeployment.Upgrade advisoryWhether or not you can skip this release depends on what storage platform you’re using and what default hashing algorithm you’ve set for your Prepare instances. This option is found in the Edit Instance window as Hashing algorithm:You should upgrade if:You’re using another default hashing algorithm than ‘SHA-1, SQL Server 2005+’.You can skip this release if:You’re using Snowflake or Fabric Lakehouse as Prepare storage. You’re using the application default hashing algorithm ‘SHA-1, SQL Server 2005+’ as your instance default, and are not planning to change that. You are using another default hashing algorithm, but have already - or don’t mind to - redeploy your objects using the ‘SHA-1, SQL Server 2005+’ algorithm.Resetting the hashing algorithm to avoid redeploymentAfter upgrading to TDI v. 7278.1, you can reset the hashing algorithm setting on the affected object so that the application will no longer see them as needing redeployment.The procedure below is useful if the majority of your hashed objects do not use ‘SHA-1, SQL Server 2005+’. Otherwise, it might be easier to change the hashing algorithm for the objects that should not use ‘SHA-1, SQL Server 2005+’, rather than change the hashing algorithm for those that should.Key stores cannot be reset using the procedure below. In addition to that, key stores will continue to be marked for deployment even when you've switched the hashing algorithm back to the original. Get in touch with TimeXtender support if you need help avoiding redeployment.To changed the all objects using ‘SHA-1, SQL Server 2005+’ to ‘Use instance default’, follow the steps below. Open the affected Prepare instance. Right click the instance in the Solution Explorer and click Edit Instance. In the Hashing algorithm list, click SHA-1, SQL Server 2005+, then click OK. In the window that pops up, click Yes to change the hash algorithm on the objects that use ‘SHA-1, SQL Server 2005+’ to ‘Use instance default’.  Right click the instance in the Solution Explorer and click Edit Instance again. In the Hashing algorithm list, click the algorithm you actually want to use and then click OK. Change the hashing algorithm for any objects that are supposed to use ‘SHA-1, SQL Server 2005+’, e.g. objects created before you initially switched the default setting.Note: If you have a lot of affected instances, get in touch with TimeXtender support and we can help you reset the affected objects programmatically.  

Today, we’ve published a minor release of the TimeXtender Data Integration Ingest Service (v. 7262.1) to address an issue that could lead to wrong data under specific circumstances.Note: This release includes a new version of the Ingest Service only. The current version of the main TimeXtender Data Integration application is still v. 7257.1.FixedWhen copying data from an Ingest instance using Fabric Lakehouse storage to a Prepare instance using SQL storage, dictionary encoding in the Parquet files could, in rare cases, cause the offset of columns to shift, leading to wrong data in the affected columns. We have fixed this issue and recommend that you do a full load from the data source through Ingest to Prepare if you're using this combination of storage to make sure data is correct.

Today, we’ve started the rollout of the next version of TimeXtender Data Enrichment that contains the changes listed below. New and Improved  Added option to use Windows user impersonation (desktop), this enables to do operations as another Active Directory user than the currently active user. This feature is available for on-prem enterprise customers.   Added new error page to web version with more information about what went wrong and the option to report errors directly to support.  Handle updating DateOnly column that caused error (DateOnly -> DateTime) (HotFix 25.2)  If a user had an access filter on a column that was readonly, they could not edit any values of other columns either.  Clicking Ctrl+S when adding a new row in the web application duplicated the row.  Deprecated adding new Fivetran connections. 

Today, we’ve started the rollout of the next version of TimeXtender Orchestration & Data Quality that contains the changes listed below. New and improved Generate Rules with XPilot (Preview) Data Quality now includes a preview feature where XPilot can analyze a dataset and suggest data quality rules.  This helps reduce the time spent creating baseline controls and speeds up delivery of AI-ready data to downstream users and processes.  To get started, open “Generate Rules with XPilot” in Data Quality. Fabric Optimization added to Azure Cloud Optimization package type Azure Cloud Optimizer packages now support pausing and resuming, and scaling Fabric capacities. This makes it easier to match capacity to workload timing and manage cost more predictably. See details in “Configuring Azure Cloud Optimizer”. Azure App Registration as Authentication method SQL and SSAS endpoints now support Azure App Registration as an authentication method, in addition to SQL logins and (for on-premises) Windows authentication.  This adds an option that can be easier to govern and automate in cloud environments. Orchestration Error Insights with XPilot [Preview] Orchestration & Data Quality now includes a preview of XPilot Error Insights to help diagnose failures faster.  This is useful for common runtime issues such as authentication failures, network problems, and schema changes where log review can take time. See more information in XPilot Error Insights And much more In addition to the headliners, the release also includes lots of smaller improvements:  Executions in Turnkey/TDP: View running tasks in a workspace, stop one or more tasks, and use Flush Queue to clear stale executions.  Time zone support in Turnkey/TDP: Timestamps now display in the configured time zone across key areas including datasets, rules, exceptions, process maps, executions, and settings.   Completely revamped User Management in Turnkey/TDP:   User Management for cloud services is now fully handled in the Timextender Data Platform (TDP), and the user administration UI in the desktop client will be disabled. Users and their privileges from Desktop and TDP will be merged and synced.  All tasks such as creating users, assigning roles, and adjusting access must be performed in TDP, and changes will then synchronize to the desktop environment where applicable.  User group management remains available in the desktop client and continues to work as before, but group‑based privileges do not affect access or behavior in the Timextender Data Platform (TDP) yet.  This only applies for cloud customers.  Systems synced to workspaces – only applies to cloud customers  From this release, all existing systems are automatically synchronized to workspaces in the Timextender Data Platform (TDP).  Cloud customers must now manage all workspaces exclusively through TDP, since workspace creation and changes are no longer supported in the legacy desktop experience for cloud  Workspace owners changed to notification users  Existing workspace owners are preserved and updated so they continue to receive notifications and now also gain explicit administrator access to their workspaces.  All users who are currently set as workspace owners will automatically become Administrators on the same workspaces in the Timextender Data Platform (TDP).  The “workspace owner” label is renamed to notification user, which is the user who receives email notifications related to that workspace (for example, execution or exception notifications, depending on configuration).  Improved  Updated graphics for Installer, icons and splash screen to follow the new look.  On portal there is a banner guiding users to use TimeXtender Data Platform  (Turnkey) with link.  Process title text and position is more uniform across Desktop, Portal and Turnkey.  Clarified when executing an empty process that it contained no active task and therefore there was nothing to do.  Improved filtering of invalid characters from column names entered by users.  Improved error messages in execution log for various different problems.  Fixed  Removed the "work in progress" panel from the home page in Turnkey.  Users were automatically directed to a disabled module in the Portal when trying to access a specific system  Clicking Open in Portal as User in the desktop client sometimes opened TDP instead of the Portal  Data Transfer package could not be opened if the Execution Connection had been deleted  Deleted email templates were visible in Turnkey/TDP  Exceptions links were not updated to point to the new domain odq.timextender.com instead of exmon.com  Improved message that appears when an older version of the desktop client is used to open a service that has been upgraded to a newer version.  Corrected text when removing Data Provider in Turnkey.  Fixed an issue with Azure Cloud Optimizer package type not deallocating Virtual Machines when stopping them. 

Today, we’ve released updated data source providers along with the new release of TimeXtender Data Integration. See the changes below.  Business Central 365 Version: 24.0.0.0 (TDI)  Added support for running on Ingest configured for Snowflake.  Business Central 365 Option Values Version: 24.0.0.0 (TDI)  Added support for running on Ingest configured for Snowflake.  CSV Version: 24.3.5.0 (TDI) / 1.9.0 (20.10 BU) / 16.4.23.0 (20.10 ODX) Added support for running on Ingest configured for Snowflake.  Added support for incremental load. Dynamics 365 Business Central – Online Version: 24.1.0.0 (TDI)  Added support for running on Ingest configured for Snowflake.  Dynamics 365 Business Central – SQL Server Version: 24.0.0.0 (TDI)  Added support for running on Ingest configured for Snowflake.  Dynamics 365 Finance – SQL Server Version: 24.1.0.0 (TDI)  Added support for running on Ingest configured for Snowflake.  Exact Online Version: 12.1.0.0 (TDI) Added support for running on Ingest configured for Snowflake.  Fixed a bug where parsing data type could fail when reading. Excel Version: 24.3.2.0 (TDI) / 1.10.0 (20.10 BU) / 16.4.22.0 (20.10 ODX) Added support for running on Ingest configured for Snowflake.  Added incremental load support.  Fixed a bug where culture was not applied properly in some cased when reading data. Hubspot Version: 12.1.0.0 (TDI) Added support for running on Ingest configured for Snowflake.  Fixed a bug where parsing data type could fail when reading. Infor SunSystems Version: 24.0.0.0 (TDI) Added support for running on Ingest configured for Snowflake. Fix query table/tool to use a default underlying table.  Removed a wrong validation of Template business unit setting so that it can be left empty MongoDB Version: 24.2.0.0 (TDI) / 1.1.0 (20.10 BU) / 16.4.2.0 (20.10 ODX)  New TimeXtender Enhanced data source provider  MySQL Version: 24.1.1.0 (TDI) / 1.0.0 (20.10 BU) / 16.4.0.0 (20.10 ODX)  New TimeXtender Enhanced data source provider  Navision Option Values Version: 24.0.0.0 (TDI)  Added support for running on Ingest configured for Snowflake.  ODATA Version: 12.1.0.0 (TDI) / 1.4.1 (20.10 BU) / 16.4.9.0 (20.10 ODX) Added support for running on Ingest configured for Snowflake.  Fixed a bug where parsing data type could fail when reading. OneLake Delta Parquet Version: 24.0.0.0 (TDI)  Added support for running on Ingest configured for Snowflake.  OneLake Finance & Operations Version: 24.1.0.0 (TDI)  Added support for running on Ingest configured for Snowflake.  Oracle Version: 24.1.4.0 (TDI)  Added support for running on Ingest configured for Snowflake.  Parquet Version: 24.1.1.0 (TDI) / 16.4.13.0 (20.10 ODX) Added support for running on Ingest configured for Snowflake.  Fixed bug where no rows in source could lead to error. REST Version: 12.1.0.0 (TDI) / 1.10.1 (20.10 BU) / 16.4.23.0 (20.10 ODX) Added support for running on Ingest configured for Snowflake.  Fixed a bug where parsing data type could fail when reading. Salesforce Version: 24.0.0.0 (TDI) / 1.0.0 (20.10 BU) / 16.4.0.0 (20.10 ODX)  New TimeXtender Enhanced data source provider  SQL Database Version: 24.1.3.0 (TDI)  Added support for running on Ingest configured for Snowflake. XML/JSON Version: 24.1.1.0 (TDI) / 1.8.0 (20.10 BU) / 16.4.16.0 (20.10 ODX) Added support for running on Ingest configured for Snowflake.  Added support for culture when reading metadata.  Add functionality to support dynamic values in table flattening configuration names.  

It's winter here in the northern hemisphere, so of course our new release of TimeXtender Data Integration, includes improvements for our Snowflake integration. AI, however, is hot as a summer day, and we're happy to introduce the TimeXtender MCP server endpoint for connecting your data to AI agents in a simple and secure way. And those are just two of the cool new features in the new release – dive into the full list below.We’ve updated the initial release (and bumped the version from 7256.1 to 7257.1) fixing two issues, one preventing the Execution Service from starting. See the details under Fixed.NewConnect AI and data with the TimeXtender MCP Server Deliver endpoint (Preview)The new TimeXtender MCP Server endpoint in the Deliver layer lets you plug tools like ChatGPT and Claude directly into your governed, business-ready semantic models, so AI works in your real business language instead of guessing from raw database schemas. You get faster, more accurate answers because the AI sees clear entities, relationships, and measures such as “Customer Name” and “Revenue YTD,” not cryptic table and column names.Compared to generic MCPs that probe databases blindly, this server exposes your semantic layer with AI-ready data, read-only least-privilege access and enterprise authentication, improving reliability and security for AI-driven insights you can trust.This feature is in preview - visit Get Early Access if you want to try it out.Snowflake as a new storage option in IngestWe’ve added support for native Snowflake storage in the Ingest instance. Previously, you had to land data in Azure Data Lake before moving to Snowflake in the Prepare layer. Now, you can cut complexity and cloud costs by running a Snowflake‑only architecture.By loading into Snowflake using its native staging and COPY INTO patterns, you follow Snowflake best practices while still benefitting from TimeXtender’s incremental load logic, helping you keep Snowflake usage and execution times under control.Snowflake improvements for Prepare storageWe’re adding support for the remaining core TimeXtender features for Prepare instances on Snowflake storage, including custom data, custom hash fields, pre- and postscripts, related records, checkpoints, hierarchy tables and integrate existing objects. One notable exception is object level security and related features, which will be included in an upcoming release.Previously, you had to use a Microsoft SQL variant as storage if you needed these capabilities, since Snowflake storage only supported features on the simple mode level. Now, Snowflake and SQL support roughly the same features, so you can move projects across storage technologies more easily and still follow TimeXtender best practices regardless of which platform you choose.Select and transfer data between Prepare instances on SQLYou can now select and transfer data between Prepare instances, so you can use one Prepare instance as a data source for another in the same way you already do with Ingest. This is currently supported for Prepare instances using SQL storage.Previously, you were limited to pulling data into Prepare only from Ingest instances, which made it impossible to build more than three logical layers, reuse an external Prepare-based dataset across projects, or design hybrid setups. Now you can drag and drop tables between Prepare instances and combine data from multiple Prepare and Ingest sources into the same table, giving you much more flexibility to design layered, reusable solutions without manual workarounds.Qlik Cloud Deliver endpointWe’ve added a new Deliver endpoint for Qlik Cloud, so you can push TimeXtender semantic models directly into Qlik’s SaaS platform instead of only targeting Qlik Sense Enterprise.Previously, you had to rely on workarounds and custom tricks to connect TimeXtender to Qlik Cloud, which added friction, complexity, and extra maintenance for you and your partners. Now you can configure Qlik Cloud as a first‑class endpoint, reuse your existing Qlik skills and apps, and keep TimeXtender as your central, governed data and semantic layer while still following Qlik’s recommended APIs and patterns. Note that managed workspaces are currently not supported.Support for SQL Server 2025TDI now supports Microsoft SQL Server 2025, which was released in November 2025, as storage.ImprovedCreating new instances is now much fasterWe have brought the time it takes to create a new instance down to 3-5 seconds - in most cases - by pre-provisioning resources. We hope you’ll enjoy the time saved – we sure do!Decide when data source providers are updatedYou can now control when data source providers are updated in Ingest instances. Previously, the system automatically updated all data sources to the latest compatible version when you installed a new version of TDI. This could introduce unexpected behavior, breaking changes, or even downtime in your production environments.Now you decide when and where to update data source providers: you can turn off all automatic updates, keep the existing “always update” behavior, or selectively enable automatic updates per data source.More efficient primary key storage for incremental loads on SQLThis change reduces duplicate primary key data for incremental loads in SQL, improving storage efficiency. Each primary key row now has a validity range instead of being repeated for every batch. Existing tables are upgraded automatically, and both the old and new structures continue to work when transferring data from Ingest to Prepare.User experience improvementsIn addition to the bigger item, we’ve also included a few smaller improvements to the user experience. The Query Tool window has an updated layout with a word wrap option. And, building on the work done in our last major version, data lineage performance has been improved. In addition to that, the SQL Server Cleanup tool can now resolve the name of other instances in the storage that would previously be shown as ‘Unknown TX object’.DeprecatedDedicated SQL Pool (formerly SQL DW) deprecated as Prepare storageWe’ve supported Dedicated SQL Pool as data warehouse/Prepare instance storage since 2019, but we’ve seen very little usage. For that reason, we’ve taken the decision to deprecate support for it so that we can focus our effort on more promising storage technologies.FixedTDI PortalUsers would sometimes accidentally be logged out of the TDI portal. The SQL connection string in the additional parameters for SQL 2022 and Dedicated SQL Pool was not correctly validated in the TDI portal during save. The company details would occasionally show an error instead of company address data. Fixed a cosmetic issue where the secret field for Azure Data Lake Storage was unintentionally set to blank after saving.TimeXtender Data IntegrationIn Prepare instances using Fabric storage, incremental load with deletes would, in some cases, return duplicate records. It was possible to create and deploy two tables with the same name and schema - the last table to be deployed would just “win”. Now, this will result in a validation error on deployment. The Query Tool would show datetime values as date. In some cases, the proxy setting was not applied when making API requests to the TimeXtender web services. It wasn’t possible to generate documentation on Ingest instances We’ve fixed a bunch of issues that would pop up when using Snowflake Prepare instance storage: Dragging a table to the Views node to create a view would create a view where the FROM statement was empty. Conditional lookups would return incorrect values when the ‘Merge conditional lookups’ option was set to the default ‘Merge all if possible (fastest)‘. Data selection rules didn’t work. The application would attempt to cast NULL to datatime2, which is not a valid data type in Snowflake. (v. 7257.1) Running a scheduled TDI execution package in Orchestration could cause the error “The process is unresponsive. Failed to read from process after retrying 3 times,” especially when many executions ran simultaneously. We have fixed an issue in the communication between the Execution Service and the main TDI application to resolve this. (v. 7257.1) An issue with the Execution Service configuration file prevented the service from starting because it couldn't load a required DLL.

Today, we’ve released updated data source providers. See the changes below.Azure Data Factory - SQL ServerVersion: 17.0.1.0 (TDI)Importing metadata would not resolve the datetime precision. This has now been fixed.

Today, we released a hotfix of TimeXtender Data Quality & Orchestration (v. 25.2.0.55).FixedAuth0 users could not log in builds 25.2.0.53 and 25.2.0.54 In some cases, the ‘Open Portal as user’ button would try to direct users to turnkey instead of the old portal. Exception links used ‘.exmon.com’ instead of ‘.odq.timextender.com’ If DataTransfer was using execution connection that had been deleted, the user could not open the DataTransfer package to fix it.

Today, we’ve released an updated data source provider for Excel. See the changes below.ExcelVersion: 23.19.2.0 (TDI) / 1.8.0 (20.10 BU) / 16.4.20.0 (20.10 ODX)Fixed issue where culture and decimal separator could not be used together. Fixed issue where "Date formats" would not apply when loading data. Fixed issue with nvarchar length for the ‘_ResourceURI’ column not being long enough. Updated core Excel library (Sylvan) to include a bug fix related to reading numbers with culture.

We’ve published three minor releases of TimeXtender Data Integration as follow-ups to the last major release. To give you a better overview of the changes included if you upgrade today, we’ve listed them all below. We recommend that you upgrade if you’re affected by any of the issues that have been fixed.7158.122 Oct 2025Fixed an issue where the direct read stored procedure would be wrong when the source mapping is a view.7157.121 Oct 2025On Fabric Lakehouse Prepare instance storage, the execution timeout per cell was fixed at 600 seconds which was too short in some cases. You can now configure the cell execution timeout by changing the command timeout for the storage in the Portal. Fixed a long-standing issue present since the initial release, where records with negative DW_Id values (e.g., -999, -998) were not transferred correctly between tables. This fix ensures all valid rows, including those with negative identifiers, are now properly processed during data warehouse transfers. 7150.115 Oct 2025Fixed an issue where data of the Sql Decimal type containing null values would fail for transfers to the Ingest Storage when using Parquet files as the output.  Fixed an issue where Selection Rules didn't work as expected on a Prepare Lakehouse. Fixed an issue where re-deploying measures and hierarchies in Qlik would time out. Fixed an issue where deploying a Tabular model to Azure Analysis Services would fail with a message saying a dll was missing. Fixed an issue where a sub query was used to get primary keys for incremental load when sub query is disabled for query tables. Fix primary key upload during incremental load with "handle deletes" enabled for data lake.