HiOver 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 Oracl
Good Day,We have a client that is on V20 that would like to incorporate some Sensitive Data within their TX environment that some of the TX Developers should not have access to. As far as I am aware, if you have access to the TX Repository then the developers can open all projects.How would I handle the solution of the Sensitive Data in TX?Kerry
PrerequisitesCreate an Azure App RegistrationThe App Registration should use the Microsoft Graph API with the following permissions:Finding the List IDUse Postman to find the Site ID. Use the Site ID to find the List ID. You can find these by using Postman and by looking at the Graph API collection Graph Fork. You can use the app to connect to this and locate the SharePoint folder under Application. In there you have two requests, https://graph.microsoft.com/v1.0/sites and https://graph.microsoft.com/v1.0/sites/{{SiteID}}/lists. Use sites to find the site ID and use the SiteID to find the List ID. You can also find the ListID by navigating to the SharePoint list and then clicking List settings and then copying the ListID from the URL Use the TimeXtender REST data source connectionConnection SettingsUse the following Base URL (where {{SiteID}} is the Site ID found in Postman):https://graph.microsoft.com/v1.0/sites/{{SiteID}}/listsEndpointsCreate the endpoint using the following path (w
At times you may want to share a specific data source setup with someone else.Here is how this can be done.Create the project with the data source Export the project and note the version of the project Import the projectCreate the project with the data sourceLets say you have a REST data source made with the Enhanced TX REST data source provider and it needs to be shared with someone without access the the machine where TX is installed.First you note the specific data source, or sources if additional ones are necessary. Then you use the save as option.When you use this method you create a new project with the same setup the only difference is the name of it.After creating the new project there still are some things to do before you are ready to export this.First you delete the unnecessary parts such as Semantic layers and Data warehouses.Delete all execution packages, so only the default one remains.Finally you delete all the unneeded data sources and any custom tables added to your BU
Use deliver instance endpoint name variable, in combination with data selection rules, to perform different data selections for different endpoints in the same deliver instance. This way, each department can get their own endpoint with a subset of data relevant to their division. This can help improve load performance, report performance and help manage costs by keeping individual models smaller. This also helps avoid creating multiple deliver instances for different departments.How to filter use data selection rules for specific endpointsCreate a Deliver instance with multiple endpoints Close all instances in TimeXtender Data Integration and then open the Deliver instance in TimeXtender Data Integration and click Tools > Instance Variables. Then click Add, and add an instance variable of type Destination Scope, setting the Value Filter to Endpoint and setting the Value to Name. Then click OK and close. Right-click the table you would like to create filter on and select Add Data S
There is a free currency API called Fixer IO https://fixer.io/You can connect to it by generating an API key and generating an account is free.The documentation can be found here https://fixer.io/documentationThis guide is for learning how to set up a REST data source, how to generate dynamic values from SQL queries, and how to use additional parameters for your calls to get different info out of it.ContentContent Set up Fixer IO account Setup Common settings Setup Request limits Setup endpoints Latest - Gives today's rates and shows how to apply parameters Yesterday - Gives historical rates based on a specific date. Uses SQL query to dynamically apply yesterday as the date Timeseries - Gives historical rates based on a start and end date. Uses SQL query to generate dynamic dates Custom range endpoint - Use a function in DW Instance to generate a range of dates to loop through Use XLS to do table flattening Use Unpivot on your XLST Change the content of the rates to show decimal
Hi. Is it possible to move my current community account to my new e-mail address? I could not find anywhere to update this on my profile.
I’m looking for a TimeXtender Fabric Lakehouse (pyspark.sql) expert 😀I’ve got a SQL transformation that selects the maximum value of 10 columns:(select max(val) from (values ([Column_1]), ([Column_2]), ..., ([Column_10])) as [Values](val))How do I achieve this in a Prepare Lakehouse custom transformation?I could build the mother/father of all massive case statements, but I’d prefer something simpler and more elegant … if possible!?
I'm using dynamic values function in the TX REST connector 9.1.0.0. I use id's from another endpoint to loop through in my second endpoint path. This works well when I use “From Endpoint Table” but now I want to add a filter to only get the id's with a flag “hasresponse=true”.I've read the page but I still get an error with my Endpoint query. “No such table” the error message says. I've tried several things like adding a schema. But all with the same response. Is there something wrong with my syntax?Error:
Today, we released a minor version of TimeXtender Data Integration (v. 7047.1) with the changes listed below. We recommend that you upgrade if you’re affected by any of the issues fixed.FixedFixed an issue for Prepare instances using Snowflake storage where Snowflake would throw an error on deployment when using differential deployment. Deployment would fail on Prepare instances using Snowflake or Data Fabric storage if custom data was present. Custom data is only supported on SQL storage, so this issue would appear when changing storage from a SQL Server storage with custom data. It’s now possible to delete custom data when it is not supported by the storage type. For Prepare instances, fixed an issue where the ‘DW_SourceCode’ field was missing in the primary key check. For Deliver instances, updated the logic for the PowerBI endpoint connection string, so you can now use the Gateway in the PowerBI portal.
Hi,We are using a REST data source with dynamic values to fetch data for approximately 12,000 records, where each record corresponds to an individual API call.Occasionally, we encounter issues with the API provider where some calls return a 400 error. Unfortunately, it’s unpredictable which dynamic values will cause these errors.Currently, it appears that the TimeXtender REST data source stops processing upon encountering a 400 error, resulting in a "Completed with errors" status.Is there a way to configure the REST data source to continue processing the remaining dynamic values, skipping over those that result in a 400 error? Ideally, it would also log the calls that failed for review. Best regards,Pontus
I have a client that wants to explore a significant rework of their Prepare instance. They want to duplicate their existing Prepare instance in Dev to create a sandbox instance. Is there a recommended approach to achieve this? They are using version 6898.1
Does anyone know exactly what happens when we ingest data from e.g. a SQL Server into Fabric Lakehouse? It seems concurrency impacts performance (more can be less) but there might also be Fabric assets in play that could act like bottlenecks, and which requires “capacity” management.Any best recommendations/practices in this space?
I am loading a table incrementally into my ODX storage in an Azure Data Lake, where new Parquet files are added daily. This approach is because the source only holds data every two weeks, and I want to maintain a log in the ODX. The Parquet storage is very compact.However, for downstream analysis, I only need to retrieve data from the last 1 to 2 days into my prepare instance. I am using a data selection rule on the mapping, and I have also tried applying it directly on the table. Both approaches take a very long time to complete (+1 hour), whereas running the same query on the source SQL database filtering for 2 days of data completes in about 10 seconds.I suspect that the prepare instance is scanning through all the Parquet files, including older days, causing the slow performance.My question:Is there a way to configure the TX prepare instance to only process the most recent X Parquet files (e.g., the last 2 days) instead of scanning all files? This would significantly improve the se
Recently we have been running into big problems with our production repository database becoming completely unresponsive after completing an environment transfer, actually leading to scheduled executions not starting the following night.It has happened twice in the last two weeks but never before during the 3 years that we’ve been working with TX.The issue is seemingly resolved having switched to a vCore model on the production repository, but we are at a loss as to the root cause of this problem.We have of course read all the relevant knowledge base articles/community discussions that talk about why the repository may become generally slower over time (execution logs have been deleted, yes) -however, for us it has not been gradually deteriorating but suddenly. Also, we believe our projects are not that big (see below) to warrant the export-import procedure.SetupTX version 20.10.25.64 Multiple environment setup (Dev + Prod), TX running on single Azure VM and all databases are Azure SQL
When backloading very large tables it may become necessary to load a table in smaller segments or "chunks". The following instructions explain how you can configure a segmented table execution in our program using a combination of project variables, data selection rules, and Incremental load. These instructions use an example table called [OrderLines] and an example date field called [LastEditDate]. Prerequisites Configuration ExecutionPrerequisitesIn order to support this configuration, you must enable Incremental Load, so the table must have a reliable primary key and field with an incremental value that increases with each insert AND update. This is typically a ModifiedDate field, but other data types may also work as well.Configuration Enable Incremental Load on the table you wish to configure segmented table execution, in this example [OrderLines]. The Incremental selection rule MUST be the SAME FIELD used in the project variable in the next step, in this case [LastEditDate]. At
Today, we’ve released an updated CSV data source to fulfil a customer request for the updated S3 feature.CSVVersion: 23.7.3.0 (TDI) / 1.3.0 (20.10 BU) / 16.4.8.0 (20.10 ODX)Added support multiple delimiters. Added support for general S3 bucket connection.
Today, we've released a new version of the TimeXtender Data Integration Portal with the changes listed below.Fixed Fixed an issue preventing the page 'REST API web servers' from loading in some cases. Fixed an issue preventing blueprints from being shown. Fixed an issue preventing data source details to be loaded. The migration modal will now correctly remember your saved config.
Version 7026.1 - Ingest into LakehouseI’ve got a SQL data source where some column names contain spaces. This causes the TX SQL connector (23.0.3.0) to throw the following error when I try to ingest data into a Lakehouse:Executing table dbo_tx_profitcentreinfo:failed with error:Found invalid character(s) among ' ,;{}()\n\t=' in the column names of your schema. Please enable Column Mapping on your Delta table with mapping mode 'name'.You can use one of the following commands.If your table is already on the required protocol version:ALTER TABLE table_name SET TBLPROPERTIES ('delta.columnMapping.mode' = 'name')If your table is not on the required protocol version and requires a protocol upgrade:ALTER TABLE table_name SET TBLPROPERTIES ( 'delta.columnMapping.mode' = 'name', 'delta.minReaderVersion' = '2', 'delta.minWriterVersion' = '5')I can read what it says 😀 but I thought I’d ask the Community for advice. Has anyone encountered and resolved this issue? If so, what do you recommen
SYMPTOMSWhen trying to run DAX Queries using TimeXtender Orchestration & Data Quality Version 25.1 against a Analysis Services Tabular Model data provider, the query is unable to return any results and the following error is displayed at the bottom in the status window.Error in query: ExecuteQuery(): The result set returned by the server is not a cellset or a multidimensional data set.An example of this error is below.CAUSEAs of June 2025, our Product Team is looking into the cause of this error and may address it in a future release. In the meantime, a PowerShell query can be used as a workaround in order to run the DAX queries similar to the following screenshot. ResolutionThe specific steps needed to set up the Powershell workaround are as follows:1. Install the Adomd msi from here: Analysis Services client libraries | Microsoft Learn2. Create an app registration in Azure and set the clientid and client secret in Global Parameters in TimeXtender Data Quality3. In SSMS in Anal
With the TimeXtender REST data source, you can gain access to REST APIs. Many APIs have a unique setup and use a specific behavior, this article describes the settings to connect to various APIs.Connect to REST APIs with various authentication methods such as Header options, Bearer Tokens, OAuth, and similar. If the REST API contains multiple resources such as users, posts, and comments you can use it to connect to each one as individual endpoints, by providing the base URL. The data source offers pagination options to connect to each page of an endpoint. In some cases, endpoints require the input of a date or an ID from another endpoint. Configure dynamic values within the data source to handle this requirement.At the bottom are some real examples showing how to connect to some APIs everyone should have access to. Additionally, they show how to use specific options for authentications and how to use dynamic values.ContentContent TimeXtender REST Data Source Settings Connection Setting
At times your result returns data based on a date range, it could be a start and stop date or just one of each.When using a lookup to fetch data from these tables your join rule would have to be StartDate <= Date and EndDate >= DateThis is not an effective lookup and it will make the execution of this table slow.This guide will show how to make this fast by using the Date table to fill out the dates between each so the join will be Date = DateSplit exchange rates out on individual days The exchange rate table contains both start and stop date The exchange rate only contains a stop date The exchange rate only contains a start date Split exchange rates out on individual daysThere is two types of views you can create. It depends on what fields your exchange rate tables contains.In both cases you will need a date dimension. Since you most likely will use this in the DSA/Stage db, so start by creating a Date dimension.The exchange rate table contains both start and stop dateThis is
The Table builder is a powerful tool in the REST and JSON & XML data source providers that you can use to transform nested XML or JSON data into a flattened table with columns and rows by using simple drag-and-drop functionality to define XSLT code.This guide will walk you through the various features and steps involved in using the table builder.To use the table builder, you need a REST or JSON & XML data source set up and mapped to a running Ingest instance.Add table flatteningThe first step is to add a flattened table to an endpoint. Open your data source, expand the endpoint, click Table flattening under Additional configurations and then click Add. Give your table flattening a name (this will be your resulting flattened table name) and click the Open button to open the table builder interface. The table builder interface consists of 5 different sections: Input: Here, you paste in the XML or JSON you want to flatten and also select the applicable data structure for you
Hi, I have two questions regarding Orchestration, schedule groups.(1) There is the option to make a schedule based on a SQL custom script. When I try to test this functionality out with the following statement:SELECT CAST('2025-06-10 01:00:00' AS DATETIME)It gives me the following pop-up: Does someone know why I don't get query result = '10-06-2025 01:00:00’? The SQL statement produces a valid datetime value in SMSS.(2) I need to schedule a job that runs four times per day for a project. I wanted to build this schedule with the custom SQL option and by using a calendar table in our database from the Prepare Instance. Is this possible? Thanks in advance!
One of the most powerful advantages of the TimeXtender software is how it uses project metadata to "remember" all of the objects in a project and their relations to one another. Another of TimeXtender's strengths is its ability to incorporate customized SQL code wherever the native functions are not sufficient to accomplish a task. Through the use of script parameters, both of these advantages can be combined.What is a script parameter? Creating a parameter Understanding parameters Mapping or renaming parameters Viewing your parameters Removing parameters Manual delete Automatic removal Limitations of script parametersWhat is a script parameter?A script parameter creates a link between the script and a TimeXtender object. This link has two primary benefits. One benefit is that the link includes parameterized code in data lineage and impact analysis, and enables the application to automatically manage some object dependencies.The other main benefit is that the the parameter replac
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
