Recently active topics

Hiwhen I try to test the connection I get this error message:Exception Type: ODX.Model.Exceptions.DataSourceExceptionMessage: The connection 'EXT_EXACT_NL' uses a version of the provider that is not compatible with this version of TimeXtender Ingest Service. Upgrade the data source connection in the Portal and try again.But I cannot upgrade the provider. Has anyone the same issue?

I’ve got a customer with approx. 200 orchestration packages in TDP 26.3.I need to update retry settings for the vast majority of these packages … manually, that’ll take close to forever.We should have a bulk-update feature based on the existing multi-select feature, which currently only works for deletions:  enable/disable retries and, if enable, set the retry interval to e.g. 60 seconds for all selected packages.Notifications are also relevant from a bulk-update perspective.

Hello,My Azure SQL ERP source does not have a lastmodified datetimestamp on the tables. We’re investigating the options to enable change data capture (CDC) or change tracking (CT) on the biggest tables.How would I proceed with further setting this up with TimeXtender? I can't find any related manuals, blogs or sources for this.Thanks in advance! 

I have just checked the excution on a clients Orchestration site and it seems to have dropped history and I am not sure if scheduled executions are happening. Is there an issue with your Orchestration tool?I just had a look at the history package in a production process and process map that runs every hour and the history on that item shows it executing this morning at 8:57 (over 3 hours ago) and then before that August 5th! It has definitely been running consistently, so I am not sure what has happened that you no longer have history why and the process executions do not appear to be taking place as scheduled.  

The TimeXtender MCP Server bridges AI agents and governed analytics data by exposing semantic models through the Model Context Protocol (MCP). It solves the core reliability problem in AI-driven analytics: making sure AI-generated queries use approved business definitions and validated logic instead of guessing meanings from raw database schemas.Early AccessTimeXtender MCP Server is currently in Preview. Apply to the Early Access Program to get started.ArchitectureThe MCP Server runs as a single Windows service on a machine inside your environment. That one service hosts every semantic model you register, talks to the underlying data warehouse with a read-only database account, and answers AI clients that connect to it locally or over HTTPS.The TimeXtender MCP Configurator (a separate Windows desktop application installed alongside the server) is where you register models, configure providers, generate API keys, and start the service. The Configurator writes the server's configuration

I'm currently loading Parquet "tables" in TX Classic with the following setup: Using Synapse Serverless to read Parquet files and expose them as external tables Connecting via SQL Server authentication This works, but I’m looking for a better approach.Is there a way to read Parquet "tables" directly in TX Classic? The Enhanced Data Source seems limited to reading or aggregating files, not treating them as tables.Alternatively, could I replace Synapse Serverless with Fabric Serverless? The main blocker is authentication—TX doesn't appear to support SQL providers with service principal (OAuth) authentication, only SQL Server authentication, which we’d prefer to avoid.Any suggestions, recommendations or workarounds would be appreciated. 

I’m getting this error in the Sign In proccess in the new version 26.3.0.1  

Project blueprints enable a Timextender partner to publish a Timextender Classic project once and let their customers use it as the starting point for new projects. Work done for one customer can be reused for the next, so customers start from a working solution instead of an empty project, all without juggling project imports and exports. If you've used Instance Blueprints in Timextender Data Integration, this is the same idea for Classic.Understanding Project BlueprintsA project blueprint is a copy of a project that a partner publishes for reuse. When a partner uploads a blueprint, they set its name, version, description, an optional documentation link, and its visibility.Visibility controls who can see and use a blueprint:Public: All customers below the partner's organization in the Timextender Portal hierarchy can see and use the blueprint. Access is checked every time the list is loaded, so a customer who is added later sees existing public blueprints without the partner having to

With the Microsoft Fabric SQL Provider, the Dynamics AX adapter in Timextender Classic can read Dynamics 365 Finance & Operations data from a Microsoft Fabric Lakehouse that Dynamics exports into, for example with Link to Fabric, instead of from an AX SQL Server or Oracle database. The provider connects to the Lakehouse's SQL Analytics Endpoint and authenticates with a Microsoft Entra service principal. Everything else about the adapter is unchanged: companies, table selection, enum labels, incremental load, and primary key deletes work as they do with a SQL AX source. For the adapter itself, see Timextender Dynamics 365 F&O Data Source: Classic (AX Adapter).PrerequisitesIn Microsoft FabricA Lakehouse that Dynamics exports into, and its SQL Analytics Endpoint. The export must include the tables you want to read. In addition to your business tables, three tables are important: dataarea: The company master. Without it, the adapter cannot synchronize companies. sqldictionary: AX'

Hi,We have a Contact Centre based on MS Teams (quite a new solution for us) and now they want to start gathering data and follow up the number of calls per operator and such. The only option that the service provider provides for us to get a hold on that data is to set up an Azure SQL database that they can send the data into.Since we have all our other databases locally, I was looking into how to set up a connection to such a database in the portal but didn’t find any specific option for that. Should I just use a “regular” SQL connection with the Azure server name and database name with Entra authentication or how do I go about this?Anyone who has done this before?Any information is appreciated. :)

Hello, I have submitted the following question to TimeXtender support. I wanted to post the question here to see if there are other people that have build or are trying a similar solution to monitor the executions. We are currently implementing a monitoring and orchestration framework based on the TimeXtender Meta Collection data.According to the TimeXtender documentation, Meta Collection metadata is exported once every 24 hours to the data lake. We have also observed this behavior in our environment. The documentation states that metadata is exported once every 24 hours and the exported files overwrite the previous export. Our use caseWe are using the following Meta Collection entities to monitor the execution status of our data platform:Ingest_ExecutionTasks Ingest_ExecutionLogs Ingest_Tasks Ingest_TaskVersions Ingest_DataSourceVersionsThe objective is to determine:Which tasks were executed Whether the execution was successful Whether warnings or errors occurred Which datasource and

Hot on the heels of 26.3, we've published a minor release of Timextender Data Integration (v. 26.3.0.2) with a follow-up feature to the full support for Fabric Warehouse as Prepare instance storage (in public preview) that was a headline feature of 26.3.The Dynamics 365 Finance & Operations Fabric/OneLake data source now works with Prepare instances on Fabric Warehouse storage. We've also included a few fixes in this release, most of them for incremental loads on Fabric Warehouse.New & ImprovedDynamics 365 F&O Fabric/OneLake Data Source Now Supports Prepare on Fabric WarehouseYou can now use the Timextender OneLake Finance & Operations data source with Prepare instances on Fabric Warehouse. Until now, a Prepare instance on Fabric Lakehouse was required if you wanted to use the data source with Fabric.Behind the scenes, the Ingest service creates shortcuts in your Ingest Lakehouse to the F&O tables you've selected in OneLake, and Prepare on Warehouse reads the data t

Orchestration & Data Quality can run your Timextender Data Integration (TDI) work on a schedule: your Ingest, Prepare and Deliver tasks, in the order you choose, against the instance you choose for each environment. Every run is recorded, and you can have someone notified when one fails.There are three steps:Connect Orchestration to TDI with a data provider. Map your TDI instances to Orchestration's three environments — this is environment-aware sync, and it is what lets one set of packages serve all your environments. Schedule the work, choosing the environment each schedule runs in.This page walks through all three, in order. You do this once per data provider.Already running TDI packages in Orchestration?Instance mapping was introduced in 26.2. If your TDI data provider was created before 26.2, start with Migrate from per-environment TDI packages. It explains what changes, what keeps working in the meantime, and what to retire. Following this page alone would leave you with two

I have encountered an issue after upgrading the TX Enhanced REST Connector from version 1.10.2 to version 1.15.0.The problem did not occur when using version 1.10.2.Our environment consists of a single TimeXtender server hosting both DEV and PROD environments.Since upgrading to version 1.15.0, i am no longer able to create new Data Sorce using TX Enhanced REST Connector v. 1.15.0 in PROD (DEV works fine). However, creating connections with version 1.10.2 continues to work without any issues in both PROD and DEVI am a bit reluctuent to re-/uninstall 1.15.0 because i have a datasource in DEV with 15 endpoints that use 1.15.0. 

I am experiencing an issue that I have encountered a few times before in TimeXtender Classic. Previously, the problem was resolved either by restarting TimeXtender or by recreating the affected tables. However, this time I have spent a few hours troubleshooting without success.I have two tables in ODX (BU) that need to be copied to corresponding tables in DSA.The situation is as follows:The source tables in ODX/BU are populated with data. The tables are correctly mapped in DSA. When I perform a Deploy (or Execute and Deploy), the tables are generated in DSA as expected. However, no data is transferred to the DSA tables. The tables are created, but they remain empty. Neither the BU tables nor the DSA tables are guarded on Deploy or Execution.I have verified the mappings and deployment configuration, but I have not been able to identify the cause of the issue.Have you seen this behavior before, or are there any logs or settings you would recommend checking?

Incremental Load Strategy for Data Warehouse Layer (Prepare Views → DW Hi everyone,We’re working on a project for a TPA that provides property and casualty services to smaller P&C companies. The architecture connects to multiple disparate sources that ultimately feed into a standardized data warehouse.Here’s our current setup:Architecture:We’re creating a raw schema in Prepare for each data source, then using views to abstract the transformation logic. The DW maps from those views. So the flow is: Source → Ingest → Prepare (raw) → Prepare (views) → DW.What’s working:Incremental loads are running well from Source to Ingest and from Ingest to Prepare raw — no issues there.The challenge:The DW layer currently runs as a full load every time. We’re moving roughly 200M rows per company. Load times are about 1:45 hours, which is manageable, but we’d like to bring that down with incremental loads. It would also reduce the vCore demand — we’re currently on 8 vCores Premium Series with memor

Hi Everyone, We want to use Fabric lakehouse as ingest layer, and did the setup according to this article: We are running TimeXtender version 6898.1We created the lakehouse form Fabric, not by using the ‘Create Storage;  option from TDI. When we test the connection in TDI, everything looks fine:However, the metadata import task fails with following error: The execution failed with error:Exception Type: Azure.RequestFailedExceptionMessage: Service request failed.         Status: 400 (BadRequest)         ErrorCode: IncomingOperationUntrusted                  Headers:         x-ms-error-code: IncomingOperationUntrusted         Access-Control-Allow-Origin: *         Access-Control-Allow-Headers: REDACTED         Access-Control-Allow-Methods: REDACTED         Access-Control-Expose-Headers: REDACTED         Strict-Transport-Security: REDACTED         X-Content-Type-Options: REDACTED         x-ms-root-activity-id: REDACTED         Content-Length: 0         Date: Thu, 06 Mar 2025 14:57:14 GMT 

Hi,Is it possible to connect to a Microsoft Fabric OneLake using a specific data source in TimeXtender version 20.10.74.64?We have tried using a SQL Database connection, but are encountering authentication errors, as the connection depends on Microsoft Entra ID authentication.

I believe I have read the documentation, in case I missed something. My bad. Im trying to load csv files from the root of a S3 bucket. The 'test connection’ in the portal turns green but when trying to synchronize in timextender it tells me I have to enter a value for ‘path’.I have tried these so far: /.mybucketname/inbound/s3://mybucketname/inbound/But timextender keeps throwing errors saying the directory does not exist. I can succesfully connect to it and download the csv's via Python so Im quite sure the setup is correct.  Does anyone know what to fill in for ‘path’?