Recently active topics

Issues that can arise when executing TimeXtender Data Integration tasks and execution packages in TimeXtender Orchestration:TimeXtender Ingest/Execution Service is not running Server running TimeXtender Ingest/Execution service firewall issue TimeXtender Ingest/Execution service settingsCannot see or select specific instances in OrchestrationSome instances are not appearing as packages when Syncing the TDI data source in Orchestration, or when trying to create a TimeXtender Ingest/Deliver/Prepare package in Orchestration, an instance is not appearing in the dropdown. Please ensure that you have added a new execution package (other than the default execution package) in the relevant instance. Once the new execution package has been added to the instance, deploy the instance, and then try syncing the TDI data source in Orchestration again or adding the TimeXtender Ingest/Deliver/Prepare package in Orchestration manually.TimeXtender Ingest/Execution Service is not runningError: TimeXtende

Hi,We are currently using TX 20.10.80.64 in combination with TX Data Enrichment. TX DE is exposed as a source in the ODX.When we modify a Custom SQL query via Table Designer → Actions → Source, it appears that the data is not refreshed in Home afterwards. Old columns or outdated row counts are still displayed.We have configured primary keys (PKs) to define the columns in the Table Designer.Therefore, we suspect that when we call the ODX source TX DE within TX 20.10.80, the data is not being refreshed from TX DE.What are we doing wrong?

TimeXtender Exact Online Data SourceAccess and ingest data from Exact Online REST APIs using the TimeXtender Exact Online data source.TimeXtender Exact Online Data Source Authentication Setup Create an APP in Exact Set up the Authorization request to retrieve the code value to use to generate the tokens Use the code value to generate the initial tokens Find the division value Endpoints Query parameters Table flattening Other AuthenticationExact Online REST APIs use OAuth Refresh Token flow for authentication. This requires the user to perform initial steps before it is possible to set up the authentication in TimeXtender Exact Online data source. When you have generated a client ID, client secret, and the initial access token and refresh token, you can fill in the corresponding fields for authentication.NOTE: the initial access token timestamp needs to be converted to UTC time-zone and then to UNIX timestamp seconds.To find these values you need to go through a three-

Hello,Couldn’t quickly find a similar thread so I would like to ask it here.What is the best way to transfer selected objects between environments, TEST→ PROD or is it still all or nothing? We’ve integrated a new ERP system and I only want to migrate tables from this new source to PROD, not all the other changes I’ve been working on.Would be great to just select which objects I want to push to the next envrionment.

Hello, Is TX 20.10 compatible with Azure SQL. My understanding is that Azure SQL is SQL 2025 which is not supported by TX 20.10ThanksTIM

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

 Changes in TDP 26.2Previously, syncing a TimeXtender Data Integration (TDI) Data Provider created one package per environment per unique TDI package. A workspace with 18 unique TDI packages across three environments (Development, Testing, Production) would result in 54 package entries in Orchestration & Data Quality (ODQ). This caused confusion and added maintenance overhead.With this release, sync deduplicates packages by their unique package GUID. The same TDI package, regardless of how many environments it appears in, is now represented by a single entry in ODQ. The correct environment (and its associated TDI instance) is resolved at execution time.Before: 18 packages × 3 environments = 54 ODQ package entriesAfter: 18 packages × 1 = 18 ODQ package entries  TDI Data Provider — TDP OnlyThe TDI Data Provider configuration dialog is only available in the TimeXtender Data Platform (TDP) web interface.If you open a TDI Data Provider in the desktop application, you will see an "Open i

TimeXtender 20.10, colloquially known as "Classic", has been replaced by TimeXtender Classic as the bearer of the TimeXtender legacy back to the very first version from 2006.Before support for TimeXtender 20.10 ends in February 2027, we strongly recommend that you upgrade to either TimeXtender Classic or TimeXtender Data Integration. See Important information regarding TimeXtender 20.10, TimeXtender Data Integration, and TimeXtender Classic for more information.Differences between TimeXtender 20.10 and TimeXtender ClassicTimeXtender Classic has a focus on on-prem solutions based on Microsoft SQL databases, while its sibling TimeXtender Data Integration is built to take full advantage of cloud-based infrastructure such as Microsoft Fabric, Azure Data Lake, and Snowflake.Since TimeXtender Classic is designed to solve a more specific use case than TimeXtender 20.10, some 20.10 features are not available in Classic. We've also taken the opportunity to remove previously deprecated features

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

Note: Please download and install the latest version of 20.10 before migratingThe TimeXtender Migration Tool is here to assist you in the upgrade of your existing TimeXtender 20.10 (not to be confused with TimeXtender Classic) projects to TimeXtender Data Integration. This article explains how to use the migration tool.BenefitsTimeXtender Data Integration is Cloud-enabled for significantly improved scalability and usability. Some features only available in TimeXtender Data Integration include:No need to host project repositories - TimeXtender Data Integration is powered by fully managed cloud instances. Goodbye License Keys and Client Secrets - TimeXtender Data Integration now supports user sign-in and granular user permission management. Simplified Multiple-Environment management & transfer in the portal, including the Ingest instance. Cloud-based Data Source connection management - Admins can now create and share access to data sources without passing around passwords. Run PowerS

See the below screenshot.  I’ve installed Classic 26.2.1.1 and if I just put in the License Key, it tells me I need to have an activation file.  Never had to do this with 20.10.Went to download the activation file, and there is not an option for v26.  If I try a 20.10 activation file, it says it’s the incorrect version.Using the Alithya partner key starting with: 3c67…. 

Hello,Since about a month ago, I am not able to connect to Sharepoint Lists anymore. When I test the connection, I get the error message as seen in the image below. Authentication wise, I use Auth scheme AzureAD end the Sharepoint edition is Sharepoint Online. I do not use OAuth and I am able to login to the Sharepoint site with the account I use. Is anyone experiencing the same issue or does someone know how this can be solved? 

After upgrading to Ingest 7313.1 I updated my REST API provider version to 12.1.0.0. Now some of my REST endpoints have started failing.Running “Import metadata” works fine, but when it tries to extract values from the JSON, it fails with errors like: Failed to execute callback for endpoint 'Get Charge Points':Column 'data_id' does not belong to table charge-points.System.ArgumentException: Column 'data_id' does not belong to table charge-points. But it should be able to parse it.The structure of the JSON is like this (just showing top of file):{  "data": [    {      "id": 1096237,      "teamId": 449574, Any tips? 

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

Hi, I no longer have Timextender in the Microsoft Authenticator application on my phone (after I switched phones), so I think I need to have the MFA for my account reset. Can someone please help me with this?

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.  

We are getting a bad request error when we are using the timextender odata data source.  When we use the endpoints that we previously selected during metadata discovery, they still work normally. So why is the discovery metadata at the moment not working (it worked the first time). Thank you in advance!   

Hi all,I am looking for architectural advice on designing a future-proof multi-ERP data warehouse setup in TimeXtender.We currently have multiple ERP systems feeding into one data warehouse. The goal is to create a scalable pattern that works now, but also remains maintainable when more ERP systems are added later.The main question is around where and when to create keys, especially super natural keys / business keys, and where to perform the joins between facts and dimensions. I found some scattered articles on keys and stuff, but not really an proposed best practice in TimeXtender. I understand there are multiple ways to Rome depending on the setup/preferences/performance etc. but I reckon there would be an advices standard based on TimeXtender working and fundamentals. Example simplified architecture:DSA.ERP1.Customers- CustomerID- CustomerName- DW_SourceCode- SNK_Customer = DW_SourceCode + CustomerIDDSA.ERP1.Invoices- InvoiceID- CustomerID- Amount- DW_SourceCode- SNK_Invoice = DW_S

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?