Solved

When having an historic snapshot table in TimeXtender MDW, based on a table insert, I need to limit the table somehow to prevent it from growing too large. I want to limit the [Date] field for only 1 year of data. Because it's based on a table insert, there are no fields available in the table to use for a table “Data selection rule”. I can only place a data filter on the table insert which only has data of 1 day. My historic table works like this: Actual table (snapshot of today) Historic table (table insert, daily, of actual table, so it stacks up the daily snapshots) (TX version 20.10.43.64)

I have a job that reloads a DWH instance that seems to be stuck on ‘Active’. This job is months old and may have been killed by a VM being shut down automatically. This job blocks executions with a ‘Job already queued’ error. Is there any way to remove this from the queue?

I'm using a FireBird database connection over ODBC. Syncing gives me the following error: System.ArgumentException: Column 'TABLE_SCHEMA' does not belong to table Tables. There is a column TABLE_SCHEM (no A). Can I override this somehow? Key Value Is Sensitive Schema Name TABLE_SCHEM false This does not work as additional option in the Data Source TimeXtender Desktop 6536.1 Kind regards, Thijs

Hi, One of the improvements of the that is stated for this update it says the following for the tabular model. “We've improved the Tabular model generated by the Tabular semantic endpoint to have better efficiency and reduce the size of the model.” Could you elaborate a bit more how it is more efficient and how you reduced the size? For us the size is especially important, since we have a 16gb limit with our ssas. Could you elaborate if you changed the encoding hints, since I do not assume you are changing any datatypes or something like that. Or did you guys mean that the processing of the tabular model has been improved, and the size it takes during processing has been reduced? In any case, I wrote another question regarding Tabular model size, and DirectQuery mode. Maybe here the timextender team or anybody else can give guidelines / best practices to reduce the size of the Tabular model as much as possible.

I have setup an Execution Package and am running a number of Perspectives in the order they need to build in the project. I then call 2 External Steps, which are Execution Packages in other TX Projects in the same environment. I am having an issue where when a step fails in the project, the build then continues onto the External steps whereas I would like the entire package to fail. I thought this would be accomplished by selecting the FailPackage action on Failure Handling but it is not working. Do I need to set this up a different way to get this to work? (I have hidden sensitive data in my screenshot)

I want to display data from my local SQL Server in the Report section of Exmon DG’s web interface. I have installed Exmon Gateway on my local machine which I want to connect to and created a Data Provider for the database I want to access. I can access this Data Provider through the Exmon DG Desktop and data is displayed in the report as intended (marked green). Exmon DG Desktop Exmon Gateway In the Exmon DG’s web interface, however, I get the following error message: Error message Exmon DG Web I have tried using ./computer name/localhost/ip address as Host Name in the Data Provider but I still get the same error. Any ideas on what might be the issue?

In many of the tutorials for dealing with specific types of APIs reference is made to internal variables like {TX_CurrentPage} and others that can be leveraged to implement things like pagination. As far as I can find there does not seem to be a list of such items and what they do. Could this be made available?

Hello, I have a data export object/task. I have created an execution package that runs this export. When I start this execution via a schedule it fails with this error (table does not exist): Execute ReaturnPortefeu:Info:Initialized -Execute ReaturnPortefeuExecute Data Export Table ReaturnPortefeu vw_ReaturnPortefeuille_Export:Info:Initialized -Execute Data Export Table ReaturnPortefeu vw_ReaturnPortefeuille_ExportFill Data Export Table 'vw_ReaturnPortefeuille_Export':Error:Failed -Fill Data Export Table 'vw_ReaturnPortefeuille_Export' 'Failed' The table vw_ReaturnPortefeuille_Export does not exist! When I start the execution manually (right click and execute) it works without issue. Execution log The source table for the export is a view: Source table Why does it fail when scheduled and not when run manually?

Hi team, TimeXtender allows adding parameters from a different table to a custom field in a semantic data model (Qlik). The resulting syntax/qlik script combination is always broken. When using adding a custom field parameter from a different table, TimeXtender fully qualifies the Qlik syntax regardless of the settings. The resulting syntax on the Qlik side will no longer match the syntax in the views created by TimeXtender: Qualified setting: Fully qualified setting: The resulting Qlik Script: "Sales_Targets":LOAD"KPI", "Target", "DIM_Boekdatum.DayName" AS "Test";SQL SELECT"KPI", "Target"FROM "Test"."dbo"."Test QVD_SLQV"; But the view has the following syntax: CREATE VIEW [dbo].[Test QVD_SLQV]-- Copyright 2011 timeXtender a/s-- All rights reserved---- This code is made available exclusively as an integral part of-- timeXtender. You may not make any other use of it and-- you may not redistribute it without the written permission of-- timeXtender a/s. ASSELECT [KPI] AS [KPI] ,[Target] A

Hi I am trying to use ADF to connect to a on-premise SQL Database with some very large tables for transfer. I selected the Azure Data Factory - SQL Server (14.0.0.0) as the source and created the datasource. When I tried to Synchronize the ODX source in TX desktop (6521.1) I got the error message that the assembly for the provider is not installed. I cannot change the provider without creating a new data source (product enhancement request!), Do I need to upgrade the TX Desktop to get access to the drivers? Or is it some other install that I need to do? I cant find any documentation on this.

I’m using Timextender version 6521.1 and I get an error when using hard deletes on a incremental table. If I choose no deletes it works just fine, soft deletes also throw me and error. As far as I could tell from these notes incremental loading should be fully supported. Things I have checked: Primary key on the table in the ODX Incremental load is setup in the ODX Incremental load is setup on the Snowflake table. I’m not quite sure if this is just a bug or I missed something obvious. This is the first table i’m trying to load incremental in Snowflake. This is the error it throws at me: System.AggregateException: One or more errors occurred. ---> Snowflake.Data.Client.SnowflakeDbException: Error: Error parsing the parquet file: Invalid: Parquet file size is 0 bytes Row 0 starts at line 0, column If you would like to continue loading when an error is encountered, use other values such as 'SKIP_FILE' or 'CONTINUE' for the ON_ERROR option. For more information on loading options, please r

Hi, We have been using ADF for transferring data from our ODX storage account to Azure SQL database for a long time but now our manual and scheduled reloads get stuck in ADF. It looks as if TX does not pass the runtime to ADF. This is required because our storage account is behind a private endpoint so we need to use an IR that resolves in our VNet in Azure. Do you have any idea why the runtime does not appear on the pipeline? As you can see there is no runtime assigned to this run: Normally the runtime appears in ADF: We are on TX 20.10.45 by the way. Would love to hear from you!

Hi I wanted to verify what I am seeing as recent changes to the TimeXtender Portal data source definitions. I distinctly remember being able to switch how a data source was being used to upload data to the ODX whether it was going to use AD).NET or ADF. If I selected ADF then I had to enter the ADF credentials. This seems to have disappeared in recent changes. I was using CDATA REST API connectors, I can no no -longer switch between transfer methods without it seems defining new connections. Can someone confirm this and let me know how I can switch between these transfers without creating new data sources?

Hello, We are currently utilizing the new TimeXtender REST API 6.1 and leveraging its built-in paging feature to connect to an external REST API. We're not using an RSD configuration for this setup. I've encountered a challenge with pagination, specifically with the use of a parameter named "Cursor." This parameter is critical for the pagination logic in the API we're connecting to. Each row in the data returned by the API has a unique Cursor value, but for pagination purposes, only the first Cursor value from the current page should be used in the subsequent POST request to fetch the next page. Here’s how we've set up the Cursor parameter: Name: cursor Type: XPath Value: /TX_Autogenerated_Root/TX_Autogenerated_Element/data/arTransactions/edges/cursor The issue arises because I need to ensure that only the first Cursor value from each fetched page is used in the pagination post body for the next request. I'm unsure how to configure TimeXtender to utilize only the first Cursor value for

v20.10.35.64 I just noticed there’s a bug in the current version of our ERP related to the UpdateDate & UpdateTS field which impacts incremental loading. Hence, I'm investigating the possibilities to set up a semi-incremental loading infrastructure. With my TX version I can also set up the following, which is limited: My database has data ranging from 2013-today. I'm looking to find a way to load 2013-2023 just once and then only full load the data with a UpdateDate >= 01-01-2024. I'm thinking to achieve this the following way: Set up a Query Table for every table where UpdateDate >= 01-01-2024. Set up a Load task, LOAD_FULL which has the original tables Set up a Load task, LOAD_INCREMENTAL, which has the Query table with just data from 2024. Execute the LOAD_FULL task just once. Schedule & Execute LOAD_Incremental every 30 minutes. If I do it this way, it's not a classic incremental loading process. Can I still utilize TimeXtenders ODX/DSA incremental loading functionalities this way?

I'm trying to connect to an InfluxDB source, where a POST request is expected, including flux script in the body to filter data. The output is in CSV format. I have this working in Postman, but how should I configure this in TimeXtender? Anything I try results in the error below, which also means no RSD is generated. [500] Could not execute the specified command: HTTP protocol error. 405 Method Not Allowed

Dear community, Is the only way to connect the ODX server to an Azure DB still on SQL Server authentication?No Windows or Azure integrated security yet? Thanks! = Daniel

Hi, I'm using the TimeXtender REST Data Source (5.0) and trying to set up pagination.Right now the relevant table from the data source contains 3999 rows.However the table should contain 4092 rows. In the API documentation I couldn't find a XPath or a header containing a link to the next page.Could someone help me with configuring the pagination in the portal. (maybe by looping over the max row count) Thank you.

When choosing a execution job, just a single execution job, it’s grayed out and I’m not able to choose it.it’s deployed and the execution jobs works, when I run it manually. I’m running Timextender version 6590.1

Hi, I was wondering if it is possible to reference to the content of local file on the ODX server from within a RSD file. Such as Get-Content with Powershell. We have some RSD files for some of the api’s call that we are making. We are in the process of including these RSD's in our own source control system in order to keep track of the changes that we do with the RSD files. One of the api's is quite unstable and sometimes needs tweeking in the rsd file. (Source control on the RSD file's / powershell scripts files could be another topic to be honest). Anyway, we have to include an API key in the script that we would not like to have saved in the source control. Therefore, an option to reference a file in which we can store the API key would be great. I know that you can also include authentication in the portal, but we are looking to maybe avoid putting credentials as much as possible in the portal. The portal also creates a OAUTH map if you use OAUTH in the portal. But I don't know ho

Hi guys, We are creating a users table in Timextender based on Active Directory. However, there’s also an on premise Exchange server, adding Exchange attributes to the user in Active Directory. But it seems we cannot read these attributes. We use the CData Provider for Active Directory in our ODX server. When trying to add the fields, the Exchange attributes are not in the list. How can we add these attributes? Do we need the CData Provider for Exchange? If so, has anyone set that one up and is willing to provide more details? Or how can we manage to import all the Exchange attributes in our user table? Thanks! Stijn Hensen

Hi everyone, I am adding a new data source to ODX, this connection has to load 6 cvs files from azure storage, could you help me to create the connection? Thanks Ignacio

Hi all, I have v20.10.45 running in Azure with ODX server running for a client. We have about 15 ODX datasources. The synch/loads run daily and the server has been up for about 9 months, so no extraordinary amount of logging I think. The issue that I’m having is that it’s not possible anymore to check the execution logs of some ODX task runs. The popup doesn’t appear and TX goes into a “Not Responding” state. Any click in the client will crash the application. This happens when I have no TX project opened, only the Manage tab for ODX server (see screenshot). I’ve upscaled the VM from DS2v2 (2 core, 8GB) to D4S_v3 (4 core, 16GB), but this doesn’t change it. Restarting ODX server also doesn’t help. The issue is not with all tasks. Tasks for which all recent executions are successful will show the logging. Checking the event logging at ODX server level will crash and tasks with a lot of recent failures also crash. Edit 1: A connection that has this logging issue is a connection using the

Hello dear TX Community, We want to load tables from our ERP System, and we are encountering the following error: HRESULT: 0xC0010006. This error indicates that the name of the SSIS Package created is too long, and we need to shorten it. I've attempted to shorten the name by modifying the schema name we agreed upon, but this would only be a temporary solution as there are more tables with longer names. For your information, the package name typically consists of the following parameters: connector name - schema name - table name - SSIS-ID, for example, sql91_DBTest_zzdomAG_DBTest_dbo_SalesAppointment_3d5329a2-54ab-42a1-9126-4c21d569131ce. Now, I have the following questions: 1. How can I manipulate/shorten the package name apart from changes I can make to the connector name and schema name (in TX)?2. Is the SSIS-ID always generated with the same string sequence, and is there a specific use case behind it that requires the ID to be formatted this way? kind regards Faras E.Nazeri

Hello, We are looking to implement incremental data fetching from REST API endpoints, specifically by dynamically filtering with an updatedAt parameter. The goal is to use the maximum updatedAt value previously fetched from each API call, which is stored in our ODX tables. While I'm aware of the capability to use dynamic parameters based on endpoints and queries within TimeXtender, I'm struggling to find a method to reference the maximum updatedAt value already loaded in the ODX tables for this purpose. Has anyone implemented a similar dynamic data fetching mechanism in TimeXtender? If so, could you share how you managed to reference data from the ODX tables to set the parameters for the next API call? Thanks!