Ingest

We have a client with a Rest Datasource that does not use URL parameters. Instead they use the post body to pass a series of filters and conditions.We are using this post body to implement Incremental loading from the datasource. It seems to be working correctly in so far as the rest source is definitely loading incrementally.However the Ingest instance does not seem to recognize the tables in the Gen 2 Storage as incremental.We have defined the incremental several times, deleted the entire folder in the Azure Gen2 storage. Still the same result.if we drag the table over to a data area the source in the Ingest instance is not flagged with an “i” indicating that it is incremental.Is this because we are passing the incremental variable through the post body and not as a query parameter?if this is the case is there a work around?The issue we are facing is that we cannot do any downstream incremental loads as TX complains that the source table in the ingets instance is not incremental. Not

Hello. This document has the ports which need to be opened. Configure your Firewall | Community It doesn't reference Fabric Lakehouse.. are you able to advise what we need to open for the ingest service to communicate to Fabric Lakehouse?Thanks Tim

Hi,We are consolidating our ingestion setup from one ingest instance per environment to a single shared ingest instance for both DEV and PRD environments.Current situation:ODX DEV → DSA_DEV → SSL_DEVODX PRD → DSA_PRD → SSL_PRDTarget situation: ↗ DSA_DEV → SSL_DEVODX PRD ↘ DSA_PRD → SSL_PRDThe DEV VM is able to communicate with the PRD VM, where the shared ODX instance is hosted.Could you please advise on the next steps required to implement this change?  

I have a large table with about 50 columns. There is column called projectNumber. This column, i am unable to override.This column is varchar. However in TX with Enhanced Drivers it shows Int32.I have overridden it to Text It even says so in Data type overrides on the DataSource I have even tried adding and removing it in Table builder  

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’?

I have followed this guide to set-up an Incremental load on a table in BU:Incremental Loading in a Business Unit (BU) in TimeXtender Classic | CommunityHowever, during the deploy i get an error:Data source Incr LoadsValidation status: ValidMessage: OKStaging Database ODXValidation status: ValidMessage: OKTable: Incr_LoadValidation status: ValidMessage: OKIncremental LoadValidation status: ErrorMessage: Incremental load is not supported on this table.Details:Data source Incr Loads ...TimeXtender.DataManager.UserErrorExceptionIt says in the guide that: When the option is enabled and the table is deployed, TimeXtender performs the following:Initial Full Load: The system fully loads the table. Setting content of the _I Table: This table records the largest incremental field value from the given load I am attachig a video of where i get an error.What am i doing wrong?

Can I preserve my source field names when synchronizeing my fields?I dont want spaces and periods replaces by an underscore, my current workaround is to edit the fields manually when I use the tables in my prepare instance.  

Version: TX 7158.1Hello,I’m currently running into an incremental loading issue where the source system automatically generates invoices in batches. This inserts new rows/Primary keys in the invoice table. It could be that certain invoices are scheduled for a batch. Let’s say from 24-07-2026 scheduled for 29-07-2026.If that’s the case, the new row will get inserted on 29-07-2026 with a datelastmodified of 24-07-2026. Any changes to that document will trigger the datelastmodified correctly, only this process gives this issue. In that case, my incremental loading will completely miss these new document / primary keys (currently -1 day offset).Is there a way to always add new primary keys but only do the updates based on the datelastmodified timestamp?

In TX Enhanced Connector, how do one handle fields in JSON response that has the same name?In the screen-grab below, the fields in marked in red comes multiple times but the values are different.In TX Enhanced Connector, the field always grabs the value of the first occurance of the field i have marked in red.Is there a way to grab the desired value by doing somethng like this:/json/addendumValues/addendumGroups/rows[0]/json/addendumValues/addendumGroups/rows[1]/json/addendumValues/addendumGroups/rows[2]/json/addendumValues/addendumGroups/rows[3] If not, is there a way to grab everything in blue and show in one column?I can then creat a view in BU and grab each saperately The screen grabs are broek here: Understanding and using script parameters in TimeXtender Classic | Community, so i can not fuly understand the documentation

Hello,After Snowflake enabled behavior change bundle 2026_04 on our production account, our execution packages began failing. TimeXtender generates the "SCD Surrogate Hash Key" column as a virtual (computed) column with a NOT NULL constraint.As of bundle 2026_04, Snowflake rejects NOT NULL/CHECK constraints on virtual columns at DDL time, so the CREATE TABLE statement for the TX-generated temporary staging table now fails. The same project ran fine until the bundle was enabled, and runs fine again after we temporarily disabled the bundle.The failures occur only on tables that have History (SCD) settings enabled. Tables without history are unaffected, which is consistent with the surrogate hash key being generated specifically for the history/SCD code path.Environment- TimeXtender Data Integration, product/portal version: 7158.1- Data storage: SnowflakeError messageJavaScript execution error: Uncaught Execution of multiple statements failed on statement "CREATE TABLE ...#<temp>...

I have en endpint with multiple parameters:CaseHandling/External/Cases/GetCases?exportFields=CaseID&exportFields=Closed&exportFields=Position&exportFields=ProjectLevel&exportFields=Anonymous&Key is always exportFields Values are differentIn CData i have no issues getting values in the columns.In TX Enhanced Connection, when i define multiple parametes with key-anme exportFields and different value, only the last is shown: This is how i have defined in TX Endpoint I have tried the whole endoint in Path, which gived empty table  

Dear sir,How can I remap tables to a different ODX instance automatically, instead remapping tables manually for a 100+ tables (V7303.1).Any suggestion is welcome.Thanx.Regards,Arthur

Hi,TimeXtender Data Integration 7303.1TimeXtender Ingest Service 7313.1  We are connected to our Azure Datalake Gen2 storagecontainer (tested OK through TDI) We are having problems with our ingestserver trying to connect to all our data sources. All of them are timing out when running and they fails with no log The only log we kan find are from TimeXtender O&DQ Desktop (see att.)We have been trough https://support.timextender.com/initial-setup-start-here-115/configure-your-firewall-700 and done the tests,  all OKTest-NetConnection sql-instances-prod.database.windows.net -port 20000Test-NetConnection sql-instances-prod-002.database.windows.net -port 20000Test-NetConnection traws.timextender.com -Port 443Test-NetConnection gateway.timextender.com -Port 443Test-NetConnection gateway.timextender.com -Port 80Test-NetConnection sbns-customer-prod-001.servicebus.windows.net -port 5671Test-NetConnection sbns-customer-prod-001.servicebus.windows.net -port 5672Test-NetConnection auth0.com -P

I’m currently working with TX Enhanced Data Connectors and have noticed that there doesn’t seem to be a built‑in way to handle HTTP 404 errors. Heres is a senario:I have en endpoint which is:/api/{referenceA}/{referenceB}referenceA are office-location IDsreferenceB are values like [sales, procurement, operations]I can do this either by GET, this way: or, by POST, this way: { "referenceA": {officeLocations}, "controlCurves": [ "sales", "procurement", "operations" ]}If an office location (referenceA) has all three departments (referenceB), i get a responseIf an office location (referenceA) has one or more departents (eferenceB) missing, the extraction stops.I have also tried it with a GET method in TX Enhanced ConnectorsI dont want the extraction to stop, i want it to skip and go to next value. Something like this (log from a python script): Fetched sales for LOC1Fetched operations for LOC1Failed for LOC1, procurement, status 404Response: {"description":"Procurement' does not exist

Hello,We recently upgraded from TX destkop 20.10.45 to 20.10.80 (Both ODX and App). After migrating the ODX from the Db022 to the Db026, the CDATA Microsoft Active Directory 2025 connector succesfly completed all its taks, but tables in the ODX are still empty. I already tried:Switching to older version (2021) Installed another test connector Reinstalling ODXAnyone an idea how this is possible. Below some (blured) screens.    

I have now installed a new version on a new server.I have downloaded Enhanced datasources.Now i want to Replcate one of my CData Sources so that i can use TX REST ot TX JSON datasource. The Cata Source i want to replicate is a REST source:DataModel : FlattenedDocumentsI have my RSD files at: C\RSD\DataSourceConection requires that i send a bearer token.  

A couple of questions:Table builderTo build i a table, i extract data steam first in POSTMAN.I can either copy it into a flatfile and use input method Local File I find it a bit strange that there no browser option:  Or if the response is not too large, i can just copy it into Table Builder[ { "_recno": 0, "ID": "1", "Topic": "TX Enhanced Data Connectors", "valid_upto": "2099-12-31T00:00:00+01:00", "attr": "Data Connectors", "related_attr": "TX", "status": "N", "date_from": "1900-01-01T00:00:00+01:00" }]This is the table builder, with copied respose: The issue is that, when i click OK, go out and go back in, the space where i have pasted the respose is empty and so is the ‘Nodes in the table’ window ! Table Builder - errorIf i some how makes a mistake (lets say that i have forgot the closing brackets): instead of a pop-up error, TableBuilder throws me out and the changes are lost: Show XMLAlso, what is Show XML tab at the bo

Hi, I'm trying to consume REST API with limit/offset paginationhttps://<>.rest.afas.online/ProfitRestServices/connectors/<connector>?skip=250&take=250&orderbyfieldids=Medewerkerskip = Offset. in the example above skip the first 250 rows take = limit. take 250 rows seems to work in Postman My approach was to use 'override pagination’In combination with endpoint's 'query parameters’  using the following expression:SELECT ({TX_NextPage} - 1) * 150 AS skipValueWhen running the ODX tasks it seems to ingest only the first page. What am i'm doing wrong? 

In 20.10, is there a way to remove a data source but keep the tables with the data that were created from it? I’m trying to eliminate my last CData data source that pulled legacy data in from an old MS Access database. I tried to remove the data source, but in doing so, it attempts to delete the loaded tables in the Business Unit. I still need to be able to use and reference the legacy data that was loaded but I no longer have access to the legacy MS Access database to re-load it with a non-CData connector.

Hi,TimeXtender Data Integration 7303.1TimeXtender Execution Service Configuration 7303.1Storage Type: Azure Data Lake Gen2 storage  All my mapped data source connections has not connection to the source since friday 27/3 evening. So none are working. None error messages when running....Any clue why?best regards,Bjørn A.

Hello,What’s currently the recommended alternative for the CData Googlesheets provider when we switch to TimeXtender Enhanced providers?Kind Regards,Hendrik

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

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

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.