Recently active topics

Hello, We have currently set up a hybrid environment for our TX deployments. A DEV environment in on premise MSSQL database and test and prod in Snowflake. I have already come across situations like hashing where the built in functionality is not usable in Snowflake and if you create a custom field with a hashing algorithm it is not possible to deploy from MSSQL to Snowflake becuase of the different language required to create the hash. I have also com across this when writing custom scripts. In those cases so far i have been able to create code that works in both environments. Is there any way to handle this more effeciently when running a hybrid set up like this? We are trying to reduce unneccessary costs in Snowflake during development hence the hybrid set up. I have read some things about Instance variables but it would be great if there is some kind of best practice in a set up like this.

Hi all, Does anyone have experience with or managed to do a “dynamic” kind of flexi multi key join in TimeXteder? Example like this --- a.[BUYER_GROUP_CD], b.[BUYER_GROUP] FROM [DSA].[SYNAPSE_SILVER] a LEFT JOIN [DSA].[XLS_PURCHASING_GRP] b ON a.[BUYERGRP] = b.[BUYER_GROUP] OR ON a.[BUYER_GROUP_DESC] = b.[BUYER_GROUP_ID] OR ON a.[BUYER = b.[BUYER_GROUP_WORKSPACE_ID]

Hello, We have a case in TimeXtender Classic where we need to read more than 256 Columns from the Excel connector. My understanding is that the underlying driver does support it, but by default it will only Return the first 256 Columns, and thus that is all we see when reading objects from the DataSource. Does anyone know if there is a way to expose more columns beyond the 256 already shown? Thanks Tim

Designating a field as “raw-only” allows for the field to be hidden from the valid version of the table but still available for use as the basis for other fields, which can help streamline the valid version of the table. As the name implies, a raw-only field is a field that only exists in the raw version of the table and not the valid one. Raw-only fields will not be displayed in other Data Areas or Deliver instances that only use the valid part of the table. Hiding a field from the valid version of a table can be appropriate for fields that have no other purpose than to be part of other fields, e.g., used to create a surrogate key for dimensional modeling. Use the following steps to designate a field as raw-only: Right click the field and click Raw-only field. Raw-only fields are displayed with an “R” in their icon. Raw-only fields cannot be added when dragging fields from one data area to another. Raw-only fields also cannot be added when attempting to drag fields to a Deliver instan

Hello, Our data source owner team needs to close their Synapses behind the firewall to close the Prisma Clouds alerts. Therefore they are collecting all the IP ranges needed for different access scenarios, like Zscaler IP ranges for getting access from VPN/Zscaler. TimeXtender is the only solution outside Azure resources in their eyes that needs to access the data.So we need to listed those ranges. Do you know where to get these ranges for TXD cloud portal,? Or I was understanding it wrong, it is just the IP that hosts Ingestion server connection? Thank you in advance.

Hi everyone, I’m working with TimeXtender Data Integration version 6848.1 and my ODX storage is an Azure Data Lake using Parquet format. When I trigger a new reload from the source to the ODX (which should create a new incremental file in the background), I get the following error: The table folder 'x' is used by another table with the id 'y' I found this article that describes the issue: The table folder is used by another table The suggested solution there is to delete the existing folder in the data lake. Unfortunately, that’s not an option in my case because the source system only holds two weeks of data, while I have built up historical data in the data lake that I cannot afford to lose. This means every time I run a reload, the process fails as it tries to create a new incremental file for that table. Has anyone encountered this scenario and found a workaround that does not involve deleting the existing folder? Is it possible to remap the table or adjust the configuration so the

I just upgraded TimeXtender to the latest versions for a client. (7017 and 7047). In doing so most of the datasource stopped working unless I upgraded the datasources to the latest versions. I decided that I should just do them all to be consistent. This has broken my CData Rest sources because the new drivers are not installed! This is a massive issue, and i was not warned in any significant way about this particular issue in the upgrade. I need to get the new CData drivers, I am not in a position where I can transition multiple CData Rest sources as part of an upgrade! This is a production issue and I need to resolve it ASAP!

Hi, We're observing strange behavior with the new enhanced REST data source provider. When we do the call on this endpoint in the old connector or in Postman, we get a return of 197 records. This is a single payload, 1 page, with fully filled rows, including a populated PK field. Now, when we do the same call with the enhanced REST data source provider we receive 589 records. 392 of these have null values on all records except for one field, a descriptive but not otherwise important. Importantly the PK field of these records is also null. Now we have two questions: Why is the new REST provider delivering more records than other providers/tools? How can we effectively filter out these records in the actual call? As it seems we are now only able to successfully filter out these almost empty records at the DSA. Best, Luuk

Once you have set up your data warehouses and business units and established connections to the sources you want to use, it is time to start designing your data warehouse. This involves transferring data from the source systems to the data warehouse(s) via a staging database or ODX and applying transformations and data cleansing rules along the way. It is common to set up more than one Data Warehouse to accomplish all of the transformations needed to get your data into the single form of truth that will be the semantic layer. The first data warehouse is normally referred to as the Data Staging Layer or DSA. This is the first layer where data from your data sources is first loaded, and where you want to make sure all of your primary keys, data types, and incremental loading rules as appropriate are configured. The second data warehouse is normally referred to as the Modern Data Warehouse or MDW. It is in this layer where the more complex transformations, lookups, and inserts are impleme

Hi In an effort to resolve intermittent ODX errors whilst retrieving data back from Oracle JDE tables I am trying to understand whether reducing the ‘concurrent execution threads’ setting in the Oracle data source connections could be a potential solution. I have multiple Oracle connections set up in TX, with each connection pulling a subset of tables (e.g. all the JDE master file tables in one connection, all the transaction-related GL tables in another etc). All these connection transfer tasks are then wrapped up in a TX job scheduled to run each evening. The ‘concurrent execution threads’ default value across all the Oracle data connections I had set up for this was ‘8’. My thinking was that if TimeXtender is running multiple data pulls simultaneously then this could be causing resource contention issues on the source Oracle server, and thereby intermittently triggering data pull failures with generic error messages that don’t precisely indicate root cause. I have since changed the

Hello, Since the TimeXtender Classic (V25) was announced to be released by the end of Q2 2025, i would like to ask if there is a clarified date when the release is planned. To my knowledge it has not been released as of yet? Also the more important question to me is the upgrade process. Currently we are using TimeXtender classic together with ODX server and we have couple of questions: Will there be a detailed guide released on upgrading older TimeXtender platforms (20.10.52 in our case) to Classic V25? What will happen with all the data sources in our ODX instance? Since we are using quite some CDATA providers - does it mean we will have to manually recreate the data sources? Or ODX will be deprecated and we need to move to using BusinessUnits? Thanks for the information

In TimeXtender, the synchronization of data sources and objects is necessary to ensure that the Ingest Instance metadata matches up with that in the data source. Synchronization can be performed either as a task for the entire data source or on specific data source objects. This article describes the difference between the synchronize task and synchronizing objects in an Ingest Instance, and when to use each feature respectively. Synchronize Task The synchronize task on the data source level synchronizes the structure of the source with the metadata stored in the Ingest Instance. For example, if a column is added in the source, and the Ingest Instance is configured to include all the columns from that data source table, then executing the synchronize task will ensure that the column is also added to the Ingest Instance metadata. Furthermore, when the transfer task is subsequently executed the new column will also be included. If a column is renamed in the data source, then executing th

Dear All, We have a “Dynamics Business Central (NAV)” data source with multiple adapters (multiple ERPs). We recently needed to “synchronize” the object to get the last BC evolution (new fields, ...). Unfortunately, the “Display name” of some tables/fields changed. 😒 Ex: -“Lot” “Lot No_ Information” table is now named “Lot No. Information” -“Demand Forecast” “Production Forecast Entry” table is now named “Demand Forecast Entry” Our default was to use “Display Name” (instead of Database Name) in the data selection and staging deployment. Our main concern is our significant number of sql views associated to these selected tables/fields with “hardcoded” name. We know that is recommended to use parameters to avoid problem with renaming but we didn’t implement the params in this case missing time and practicality with the sql code. 😥 Do we have an alternative solution without significant adjustments in our tables/fields selections and associated staging sql custom views ? TXT version: OnP

To configure the Incremental loading of Multidimensional Cubes do the following: Ensure the destination SQL Server is an Edition that supports Table Partitions Configure Table Partitioning on the Cubes source (Data Warehouse Fact Table) Edit the cube and select Incremental Load. Once configured, Incremental loading of the Cube is handled in the following way: Loop over cube partitions. Based on the DW_PartionKey, search the physical partitions for a partition that matches the cube partition. If no matching partition is found, process the cube partition to be sure it has been processed. If a matching partition is found, compare the max value of the DW_TimeStamp for the physical partition with the last updated timestamp for the cube partition. If the DW_TimeStamp value is greater than the last processed timestamp for the cube partition, process the cube partition.

TimeXtender scheduling is designed to work by day or by week. While it is very flexible and powerful in that context, sometimes certain jobs need to be run at larger time intervals, such as monthly or yearly. An example of this kind of package would be a monthly full reload of the environment. While TimeXtender does not natively support this kind of scheduling, it's possible to get the same functionality through the use of project variables and execution package conditions. This method works by scheduling the execution package to run every day, but only give it permission to run at the desired interval. Setting up the Project Variable Setting up the condition Other considerations Setting up the Project Variable To set up a project variable, you will need to determine what you want your schedule to look like. A common requirement might be to run an execution package on the first day of the month or the last day of the month. We will then need to design a query that will return a fixed v

In the Deploy & Execute steps window, there is a checkbox called Script all objects. For debug purposes, you can check this checkbox to make all parts of the SQL script, which was created during deployment, available in the log. You can view the log by clicking on the View Log button. The checkbox is needed because TX uses Shared Management Objects (SMO) to create tables instead of just executing CREATE TABLE statements against SQL Server. The drawback is that all the statements that were executed through SMO are not in the log. Viewing the log may show something similar to the following. You can click the Word Wrap at the bottom to make the script fit in the window horizontally. You can also copy and paste the script into a support ticket for our review should there appear to be an issue with the deployment and execution.

In TimeXtender, you can add conditions to execution packages. These conditions must be based on a project variable. A common example we will use to illustrate this feature is preventing a nightly load from running in the development environment. To add the condition, right-click on the execution package and select Add Usage Condition. Select the project variable you want to use from the list of project variables. Select the comparison you want to use from the Operator dropdown. In this case, we'll use NotEqual. Select the data type of your project variable from the Comparer dropdown. Because EnvironmentName is text, we'll use String. In Value, we'll type in the name of the environment we want to prevent the package from running in. Click Add to create the usage condition. Now you can see the rule applied on the condition in the Usage Conditions area and under the execution package itself Be sure to save your project as a deployed version for the changes to take effect.

Hi, I've got a couple of installations with customers using CDATA for AD/Entra integration, with the upgrade I found an article to advise moving them to REST. I am however a bit lost on how to connect a REST API to Entra, and I couldn't find good documentation to fill it in. Could someone assist us for a moment or maybe point us toward more complete documentation specifically on using the Enhanced Data Source to connect to Entra? Thanks in advance, Jan DD

Hello Timextender and community I’m looking to understand how Timextender Classic deals with collumn statistics that aren’t tied to indexes. Our project is built on Azure SQL DB. Obviously TimeXtender automatically rebuilds indexes as part of its data cleansing procedures. However, rebuilding indexes only updates statistics on the indexed columns—not on the rest. Performance relies heavily on accurate statistics for query optimization (especially when MAXDOP isn’t explicitly set), this leaves me wondering: Does TimeXtender have any built-in process or configuration to update statistics on non-indexed columns? If not, are there recommended best practices for managing these statistics in a TX solution—either as part of the deployment or as a post-process step? After dealing with a sudden drop in performance, we’ve observed performance improvements after manually updating statistics in the entire project. This takes 16 hours though, so I’d like to ensure we’re not missing any built-in cap

Snippets Snippets are reusable parameterized pieces of code that can be used in field transformations as well as other parts of your project that incorporate code. Snippets allow developers to write a section of code once and then use it in various parts of the TimeXtender Data Integration solution wherever appropriate. Snippets not only save time but can also simplify the maintenance of code should any changes in the future be needed to it after it has been deployed. Snippet Categories SQL SSAS Multidimensional Qlik Adding an SQL Snippet The steps to create a snippet are similar for the various snippet types. The following example of creating an SQL Snippet illustrates the process of adding a snippet. On the Tools menu, click Snippets. The Snippets window appears. Click Add and click SQL Snippet. The Create SQL Snippet window appears. In the Name box, type a name for your snippet. (Optional) In the Description box, type a description of what the snippet does. Enter the script in the F

Hi Over the weekend one on our ODX jobs failed with the following error; Executing table [PRODDTA].[F0101]:failed with error:Oracle.ManagedDataAccess.Client.OracleException (0x80004005): ORA-50000: Connection request timed out at OracleInternal.ConnectionPool.PoolManager`3.Get(ConnectionString csWithDiffOrNewPassw, Boolean bGetForApp, OracleConnection connRefForCriteria, String affinityInstanceName, Boolean bForceMatch, Boolean bAsync) at OracleInternal.ConnectionPool.OraclePoolManager.Get(ConnectionString csWithNewPassw, Boolean bGetForApp, OracleConnection connRefForCriteria, String affinityInstanceName, Boolean bForceMatch, Boolean bAsync) at OracleInternal.ConnectionPool.OracleConnectionDispenser`3.Get(ConnectionString cs, PM conPM, ConnectionString pmCS, OracleOpaqueString securedPassw, OracleOpaqueString securedProxyPassw, OracleConnection connRefForCriteria, Boolean bAsync) at Oracle.ManagedDataAccess.Client.OracleConnectionInternal.OpenInternal(Boolean bAsync) at Oracle.Managed

Hi! recently I helped a customer who was changing IT providers with installing their TimeXtender in the new environment. At this moment when executing a table they get an error message saying the following: Cannot find the object "O_BAE_BTW_CODES_R" because it does not exist or you do not have permissions. Details: SQL Server: 'ohs-sql1' SQL Procedure: '' SQL Line Number: 2 SQL Error Number: 1088 This concerns a table in the DSA layer of their TX environment. And is a table that does actually exist when we check the database in SSMS. The error message appears on the following step: Execute DSA dbo.O_BAE_BTW_CODES ODX transfers Permissions have been checked multiple times, the concerned user accounts have db_datareader & db_datawriter privileges at the very least.

There are a number of ways to initiate an execution in TimeXtender. Each kind of execution is handled in one of three ways. Understanding the way the executions are run can be helpful when trying to troubleshoot execution problems. Manual Execution Scheduled and command line executions Multiple environment transfer and remote control execution Notes on recovery Manual Execution The most basic kind of execution is to simply start an execution by hand. This can include right-clicking a table or node and selecting execute, dropping a table into the execution queue, or manually starting an execution package. TimeXtender runs these execution packages through the application you currently have open. If the application crashes or is forced closed, this will cause the manual execution to fail. When you run a manual execution like this, the default execution package is used. A requirement is that it has no selected tables. Its setup will be used whenever a manual execution is started. Scheduled