Ingest

I have a API endpoint with pagination:https://www.mytestserver,com/DWH/api/v1/all-buildings?buildingType=BAR&page=5I have created a RSD file with the following code after  </api:info>  <api:set attr="in.Header:Name#" value="Accept"/> <api:set attr="in.Header:Value#" value="application/json"/> <api:set attr="in.DataModel" value="FLATTENEDDOCUMENT"/> <api:set attr="in.JSONPath" value="$.data"/> <api:set attr="in.EnablePaging" value="TRUE"/> <api:set attr="in.Page" value="1"/> <api:set attr="in.PageCount" value="100"/> <api:set attr="in.BaseURI" value="https://www.mytestserver.com/DWH/api/v1/all-buildings?buildingType=BAR&page={page}" /> <api:set attr="in.ElementMapPath#" value="/json/meta/pagination/pages"/> <api:set attr="in.Eleme

If you see Task are sucessfuly completed in ODX, and tables are vissile in query tool, but while loading data from ODX to MDW in select Table options tables are not visible, as shown in Figure

hi, Lately were are getting alot of 503 exceptions.  Error message is typically: The task '983693' failed:System.AggregateException: One or more errors occurred. ---> System.AggregateException: One or more errors occurred. ---> System.Net.Http.HttpRequestException: Response status code does not indicate success: 503 (The server is busy.).   at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()   at Azure.Management.REST.RestWebRequestManager.<SendRequest>d__6.MoveNext()--- End of stack trace from previous location where exception was thrown ---   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)   at Azure.Management.REST.RestWebRequestManager.<SendRequest>d__5.MoveNext()--- End of stack trace from previous location where exception was thrown ---   at System.R

Hi,I am trying to connect to a REST API that uses OAuth2 authentication.The API documentation is very clear on what to include in the authentication:  I have entered all this information in the REST CData provider and I can successfully use the provider’s “Authorize OAuth” button.However, when I try to test the connection, error “401 - Unauthorizated” is returned.In the API documentation, they state that the token needs a prefix “Bearer “.I suspect my error is caused by the REST CData provider sending the authorization header without the Bearer prefix, like so:Authorization: {ACCESS_TOKEN}Which the API of course does not accept. 

Hi, can you provide me with detailed instructions on how to set it up?

When configuring the CData Microsoft Sharepoint (23.0.8669) provider for extracting a Sharepoint List, we encounter a problem with the button ‘Authorize OAuth’. We are configuring the data source in ODX Server 20.10.40 and TX version is also 20.10.40.The following settings are configured:According to the CData documentation AzureAD should be used as Auth Scheme to leverage OAuth to authenticate, we also use this exact same setting and the same app registration for another data source using the Excel Online provider for which all is ok.However, when using ‘Authorize OAuth’ with the Sharepoint provided, we get the following error:

In order to retrieve meteorological data from The Netherlands, we want to use the Open Data API developed by the Dutch Meteorological Institute (KNMI). This website contains all relevant information on using the API.In summary, these are the steps that we want to undertake. Anyone can do this, because of the anonymous API key that is open to public:Locate the ‘Anonymous API key’, can be found on the KNMI documentation website Determine the dataset name, version and filename to establish the correct endpoint In this example we want to use the following endpoint: https://api.dataplatform.knmi.nl/open-data/v1/datasets/etmaalge

Our ODX is hosted on a separate VM in Azure. We followed the suggestion to use the size DS2_v2, but we encountered frequent “System Out of Memory exception was thrown” errors that caused the ODX to stop. We are planning to switch to E2_ads_v5, which has twice the memory, but I am curious if anyone else has faced this issue and has any advice.

I have a table with a varchar(max) field (stored in Dedicated Pool, which is a data source). and it won’t come through to ADLS Gen2 (ODX, version 6284.1). I’m using the Azure Synapse provider.The longest field contains almost 4 million characters, but I’ve been unable to figure out whether this is a limitation in TX or Azure. Does anyone know?

We use Sharepoint for multiple data sources. Connecting the Sharepoint Lists works fine and I have a OAuth for Excel Online running as well, but my data source throws an error: Cannot find file.  I need to handle multiple files according to this documentation:https://support.timextender.com/data%2Dsources%2D112/connect%2Dto%2Dexcel%2Dfiles%2Dwith%2Dexcel%2Donline%2D628 What’s the reason for this?  My App Permissions are set accordingly: My Setup looks like this:

Hi community, I am trying to work with the LinkedIn API to retrieve details about UGC posts (i.e. engagements, clicks, etc.). This information is not part of the LinkedIn Marketing Solutions CDATA connector, so I am using the CDATA provider for REST 2022. I first made a call to the posts API to ‘Find Posts by Account’: Posts API - LinkedIn | Microsoft Learn. After that I need to pass each Post ID into the Organizational Entity Share Statistics API to ‘Retrieve Statistics for Specific UGC Posts’: Organization Share

I’m struggling with the TimeXtender SAP Table Data Source version 18 in ODX Server v6429.1. In our current setup we use Table Name filtering like this: Please see the wildcards used. How does this translate to ODX Server v21? I have these three rules: The latter does not seem to work. I tried many variations (and did a sync data source consecutively), but when I click Select Tables under a transfer task, it only comes up with the tables matchin an equal-rule. Tables that should match a like-rule never show up: Using equal a

Hi community,I have a MariaDB data source which I connect to using ODX Server (v 6346) and the CData/ADO.net connector for MariaDB v 23.0.8565.0.The source database is set to collation utf8mb4_general_ci. I noticed by copying from ODX Server to a Data Area that some special characters are slightly different than the source/ODX. I can fix this by manually changing the data type to nvarchar instead of varchar, but that is a lot of field editing.The Override Data Type function can help as well, but as we have a wide range of field lengths, this also means a lot of override rules.Is there a way to tell ODX Server that all varchar fields should be unicode/nvarchar by default (eg. based on the source database collation)?Example from ODX Server. These fields should all be nvarchar(xx) instead of varchar(xx):

Hi,We are unable to set up Notification on Critical Errors for the ODX Server. Both service and database for the ODX is on prem. The Exchange Server is deployed as a hybrid. TimeXtender version 6221.1This is the error message:  Setting up notification for the executions in the MDW’s and SSL’s is no problem. No authentication is required by the Exchange server.BRAnders

Hi all,For one of my current client's we are rectrieving a warning while syncing the odx. The task is completed and we can transfer the data. but the warning is a bit odd.We already tried to remove the folder from the data lake and try a full load. but this didn't fix the warning. Anyone any ideas?

I’ve detected an error (sended to support) with the packages that use full load and if the incremental rule it’s defined with a datatime field.The error it’s in the ODX transfer and I’m using a SQL data source.Hope this help you.

I am working on a project with 3 environments Dev, UAT, and Prod. I scheduled ODX transfer task to run every 15 minutes.But any scheduled tasks are not working, I have to run the transfer tasks manually  Regards 

I’ve a location with multple different json files. Can i use one connector to this directory and transfer each json file, or need i to make one connector for each file? For csv files i can use one connector, for json it doesn’t seem to work this way...

Hey.This is maybe obvious - but I’m struggling to find the proper documentation, hoping someone can point me. We have TimeXtender version (20.10.42.64) on a remote server at the company I’m with, and I'm new in a data analyst role. We have the need to connect a new data source, Hubspot, to TimeXtender.  Is there only general documentation to connect new data sources or is there specific documentation related to Hubspot?     

Hi,I have a JSON data source that looks something like this{ "company": { "companyId": 1, "name": "AdventureWorks", "description": "" }, "hierarchies": [ { "depths": [ { "depth": 0, "name": null }, { "depth": 1, "name": "Company" } ], "allKeys": "1|-1|10" } ], "slicer": null, "userToGroup": "Username,GroupId\nJohn,G1\nSarah,G1\nPeter,G1\nKate,G1", "groupToKey": "GroupId,Key\nG1,10\nG1,101\nG1,102\nG1,103\nG1,104"}And I am only really interested in the last two objects, userToGroup and groupToKey, which both are in a CSV format. Is it possible to use something li

I am connecting to an Openedge Progress database via ODBC drivers. After finding out the password needs to be set in the registry, I am able to connect to the source (test connection from the Data Source properties is succesful).My sync task however fails because the datasource is not querying the correct metadata tables. In Progress, metadata for tables, columns and views is stored in the tables SYSTABLES, SYSVIEWS and SYSCOLUMNS. In the advanced settings of the datasource I am able to point out the correct column names, but not the correct tables (see screenshot below).Does anyone know how to point the datasource to the correct metadata tables?  

What does “Remove Unused Objects” do? I cannot find documentation about it. Thx!

Hello, To my understanding TimeXtender determines the data type of a column based on first x amount of rows, depending on your setup in the portal.  The fields in my source  come in as (dd.mm.yyy) for example: "05.03.2021”. I use a Storage Account with a CSV connection.  I would expect that TimeXtender creates a "date” date type out of this. However, is seems that if a field character starts with a '0’, it skips it. In the ODX it shows an Integer value '5032023’.ODX: Depending if a character starts with a '0’ the fields (dates) show up like:

At one of my clients we are using the ODX and they set it up that for every different type of load they added the data source multiple times. So for the normal full loads there is 1 source . For the incremental loads of the same source there is a different source.In the data source selection the include only the tables they need for the full load. and they do the same for the incremental. But from time to time task wil not execute without showing up in the execution log without an error. I have the feeling that because the includes je indirectly exclude the other tables and if they are running at the same time this cancels each other out. In the windows logs you can see that the package then is skipped but it's no where to be found in TX.Does anyone have an explenation about this and/or an idea how we can fix this?My idea was that maybe putting everything in 1 source and then create 2 different transfer task instead of 2 different sources would fix this p

Why does the app registration for the ODX need owner permissions on the resource? I would think that read/write permissions would be sufficient. Why does TimeXtender need the “extra” rights?