Recently active topics

In March 2025, we announced plans to deprecate CData providers to streamline our platform and focus on TimeXtender Enhanced connectors. While we believe our native connectors offer the best long-term performance, we understand that flexibility is key to your success and that many of you requested more time or options.We are pleased to share that CData providers will remain available and supported, giving you continued flexibility and choice. CData connectivity will be offered as a premium option, allowing you to remain on CData if you need additional time or prefer the existing functionality, without disruption to your operations.The detailsPricing: 250 USD / 250 EUR / 250 GBP per month per customer account (billed in your subscription currency). Usage: This fee covers unlimited use of any CData providers you need for that account. Effective date: Billing for this service will begin on March 5, 2026.How it worksWe have designed this to be seamless. You do not need to sign a new contrac

Hello,I am connecting to an external blob storage using a private endpoint. The blob storage is structured as follows:parquet/ 2025-12-29/ Acquisition.parquet Asset.parquet AssetBalanceSheet.parquet … User.parquet ValuationAssumption.parquet 2025-12-30/ Acquisition.parquet Asset.parquet … Etc. I am using the TimeXtender Parquet Data Source provider. The connection works, but the results I get from the Metadata Manager are not what I expect.Current settings Path: parquet/ Include subfolders: Yes Included file types: parquet File aggregation pattern: Asset.parquet Expected behaviorI expect the Metadata Manager to return a single table called “Asset”, aggregated across all available date folders.Actual behaviorInstead, all files/tables are returned, with what appears to be an "_<number>" suffix added for each additional date folder (e.g. Asset, Asset_1, Asset_2, etc.).I tried many setting combinations:Test 1: Exact filename, no wildcardsPath: parquet/ Inc

When upgrading data sources, ensure that the TimeXtender Ingest Service has been upgraded to a compatible version before upgrading the data source connection.There are three types of data sources where version compatibility with TimeXtender Data Integration (TDI) and TimeXtender Ingest Service (TIS) needs to be established before upgrading the data source:TimeXtender data sources TimeXtender REST data sources Azure Data Factory (ADF) data sourcesIf your seeing the below message in the portal, you'll want to be sure your TDI/TIS version is compatible before you upgrade your data source connection. Follow these steps:Identify the name of the data source and updated version that is available. View the table below and identify which "Type" of data source it is such as "TimeXtender", "ADF", or "REST". Review the compatibility table below and ensure the TDI/TIS Version you are currently running is either equal to or greater than version that matches the data source version in the table. If n

The HTTPS Configuration tab in the MCP Configurator sets up TLS encryption for all MCP services. Once configured, every service automatically uses HTTPS with the certificate you specify. This is required when connecting to MCP using HTTP mode with OAuth-based clients such as Claude Desktop.Note: HTTPS configuration is optional. If you skip this tab, services default to HTTP (unencrypted connections).HTTP vs HTTPS Prerequisites Instructions Update an Existing Configuration TroubleshootingHTTP vs HTTPSUse the table below to determine whether you need HTTPS for your deployment.  HTTP (default) HTTPS Encryption None - traffic is sent in plain text TLS-encrypted between client and server Authentication API key only API key or OAuth OAuth clients (e.g. Claude Desktop) Not supported - OAuth requires HTTPS Supported Local development / testing Recommended - no certificate needed Optional Production / cross-network Acceptable if network is trusted and API key auth is

Is the new TX Enhanced REST source slower than the old CData REST source?When we tested simple REST endpoints we saw the new TX source using 10x longer for the same identical job.Anyone have any experience with this?For reference we are running on TX 20.10.72.64.

​You can use this provider to connect your MongoDB database.Configuration manual Connection settings Server Port Database Authentication mode Authentication with SCRAM-SHA-256 Authentication with X.509 Certificate Authentication with LDAP (SAS PLAIN) Parsing Settings Configuration manualConnection settingsThese settings relate to the connection to your MongoDB database server.Server Enter the fully qualified domain name (FQDN) or IP address of your MongoDB server.Examples:mongodb.mycompany.com 192.168.1.100 localhostPortSpecify the port number your MongoDB server is listening to. The default MongoDB port is 27017. Only change this if your MongoDB server is configured to use a different port.DatabaseEnter the name of the database you want to connect to. The database must exist on the server before you can connect to it.Authentication modeThe connector supports 4 authentication modes:None: no authentication at all (default) SCRAM-SHA-256: Authentication with username and

You can use this provider to connect to your MySQL database.Configuration manual  Connection settings  Server  Port  Database  Connection Timeout  Command Timeout  User settings SSL Configuration manual Connection settings These settings relate to the connection to your MySQL database server.  Server Enter the fully qualified domain name (FQDN) or IP address of your MySQL server. Examples: mysql.mycompany.com  192.168.1.100  localhost Port Specify the port number your MySQL server is listening to. The default MySQL port is 3306. Only change this if your MySQL server is configured to use a different port. Database Enter the name of the database you want to connect to. The database must exist on the server before you can connect to it. Connection Timeout Specify the time (in seconds) to wait when establishing a connection to the MySQL server before timing out. Increase this value if you experience connection timeouts due to network latency or slow server response. Command

Hi all!Since last week I have this problem where if I login on the TimeXtender portal, I get the following error message: What's strange is that when I go back to the login screen and reset my password, it does work and I get access to the portal:  I've tried some obvious things, like trying a different browser, deleting cache and cookies, etc… Also removing and adding myself as a user (via a colleague) didn't seem to fix it. Does anyone know what the issue could be? Thanks!Willem

Couple of questions regardnig the new version:Why does date say November 2025 for the latest release: Download TimeXtender 20.10 – TimeXtender Support. A bit confusing. Is it the latest version, or is the latest version only available in customer portail? Here is says that V25 is TimeXtenders new focus for on-prem solution, but the lasted version on customer portail is 20.10.74.64. Where can v25 be downloaded from? If upgraded to the TimeXtender Data Integration (fully cloud version), how much work is it to migrate everything from 20.10.45.X ?

Hi all,Lately I have this problem that when I login at the exmon portal, I get the following error message:Earlier it did work, and I would have the usual four buttons shown here. But now the URL just says the sign in failed because of my user details (see image), and I get this white screen.I tried things like using a different browser, deleting cookies and cache, etc…Anyone might know what the issue could be? Or some things me and/or my colleagues could try? (Also, I'm not 100% sure if it has something to do with my issue in this topic. My guess is it probably doesn't, but just to be sure I'm mentioning it here as well. Anyway, these two problems did not start the very same day, but only a couple days apart) Thanks! Willem  

I have just installed TimeXtender ODQ 25.2 and at the end of the install it asked for the installer for the existing version 25.1 which we do not have.Now we cannot uninstall the older version of TimeXtender ODQ because we do not have this version of the installer. Can you please send us the installer so that we can uninstall the older version.

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.

We use the CData provider for CSV to ingest data from a https URL. The source system does not offer any other way to access the data. This works well. TimeXtender Classic with ODX.We're now looking into migrating away from CData (not trying to start a discussion about the reason...). The TimeXtender CSV provider (version 16.4.23.0) does not suport a https location, only local file/azure/s3/sharepoint/google/sftp/ftps. Is there some way to get this to work? The current workaround is to use the TimeXtender REST provider but that's quite a hassle to set up, especially when there are lots of columns involved. Also, it's really not a REST API with CSV response. It's a regular URL.

I have been trying to sort out something out,My JSON looks like this:addendumGroupName occurs multiple times. Here, its 4 times but in other cases it occurs between 1 to 50.columns can be one or multiple I am trying to list all addendumGroupName and all columns under each addendumGroupName without doing this:json/addendumValues/addendumGroups[2]/addendumGroupName[0]json/addendumValues/addendumGroups[2]/rows[0]/columns/fremdrift_group[0] json/addendumValues/addendumGroups[2]/rows[1]/columns/fremdrift_group[0]json/addendumValues/addendumGroups[2]/rows[2]/columns/fremdrift_group[0]  So i tried this (with an without [*] at the end of column name): <attr name="addendumGroupName" xs:type="string" readonly="false" other:xPath="/json/addendumValues/addendumGroups[*]/addendumGroupName[*]" /> <attr name="fremdrift_group" xs:type="string" readonly="false" other:xPath="/json/addendumValues/addendumGroups[*]/rows[*]/columns/fremdrift_group[*]and for JSONpath:<api:set attr="detai

Hi, Within TimeXtender O&DQ I am wondering if it is possible to setup “Email on failure” on processes instead of a singe Packages. Untill now I always add email on failure on every single package, but in the end it would be much faster to be able to add this on a higher, hence on the Prosess level. Is this possible?Kinds regards,Devin

Good Morning, I have just updated O&DQ Desktop from 25.1 to 25.2 and I no longer have the Data Quality folder available in the Object Explorer window. I can still open the Data Quality tests I have setup from the Recent Items on the Start window. But how do I add this menu  item back in so I can see all my DQ tests and creates new ones? 

In the new version 7257.1 What’s mean this symbol in some tables and fields? 

I have a TimeXtender REST connection to SalesForce. This specific REST API is a file api. This means that you have to send a request (in the form of a query) to an endpoint, after which the API starts to generate an export. When the export is finished, it can be downloaded via a separate endpoint as CSV.To extract this data with TX REST, I have set up a method with three endpoints per ‘endpoint’, this works as following:The first endpoint called _query sends a query via a POST request to a specific endpoint The second endpoint called _waitForComplete uses a dynamic value from the _query endpoint so that the _query endpoint gets executed first. The _waitForComplete endpoint uses pagination with a 1-minute delay to send requests to an endpoint that returns the status of the generation of the CSV file. Once the generation is complete, the _waitForComplete endpoint will return a JobComplete response which will stop the pagination. The third endpoint uses a dynamic value from the _waitForCo

Hello, Technical: 20.10.67 using ODX (Updated: SQL Database not data lake)Connector: Cdata Ado.net provider for Json (2024)Settings: Source: Azure blob Data Model=FlattenedDocuments;Flatten Row Limit=1000000I have a situation with a odx transfer task failing and crashing the ODX due to memory.I need to jump in and help in a project where they need to get a very large json (85gb) into TX, because any previous attempts to ingest it fails. I ran a sample size to test (49mb) which resulted in roughly 550k rows and took 60s to run with a transfer task. One page (5000) takes around 200-300ms from looking at logs.If it is linear it would mean upwards of 900 million rows (we do not know the actual row amount) and it could take upwards of 30h if we assume linear scaling here. One easy problem was timeout time, which I fixed by increasing the ODX timeout from 2 hours to 24 hours during testing.Currently I can get it to run to around 6-7 hours but then it fails due to the ODX crashing with the fo

I have the following problem when I perform the migration between environmentsIn Ingest instancesAfter migrating, I have to remap the metadata, select all the tables again.En Prepare instancesThe mapping table bring the source of developer environment and not  prod And Can I create two data source with the same short name?  

OverviewThis guide explains how to configure TimeXtender Data Quality to automatically send exception notifications to a Microsoft Teams channel using an incoming webhook. Prerequisites A Microsoft Teams channel where you want to receive notifications. Permission to create an Incoming Webhook connector in that channel. Access to TimeXtender Data Quality   Step 1: Create an Incoming Webhook in Teams In Teams, go to the channel where you want notifications. Select More options (⋯) → Connectors → Incoming Webhook. Name the webhook (e.g., TimeXtender Data Quality Alerts). Optionally upload an icon, such as the TimeXtender logo. Copy the webhook URL — you’ll need it in TimeXtender.Step 2: Configure the Integration in TimeXtender Data Quality Open TimeXtender Data Quality and navigate to Integrations. In the Desktop client this is under the General folder In the web client this is under Settings   Create a new integration and choose Webhook as the connection type. Paste the Teams webhoo

Overview of AI-Powered Features in TimeXtenderTimeXtender's AI-powered features include the MCP Server, Xpilot Data Quality, and Xpilot Orchestration Error Insights. This document explains where data is processed and hosted to help you make informed decisions about deployment in your environment.All AI features in TimeXtender are optional. You have complete control over which features to enable and how they're configured.Overview of AI-Powered Features in TimeXtender Our Philosophy: Customer Choice Optional by Design Flexibility in Deployment Transparency Your Data, Your Control TimeXtender MCP Server MCP Server Architecture: Zero-Access Security Xpilot Data Quality (Release 26.1) Xpilot Orchestration Error Insights (Release 26.1) Future Roadmap: Enhanced Regional Control Next Release (Planned) Future Releases Our Philosophy: Customer ChoiceTimeXtender's approach to AI features is built on the principle of customer choice and control:Optional by DesignAll AI features

In version 26.1 we have moved User Management for TimeXtender Orchestration & Data Quality to our new web application. This means that user management in the desktop client has now been disabled. For now, User Groups will continue to be managed in the desktop client but their privileges will not be applied to the new web application (Turnkey/TDP).Global Roles Global Administrator Normal User Object Level roles Configuring Users and Roles Creating New Users How Roles Apply to Objects Workspaces Datasets & Rules Process Maps & Executions Desktop Client Access Workspace Group Admin Workspace Group Contributor Viewer Only Migrating from desktop roles to TDP privileges  Desktop to TDP role mapping Understanding user roles and permissions within the TimeXtender Data Platform (TDP) is crucial for effective user management. This article provides a comprehensive overview of global and object-level roles, configuring users, how roles apply to different objects, and how TDP p