REST APIs

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

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

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

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?

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

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’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?

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: 

Hi, I’m trying to connect to a API using Timextender REST version 7.1.0.0 but my result is only one row of data. In Postman I get much more data. It might be because the API returns JSONL and TX tries to handle it as JSON. I’m trying to convert it to Text but it still doesn’t work.  Earlier I managed to complete the goal in Power Query even with pagination.  Now I’ve hit a brick wall and I need your help to proceed. My result in ODX:  My result in Postman:Here’s my connection profile:{  "Name": "MixPanel",  "Description": "",  "Provider": {

Hi,I got this structure(see below) from my rest api and I need to add order_id into each line of order_line. How can I flatten out order_lines with the order_id? I have tryed different  ways, but when I have two order lines only one get the right order_id value…. Order/Orderlinesbest regards,Bjørn A.

Hi,We're observing strange behavior with the new enhanced REST data source provider.When we do the call on this endpoint in the old connector or in Postman, we get a return of 197 records. This is a single payload, 1 page, with fully filled rows, including a populated PK field.Now, when we do the same call with the enhanced REST data source provider we receive 589 records. 392 of these have null values on all records except for one field, a descriptive but not otherwise important. Importantly the PK field of these records is also null.Now we have two questions: Why is the new REST provider delivering more records than other providers/tools? How can we effectively filter out these records in the actual call? As it seems we are now only able to successfully filter out these almost empty records at the DSA.Best, Luuk 

Hi,I've got a couple of installations with customers using CDATA for AD/Entra integration, with the upgrade I found an article to advise moving them to REST.I am however a bit lost on how to connect a REST API to Entra, and I couldn't find good documentation to fill it in.Could someone assist us for a moment or maybe point us toward more complete documentation specifically on using the Enhanced Data Source to connect to Entra?  Thanks in advance, Jan DD

Hi,We are using a REST data source with dynamic values to fetch data for approximately 12,000 records, where each record corresponds to an individual API call.Occasionally, we encounter issues with the API provider where some calls return a 400 error. Unfortunately, it’s unpredictable which dynamic values will cause these errors.Currently, it appears that the TimeXtender REST data source stops processing upon encountering a 400 error, resulting in a "Completed with errors" status.Is there a way to configure the REST data source to continue processing the remaining dynamic values, skipping over those that result in a 400 error? Ideally, it would also log the calls that failed for review. Best regards,Pontus

Hi,I'd like to make a new data source connection using REST to connect with our Azure storage table.Thus far I have managed to get the connection setup, however pagination remains a issue.When testing our connection and following the steps in the debug logging file I see that when a table has a next: "x-ms-continuation-NextPartitionKey” and "x-ms-continuation-NextRowKey” it will return this in the header (not the body). But if the table doesn't have this it will stop since the "x-ms-continuation-NextPartitionKey” header was not found.As I am applying these pagination parameters as query parameter I need to be able to solve this issue.Is there maybe a way to apply a default value to these variables (manipulating query doesn't work as the variable itself already won't be found) or some way to dynamically replace a URL? Example table with no NextPartition/rowkey:

Is it possible to add the dynamic values used in a nested call to a table flattening.In this particular case the first call gets the list of documents and feed the id as a dynamic value to the 2nd call. The response doesn't include any reference to the document and without the id we cannot link the details to a document. I've tried to add it as a static node (name: Document_ID  value {id})but that only results in errors.  

I need some help retrieving JSON data via GraphQl.When testing the connection in TimeXtender, I got a "Connection OK" message.After Synchronizing Data Source in TimeXtender an error message is displayed :   System.Data.CData.GraphQL.GraphQLDataReader ExecuteDataReader(System.Data.CommandBehavior)  [500] Could not execute the specified command: The defined query is null. : "UserViews"."query"  System.Data.CData.GraphQL.GraphQLDataReader ExecuteDataReader(System.Data.CommandBehavior)  [500] Could not execute the specified command: The defined query is null. : "UserViews"."variables"==========================================================================================================================We received the following connection string from our IT department--------------------------------------------------------------------------------------------------------------------------curl --location 'https://xxxxxxxxxx.co

Hi, is there anyone who managed to get the Freshdesk pagination working? I tried different ways but it is not working for me. Let me just describe what I did so far.trying with using Query Parameters and {TX_NextPage}, I tried using that since the freshdesk url is very easy to adjust with the page number, so I added this:My URL is:Pagination should look something like this https://[domain].freshdesk.com/api/v2/tickets?page=[number]So, I added in the connection settings first the pagination rule which looks like this:and I added the endpoint later for tickets.This didn’

I am using a Power BI endpoint (https://learn.microsoft.com/en-us/rest/api/power-bi/datasets/get-refresh-history) where I need datasetIds to get the refreshes of that dataset. I am using the TimeXtender REST data provider, in which I loop over a list of dataset ids using a dynamic value. The problem is that in the output of the Get Refresh History endpoint the dataset Id is not included.Therefore, my question is: Is it possible to pass a dynamic value used in a call as an additional column next to the output of the call? I don't see any option for this in the portal. If I were to extract the data using Power BI, I would do the call for every row in a table containing the required dataset Ids and expand the resulting column. This way, the original table column containing the dataset Ids will always be related to the dataset refre

The TimeXtender REST Data Source has the ability to add an API endpoint with table flattening in multiple ways: either adding the endpoint once with multple tables or adding the same endpoint multiple times. I've done some tests to find out which is fastest.The test was done on an API with an unstructured JSON data source, with root nodes on multiple levels where the XSLT Table Builder can iterate over. This means I needed to add 4 flattened tables on the same endpoint, each with different root nodes. Version numbers were REST provider version 9.0, TDI 6935.1, with Ingest running on and Azure VM and storage on ADLS Gen 2.Two ways of setting up the same endpoint with four tablesMy hypothisis was that 1x endpoint with 4x tables would be quicker than 4x endpoints with easch 1x table, because TimeXtender woul

We are using the new 'Import Swagger/OpenAPI’ feature in the TX REST Data Source (absolutely loving that btw), but are encountering an error.  When importing the URL for a Weather API, we receive the following error message:Error: Exception Type: Microsoft.OpenApi.Readers.Exceptions.OpenApiUnsupportedSpecVersionException Message: OpenAPI specification version '3.1.0' is not supported. So far we've had no trouble importing Open API spec 3.0.0 documentation. Is there a compatibility issue with the latest 3.1.0 spec?

Hi,I’m trying to use the transformation Set replace value in the Table Builder. Described in tutorial like this: I tried a simple SQL string function (LEFT(NodeName,5). It looks proper in the XSLT Output: The execution worked fine. No errors. But both columns PatientNameHash and PatientName produces the same result in the Ingest table. The full name.Anyone who knows how to format a transformation in Set replace value?Is the content of the template “string-replace-all” available for viewing?BRAnders

Hi all! This morning, I retrieved data with the REST API of MoreApp.com. The API is quite straightforward. I encountered some challenges that I'd like to share with you. If there’s anything incorrect in this description, please let me know so I can adjust it.PreparationI am using the TX REST connector version 7.1.0.0.You will also need an API key, which must be created by the administrator in the app.The data I need to retrieve is located at the base URL: https://api.moreapp.com/api/v1.0. The specific data I am fetching is "submissions," or filled-out surveys. The POST API used to fetch this data is structured as follows:https://api.moreapp.com/api/v1.0/customers/{customerId}/forms/{formId}/submissions/filter/{page}Customer is fixed. FormId needs to be looked up. Page is required for pagination.Aut

HI,For the first time in my life, I have enjoyed working with a REST API 😁.It is actually a pleasure to use TimeXtender's new REST data source now.Swagger import, Dynamic values, Table builder etc.There will be more to be desired of course, but hats off to the developers who built it and to Thomas who have made tutorials that are comprehensive and easy to understand.Nice job! 🎉BRAndersP.S. It feels good to be undividedly positive once in a while too 😊

Hello,I'm working with a REST API where the response is a valid JSON but has a Content-Type: text/plain. The response looks like this:[{"OrderId":"46D2A6BD-8B34-4F55-B816-B90017CDBA28","OrderNumber":131,"DeviceId":"POS41232","VendorId":1,"VendorName":"Test Facility","StoreId":114}]However, the log shows the following:2025-01-10T15:33:16.340+01:00    2    [1|Q-Id]    [HTTP|Res: 0] HTTP/1.1 200 OK, 1615 Bytes Transferred2025-01-10T15:33:16.340+01:00    2    [1|Q-Id]    [HTTP|Res: 0] Request completed in 676 ms.2025-01-10T15:33:16.344+01:00    3    [1|Q-Id]    [META|Schema: JSONValidation] https://pos.no/getsales is not a valid JSON resource.2025-01-10T15:33:16.345+01:00    3    [1|Q-Id]    [META|Schema: JSONValidation] Invalid JSON markup. Expected json, but instead found [text/plain; charset=utf-8]. To attempt to fix this, I set Accept: application/json in the request heade

Hello, I want to get metadate from my Azure datalake using their Blob API. I wasn't seeing any data in the Ingest storage so I turned on cashing to file, to try to see what's happening.  There are three files in my cashing folder: Data_.raw: The return of the call, i.e. my actual data. This look excellent, except that it's a .raw file. Contents: <?xml version="1.0" encoding="utf-8"?><EnumerationResults ServiceEndpoint="https://xxxx.blob.core.windows.net/" ContainerName="datalake"> <Prefix>my_prefix</Prefix> <Blobs> <Blob> .... </Blob> </Blobs> <NextMarker/></EnumerationResults>   Data_.xml: Basically the same as the Data_.raw, but with the content of Data_.raw as the data of a value-element. The data also contains the XML header (so now the docu