TimeXtender Desktop Q&A

I am trying to replace the CDATA Dynamics365 adapter with the TX REST connector (8.0.0) and I am having some issues where empty values from the API is interpreted as empty strings rather than NULL and as a result creates tables with incorrect datatypesHow do i set up a way to replace these empty strings with NULL values and keep the correct data types as wellI have tried with various combination of “Search and replace" on the endpoint as well as the individual nodes in the table builder without any luck.I also have the “Empty fields as null” option enabled.  

Dear Sir,In TX version 20 you had a configuration setting Direct Read.I cannot find this setting in the latest and the greatest version in TimeXtender.Question: Is Direct Read still available ? How can I set this up ?Thanx in advance for looking into this. The "Direct Read" option in TimeXtender is particularly useful in scenarios where you need to transfer data between different data areas within the same physical database but using different schemas. Here are some specific scenarios where you might use the Direct Read option:  Large Data Volumes:  When dealing with large tables, Direct Read can be more efficient as it allows for direct data transfer within the same database, reducing the overhead associated with external data movement tools like SSIS or ADO.NET.  Incremental Loads:  Direct Read is beneficial for incremental loads where only a subset of data needs to be transferred based on specific criteria (e.g., timestamp or modified date). This can help in optimizing performanc

This is the error I am facing when executing any Prepare package (no issue with executing Ingest packages) from the Orchestration portal: ​​​​​​Error I have tried resolving the problem with troubleshooting below, but I still get the same error:  Suggested troubleshootingAny further suggestions on how to handle the issue?We run Data Integration 6935.1 and Ingest 6935.1 Thanks

Hi All, Hopefully you can help me with this one. We have a source table from our POS systems containing sales transactions. There are a few value columns we transfer that are stored as a money data type and we see some weird things happening with the values of the columns. Differences of 0.01 up to 0.0001 are appearing from nowhere in the transfer from ODX to DWH and i don't know how this i happening.The columns that have money data type are called ‘Bedrag', ’Korting’ and ‘NettoBedrag’ Take transaction 52. In the source the values are like this: After transfer with ODX, i looked in the parquet file using ParquetViewer and that looks like this: Still the same, nothing wrong here.I imported the table without any modifications in TimeXtender and it looks like this: After a transfer the data looks like this: If you look closely we lost 0.0001 on the first record ‘NettoBedrag’. Also wel lost 0.0001 on the Bedrag of the second record.I've tried a few things to mitigate this. Different numeri

Dear sir, Our client wants to upgrade to the latest and the greatest of TimeXtender.Right now they are on TX version 6766.1.So they have to migrate their CData datasources to the new TX datasources.Question: Is there a ‘datasource migration-tool’ to help them with that ?Or do they have to setup/configure the new TimeXtender datasources manually ?Hope you can shine a light on this.Regards,Arthur

Hi,I'm using the TimeXtender CSV Data Source provider and was wondering if it's possible to combine this provider with either incremental load settings or history settings. I’ve tried enabling incremental load—both in the ODX and by setting the table as incremental in the first data area—but I receive the error: "The provider does not support incremental load."Interestingly, I don't get the same error when I set the table as a history table instead, but when I try to execute the table, the result is empty.I'm wondering if this could be due to incorrect natural key configuration from my side, or if the CSV provider simply doesn't support historical loading.Any clarification would be appreciated. Thank you!  

The Get Schema function is not working for the REST endpoints / table flattening. I am trying to use version: 8.0.0.0. I get the following message: Any ideas what is happening?

Hey everyone,I have the following question:Is it possible, at the database level, to set the primary key to the one selected in TX (e.g., "Umkod_ID") instead of the default "DW_ID"?The issue arises because we access our table via PowerApps, and since the app existed beforehand, references in the code were already predefined. Currently, the app's primary key is set to the "Umkod_ID" field of the table. However, in our database, the primary key is set to the system field "DW_ID." Since this table is only loaded once and no transformations occur, the system fields are not particularly important to us in this case.We resolved this issue by manually populating the table, but I am curious if anyone knows a workaround that could be applied to similar cases in the future.

I’ve an Azure storage account with a blob Container that has folders and files. How can I configure a data source to use it?  

I use the CSV provider to load a folder with multiple CSV files. I know one of the files has 17471 rows. Only the ingest task only loads the first 14521 rows. I don't have any filtering in the ingest task.Does anyone know how I can load the full file?

I am extracting data from the MS Graph API using the REST connector in TimeXtender. The issue I am facing is that I can easily retrieve the members of the groups but unfortunately, the GroupId is not included in the Query and I do not see any way to include the {id} parameter into the saved results.If anyone has solved this, can you please help with some information on how to solve this?

Have anyone an example on a successful connector regarding a normal Active Directory - not Azure AD.Can’t find any information about it but I guess many have done a connection using TX for that. RegardsAnders Bengtsson

We have trouble with an endpoint in a TimeXtender REST API data source using the Override Headers functionality. The problem arose when we upgraded our TX software to the latest version of TDI/TIS and TX REST from 6848.1/6848.1 and 7.1.0.0.We get this error message: “Failed to execute request for endpoint 'NBABIItemWS'.HTTP Status Code 401 UnauthorizedResponse body:<error xmlns="http://docs.oasis-open.org/odata/ns/metadata"><code>Unauthorized</code><message>The credentials provided are incorrect</message></error>” We use the Override Headers functionality to limit page size for the particular endpoint. It seems that for some reason the authentication token is overwritten when using this feature, and there fore we can not authenticate. We have plenty of other endpoints in the same data source not using Override Headers, and those are working fine, so we suspect that the issue has to do with that setting. We use this combination of versions:  Is there

This is my JSON{ "projectNumber": "123456", "name": "TX", "addendumValues": { "addendumGroups": [ { "addendumGroupName": "G1", "rows": [ { "columns": { "revnr_G1": [ "Rev.1" ], "date_G1": [ "2023-06-21T00:00:00.0000000" ] } } ] }, { "addendumGroupName": "G2", "rows": [ { "columns": { "revnr_G2": [ "Rev.1" ], "date_G2": [ "2023-06-21T00:00:00.0000000" ] } }, {

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.1We 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 

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? 

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. 

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?

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 | CommunityWe'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