Data Sources Q&A

Hello,Since about a month ago, I am not able to connect to Sharepoint Lists anymore. When I test the connection, I get the error message as seen in the image below. Authentication wise, I use Auth scheme AzureAD end the Sharepoint edition is Sharepoint Online. I do not use OAuth and I am able to login to the Sharepoint site with the account I use. Is anyone experiencing the same issue or does someone know how this can be solved? 

After upgrading to Ingest 7313.1 I updated my REST API provider version to 12.1.0.0. Now some of my REST endpoints have started failing.Running “Import metadata” works fine, but when it tries to extract values from the JSON, it fails with errors like: Failed to execute callback for endpoint 'Get Charge Points':Column 'data_id' does not belong to table charge-points.System.ArgumentException: Column 'data_id' does not belong to table charge-points. But it should be able to parse it.The structure of the JSON is like this (just showing top of file):{  "data": [    {      "id": 1096237,      "teamId": 449574, Any tips? 

We are getting a bad request error when we are using the timextender odata data source.  When we use the endpoints that we previously selected during metadata discovery, they still work normally. So why is the discovery metadata at the moment not working (it worked the first time). Thank you in advance!   

I have just upgraded to TX Classic 26.0.1 and i am having issues:Why do i still see ODX when i am not suppose to see it in TX Classic I havnet set up any incremental rule, so why i am getting this error? I am getting in on a table that i am not even deploying:    

Hi, I’ve got a Prooblem with a Datefield. Within the datasource it is defined as DateTime Offset. The source is connected via Rest API (ODATA) and I use table flattening before importing it into ODX. Alle Date fields arrive as DateTime2 when loading MetaData except this one field. It is imported as nvarchar. When looking into it, ist looks like a Boolean. True ist set when the field is filled. The rest is just empty.I’ve already checked if this field has the same datatype as all of the other fields- the set up ist the same.When I try to set a default value within the table flattening, the source isn’t recognized anymore and I have to reconnect. When I try override Data Types  I get the error “... Exception occurred when converting value '' for column name 'd-Istmenge_Enddatum' from type 'String' (precision:-1, scale:-1) to type 'DateTime' ...” The same error occurs when I try converting it in stage with set custom transformation to replace empty field with a default date. Maybe some on

I’m trying to connect TimeXtender to a REST API that uses JWT authentication. The API requires a JWT token for authorization, and I need to know the correct way to generate the token and refresh it.Here is how i do it in POSTMAN:I have an endpoint: {baseurl}/login, that generates a token using POST - the token expires every hourI then use that token to get data from another endpoint using GET: {baseurl}/meters 

Hi,I recently upgraded to the latest available versions of TDI and TIS:TDI: 7303.1 TIS: 7313.1After the upgrade, one of my data sources in the TX Portal is now showing "Applied provider version: Incompatible".Data source details:Provider type: TimeXtender Enhanced Current provider version: 23.16.1.0 Available upgrade: 24.3.2.0 Ingest instance service version: 200.0.7313.1The portal offers an upgrade to v24.3.2.0, but shows this warning:"If the version of TimeXtender Data Integration you're using is not compatible with the new data source provider, the data source will stop working. Please make sure you're on the latest version of TimeXtender Data Integration before upgrading the provider."I thought I upgraded to the latest TDI, but it will not support the new version of the provider?How do I resolve this?

Hello,At the moment we are onboarding a new REST API data source that uses PEM certificates in combination with a key file.We are using a legacy version of TimeXtender (20.10.80); where can I specify the PEM certificate (or its path) and likewise the key file?I have currently configured it as follows:1. Pem file2. KeyThe REST API endpoints are working in POSTman, so technically it works fine. Thanks for your anwser.

Hi, I have server, database, username and password for postgreSQL DB.with pgAdmin no issue it connects immediatelly. (no additional settings)In TX I tried CData ADO.NET Provider for PostreSQL 2022 (tried 2018 also, same result)Set SSL False - got error no encryptionSet SSL True - [500] System error: server certificate verification failed. Connection aborted. should I need any additional configuration, maybe different provider, any ideas? thanks in advance,Jakub

We are experiencing an issue with Generic ODBC Data Sources in TimeXtender 20.10.74.64 on SQLTX01.EnvironmentTimeXtender version: 20.10.74.64 Repository/Application: 20.10.74.64 Server: SQLTX01 OS: Windows Server 2019 Datacenter SQL Server: Microsoft SQL Server 14.0.3520.4 NT x64 TX build: 64 bitInitial situationWe originally noticed the issue on a PostgreSQL source that is accessed through an SSH tunnel.The PostgreSQL ODBC connection itself works correctly when tested directly in the ODBC Data Source Administrator.Example:server: 127.0.0.1 port: 5433 ODBC test from Windows ODBC Administrator: successfulAt first we suspected a PostgreSQL / tunnel issue, but further testing suggests this is not the case.What happens in TimeXtenderThe issue occurs inside the Edit Generic ODBC Data Source dialog.There are two scenarios:1. Opening the DSN dropdownWhen we open the Generic ODBC Data Source dialog and click the dropdown to show available System DSNs, TimeXtender immediately fails.So the failu

Hello,We are seeing an issue with a Enhanced Data Source TimeXtender REST (1.9.0) data source in TimeXtender where decimal values are being interpreted incorrectly during ingestion.We have two datasets based on the same AFAS source: one loaded through a REST connector in TimeXtender one loaded through a PowerShell script that retrieves the same REST data and exports it to CSV, which is then loaded into TimeXtender The CSV route shows the correct values for the field Aantal_FTE, for example: 0.18 0.25 0.55 0.95 1.00 However, the same field loaded directly through the TimeXtender REST connector shows incorrect values such as: 18 25 55 95 375 625 675 It appears that decimal values are already being misinterpreted in REST.rows, before the data reaches the staging table.For example: 0.95 becomes 95 0.375 becomes 375 0.675 becomes 675 This suggests that the decimal separator is being lost during REST parsing.Additional observations: In the REST source preview, the i

Hi,i want to retrieve ActivityEvents from PowerBI Admin using then TimeXtender REST API.configure the base URL as: https://api.powerbi.com/v1.0/myorg/admin/Endpoint configured as: activityevents?StartDateTime=%27{BDAT}%27&EndDateTime=%27{EDAT}%27&filter=Activity%20eq%20%27ViewReport%27{BDAT} and {EDAT} are populated using a SQL Query: DECLARE @i int = 0WHILE @i > -5BEGIN    select CONCAT(FORMAT(dateadd(day,@i,GETDATE()), 'yyyy-MM-dd'),'T00%3A05%3A00.000') as [BDAT],    CONCAT(FORMAT(dateadd(day,@i,GETDATE()), 'yyyy-MM-dd'),'T23%3A55%3A00.000') as [EDAT]    SET @i = @i - 1ENDi hoped it will loop for the past 5 days but unfortunately this doesn't work.Setting the BDAT 5 days in the past doesn't work either. Any ideas how to solve this?by the way we are using TX Classic V 20.10.66.64 and TimeXtender REST API v16.4.23.0 (also tested with 16.4.21.0)Kind regards,Hans 

We are migrating from CData data sources to the TimeXtender REST API data source.For Microsoft Graph API (used to retrieve calendars for multiple meeting rooms), the connection works correctly, but we are running into a major performance issue. While we retrieve the same amount of data.Performance comparison:Using CData:Ingest task: ~4 minutes Execute task per table: ~10 secondsUsing TimeXtender REST API data source:Ingest Full Load: 1.5 – 2 hours Execute task per table: 10–15 minutesWe have over 30 tables, so the execution time increases dramatically when using the TimeXtender REST API connector. Question:Are there any recommended ways to improve the performance of the TimeXtender REST API data source, both for the ingest phase and for execution runtime?For example: configuration tips, concurrency settings, pagination options, or known limitations compared to CData?Any guidance or best practices would be greatly appreciated.

We use the CData provider for CSV to ingest data from a https URL. The source system does not offer any other way to access the data. This works well. TimeXtender Classic with ODX.We're now looking into migrating away from CData (not trying to start a discussion about the reason...). The TimeXtender CSV provider (version 16.4.23.0) does not suport a https location, only local file/azure/s3/sharepoint/google/sftp/ftps. Is there some way to get this to work? The current workaround is to use the TimeXtender REST provider but that's quite a hassle to set up, especially when there are lots of columns involved. Also, it's really not a REST API with CSV response. It's a regular URL.

When I try pagination in the Enhanced datasource REST I only get 1 run, it stops after the first page.My Json result looks like this when I get to a page without a result:{    "data": [],    "status": "success"} How do I get my stopCondition to work in pagination?

Hello, We have a project that is on 20.10 (will upgrade to classic when it is released later this quarter).The customer has a source that is apache iceberg that we want to get data from but I can’t find any information regarding that for TimeXtender. Has anyone done this yet in TimeXtender, if it is even possible to ingest it?Thank you

Is there Swagger import support for the new TimeXtender REST data source?

Hi All,My current employer uses TimeXtender Desktop and two separate servers (dev/test + prod).The previous administrator installed the ODX server on the dev/test server. This causes issues when a datasource is modified, as it also affects the production environment.At my previous employer, we had an ODX server per environment: Dev ODX, Test ODX, and Prod ODX.My question is: what does the community recommend regarding having an ODX server on the dev/test environment?My ideas:Install the ODX Server on the production environment. Rename the VM.Thanks in advance for your help and input!Kind regards,Tim

Hi thereI have an issue which I’m not quite sure how I can solve in timextender.i have 2 tables, Vendor and Catalouge .. Vendor contains all the vendors and Catalouge is the productcataloge with information about the product. The only parameter I have that I can make the relationship on is VAT .. the problem is that many products have the same VAT and there is a multiple Vendors with the same VAT. I was looking into making a bridge table but Im not quite sure how I can do this automatically in Timextender. what’s the smartest solution to this?

I need to connect some new REST API's to our TX environment. These API's where easy to configure in Postman, but is now a challenge in TX. In Postman it's possible to use a “pre-script” (java) to create some variables, concatenate them and then hash. This is the script:const method = 'GET';const urlPath = '/app/openapi/v1/device/deviceOpenIds';const secret = 'MY_SECRET';const timestamp = Date.now().toString();const signature = CryptoJS.HmacSHA256(method + timestamp + urlPath, secret).toString(CryptoJS.enc.Hex);pm.environment.set('timestamp', timestamp);pm.environment.set('signature', signature);This signature is used in the header for authentication for the GET call. The API provider gives a python or java script to make the HmacSHA256 hash, but I cannot use that directly in TX.What is a good way to approach this in TimeXtender? 

I am trying to setup a connection to a MySQL Database. It works just fine in MySQL workbench. It works just fine in ODBC Data Source AdministratorTimextender throws me this error:ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specifiedBut this is what it looks like in the portal: Am I missing something really obvious here?

I’m using TimeXtender REST Data Source v10.2.0.0 with two endpoints: A static endpoint that returns a list of IDs. A dynamic endpoint that retrieves additional data for those IDs. The problem is that not all IDs from the first endpoint exist in the second. When the dynamic endpoint tries a ‘non-existent ID’, the API returns a 500 server error, stopping the data transfer.This is an external API, so I have no control over it. From what I can see, the datasource provider doesn’t offer error handling (like try/catch or “skip if failed”).I could create a curated list of valid IDs, but there are thousands of IDs that can change at any time, making this impractical. I could also ask the API provider to return empty JSONs instead of errors, but I’d prefer to handle it on my side.Any advice?

In what version of Timextender is the existing Easy Connect provider replaced by the new TNS provider? We are running the older classic version 20.10.52.64   

I'm trying to connect to MongoDB and load data  into Timextender I have a ODBC driver setup, and test connection works. In Timextender I have ODBC Generic Data setup, and test connection works and to Synchronize Data Source works as well.But when I try to execute the data transfer from MongoDB into Timextender then I get an error.  

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: