Solved

Hey there, We used to have the On-Demand setting enabled for one of our data sources. With this setting turned on, the package that executes the corresponding tables would take roughly one hour to complete. Recently, we switched to a Full Load Transfer Task, followed by an Execute Tables package. However, now the transfer/ingestion process takes almost 2.5 hours (and then another 20 minutes to execute the tables). We thoroughly checked to ensure that the tables included in the Full Load are the same as those processed with On-Demand, and they are. In the logs I can see a lot of these messages (every 5 minutes), so I am wondering how much time the full transfer is idly waiting.

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.1 We 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 Server: Microsoft-HTTPAPI/2.0 Stack Trace: at Azure.Core.HttpPipelineExtensions.ProcessMessage(HttpPipeline pipe

Hi, I’m trying to add new data source provider but it looks like all of them dissapeared. Last week everithing works well. Licence is active, I using version 2.10.36.64. Any idea about the root cause?

Hello, I understand support for CData has been removed, see However, we cannot use existing drivers anymore either, as we don’t have the option anymore to add a CData Data Source via ODX. If we click on Add Data Source, we only see some standard data sources, no CData drivers anymore. If we click on Manage Data Source Providers, we do see the installed CData drivers. We use a lot of different Sharepoint connections to import certain data, and we cannot create a new Sharepoint connection now, without upgrading. How can we add a CData Data Source now? Upgrading of the client is currently not possible. This is a blocking issue! How can we still add a CData data source? Thanks, Stijn Hensen

Hi, I have a virtual machine that is currently hosting the ODX service and I would like to get my local machine up and running with TX desktop. I have installed the application but am getting an error that can be found below. I have looked through the documentation regarding this but it seems that the legacy documenation is all I can find with anything relevant. In the screen shots it is asking to review settings in the ODX tab and the Project repository tab which are non existent in the latest TX version I am using. I only see General and Customer editors when looking at Tools>options. ERROR> A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) Details: SQL Server: 'sql-instances-prod.database.windows.net'SQL Error Number: 64

I have a table (table A) with a lookup field from table B (using the default relation between A and B). This works fine. Table B is then renamed because of a spelling error, deployed and executed. Good. Table A still seems to be OK: the relationship between A and B looks fine and the data cleansing procedure (Advanced -> Customize Code -> Data Cleansing Procedure) contains table B with its newly updated name. However, table A won't execute because the deployed version of the data cleansing procedure still references table B's old name. The simple fix is to force a deployment of table A, but I think TimeXtender should have noticed that a deployment was needed (red table name). Seems like a bug to me. Legacy version 20.10.50.64 Details: SQL Server: 'my-mdw-database.example.com' SQL Procedure: 'MDW_TR.usp_table_A_Clean' SQL Line Number: 65 SQL Error Number: 208 Invalid object name 'MDW.table_B_old_name'.

Hi, I am trying yo apply the new integrated Deliver Instance variable, but get an error when deploying the instance. When deleting the variable again, de depoyment and execution succeeds. I already tried the following: Synchronizing de Deliver instance Refreshing the environment Reopening TX Deleting and recreating the variable with a different name Trying the Fixed variable instance (which gives me the same issue) Any suggestions? Kinds regards, Devin

Just recently the TimeXtender REST data source at a client was not able to be edited to the same extent anymore. When pressing “Get Schema” in the Table Flattening Table Builder, we get this error message: No changes or updates were made to the TDI, ODX, or the TX REST data connection as the error started to appear. We use this combination of versions: As suggested here: The exact TX REST version used is 7.1.0.0. If possible we would like a solution to this problem that does not require an upgrade of the TDI software.

Hi I have a REST data source that provides the desired output in CSV format. However, I'm looking for guidance on formatting the XML output to match the expected structure. Currently, the XML output I receive looks like this: <?xml version="1.0" encoding="UTF-8"?><Name_of_table> <value> "name_of_column1","name_of_column2","name_of_column3","000: name_of_column4," "G name,with comma","2000M01","Volumindeks, kalenderjustert",. "G name,with comma","2000M02","Volumindeks, kalenderjustert",. "G name,with comma","2000M04","Volumindeks, kalenderjustert",3.2 "G name,with comma","2000M05","Volumindeks, kalenderjustert",50.2... </value></Name_of_table> Is there any support for CSV responses in the Rest Connector, or do you recommend creating a XSLT file for this purpose?

Dear Sir, One of our customers wants to keep working with TX classic into the future. Question: Till when is the 20.10 TimeXtender Classic supported ? Customers have to migratie sooner of later right ? Is there a deadline ? Or is TimeXtender Classic still supported for say the next 10 years ? Hope you can shine a light on this. 😀 Regards, Arthur

We are suddenly having issues with opening last saved project in TimeXtender. The error says: An error occurred while fetching data from the database.Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints. Location: Table: SelectionRuleFieldsForeignKeyConstraint DataFields_SelectionRuleFields requires the child key values (5b2c48b9-abad-4a3b-a9b2-002fedfc582a) to exist in the parent table.. We have tried to go back to the project that we saved before the lastest one. We are able to open that it not able to save it. The errror says: An error occurred while saving the project to the database. An error occurred while fetching data from the database.Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints. Location: Table: SelectionRuleFieldsForeignKeyConstraint DataFields_SelectionRuleFields requires the child key values (5b2c48b9-abad-4a3b-a9b2-002fedfc582a) to exist

Hello TimeXtender Support, We are looking to upgrade the ODX server at the customer. Currently the ODX service is installed on the PROD server. We first want to install the new version of the ODX service on the DEV, basically run a sandbox project to ensure everything is running fine and then upgrade the ODX service on PROD. Now, I've been told by Rory that there is a change that running a newer version of the ODX service will impact the metadata in the ODX repository in a way that is irreversible. I want to make sure that we can first try the new version of the ODX service in the DEV environment without impacting the ODX repository, so we can go back to the previous situation if anything problematic pops up and don't impact PROD. My question is: can we safely install a sandbox version of the ODX service on the DEV server and have it call home without irreversibly changing our ODX repository between these two versions? ODX Service 20.10.37>ODX Service 20.10.57 Hilsen, Luuk Bouman

Hi, I am trying to set up a REST connection. Here are the prerequisites: The API delivers data for a maximum of one month, and no more than 10,000 rows at a time. I'm a bit of a beginner when it comes to the new Rest data source 🙄I wonder what the easiest way to do is to;1. Read all rows for the selected period using the fetchFromActivityId field. That field is in one of the API's tables.2. Loop through month by month until I arrive at today's date.The API works fine. It is no problem to fetch 10,000 rows from a selected period.All ideas are gratefully received 🙂 BRAnders

When running an execution and it fails in a Tabular, isn't it possible to continue executing the other tables (which are of course not a source for the failing Tabular). Now in our process the execution stops, but the tabular is just a last step for a few tables, not for all other tables.

I cannot see it in the Data Source Providers: Can you give me a setup guide?

We have a table which is guarded on deployment and on execution. When we run a manual execute on this table we get the message that this table is guarded, therefore not executed. This table is in a nightly execution and we don't expect this table will be executed because of the guard on execution. But we are dumbfounded that during the nightrun it is executed (and runs in an error). What are we doing wrong?

When launching the newly installed ODX Server configuration (20.10.45), we get the following error: First, we thought this was a Firewall issue on our (Azure VM), because this test-netconnection did not work (see the second one failing): When I try to reach that second address from my local laptop, I get the same failure. Could you explain what is going on here? When using the ‘tracert’ to timextender-api.azurewebsites.net command in the command prompt on my local machine I see that it forwards to waws-prod-am2-061.cloudapp.net. When we try to do the same on the TX Azure VM, it times out on the first step. Do you have any advice on how to proceed here? Could it still be a Firewall issue on our VM?

In the TimeXtender Classic training, I only see 4 modules, while Peter Jensen (element61) sees 5 modules. See below screenshots. We are wondering why Peter has a module named ‘Business units’ that I don’t see.

hi there After the latest update executionengine_x64 and Jet datamanager server takes 100% of my cpu .. are there anyone who have experienced the same ?

Hello, I have an Acceptance and Production environment and using multiple environments transfer. Now both servers are new and also TX is upgraded (latest version) and the connection between them seems to be gone after this. How do I setup the multiple environment again ? Just by adding an environment or can I get it back from the ‘old’ TimeXtender ? Thanks, Ronny

Apologies for vague subject but I couldn't come up with anything better. We have an Semantic Model in TimeXtender 20.10.55.64 setup with a Role, and a Row level security setup. Those two are normally ‘linked’ as required, and described in articles as Deliver Instance Model-Level and Row-Level Security | Community We've just noticed while delivering a new PowerBi app to our users that this link disappeared somewhere between deploys, giving all users read-access to all data (oops). Is there any documented reasons why this would happen? Or better yet, is there a method for RLS that would default to users not having access to ANY data at all rather than everything if this happens? Eg explicitly grant users access to data, as opposed to explicitly deny access. Thanks for any insights.

Hello, I’m looking for a query/view/stored procedure that can be used to query the data lineage / data flow. I would like to have the source to target mapping etc in a report/overview instead of in the GUI. So, I can easily report on the tables that are used to build the table in the next layer. Anyone an idea? Thank you, Gert

Dear Sir, Our client upgraded TX to version 6766.1.Now their scheduled job executions stop working.They are having an issue with thier Scheduled Jobs.Running the jobs manually works fine. Please help, is there a specific Log to check in TX to understand what is causing the issue ? Does an upgrade solve this known issue ?We have released a bug fix for this in 6698.1. Please upgrade, and see the below release notes for reference: TimeXtender Desktop 6698.1 Hope to hear from you. Regards, Arthur

Dear sir, Is it still possible to work with RSD files in TX version 6892 ? I found this link: Is it possible to do something like this with the latest 8.0 TimeXtender REST provider ? I am trying to work with an API that is refreshing there Bearer Token every hour “expiresIn”: 3600 curl -X 'POST' \ 'https://openapi.binnenbeter.nl/api/v1/login' \ -H 'accept: application/json' \ -H 'Content-Type: application/json' \ -d '{ "tenant": "horstaandemaas", "username": "*****", "password": "*****"}' { "token": "eyJwMmMi**********lRW5SWTZKaTFzb1EiLCJhbGciOiJQQkVTMi1IUzUxMitBMjU2S1ciLCJlbmMiOiJBMjU2R0NNIn0.J8cstvlbqRrWzsRulKtnBFv4eKG6r3fvudZI*********gvjw", "tokenType": "Bearer", "roles": "ADMIN, API", "expiresIn": 3600} So I have to come up with a solution that dynamically refreshes the token before it is fetching the data or else the API will deny access because the token is out of date. If you have any ideas please let me know. The plan is: What I am trying is to run a powershell script to fetch

Hi, I cannot find the option to ‘Select tables’ from the source: My TX version is 6848.1Where should I look for that?