Ingest

Hi Just upgraded existing TX ingest and Data Integration to latest versions 6848.1 on dev server and now I get a failure when running my ODX Data Source steps, specifically it seems just what used to be know as the synchronise step but now called the import metadata task. Originally each data source has 3 steps, synchronise, transfer and storage management, and they used to run fine. Now I get seemingly random job fail errors on what looks like so far just on what was the synchronise step. If I run the failed step manually it processes without issue. However, when I run the entire ODX job I have set up it seems that one or more data source sync steps now fails. The execution failed with error:Exception Type: Microsoft.Data.SqlClient.SqlExceptionMessage: Transaction (Process ID 76) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. Stack Trace: at Microsoft.Data.SqlClient.SqlConnection.OnError(SqlException exception,

This is a follow-up of Using XML to ingest data, that i have managed to solve. I need some help with creating a nested statement. The first rsd which lists out all the IDs is this: <api:script xmlns:api="http://apiscript.com/ns?v1" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <!-- See Column Definitions to specify column behavior and use XPaths to extract column values from XML. --> <api:info title="contract" desc="Generated schema file." xmlns:other="http://apiscript.com/ns?v1"> <attr name="contractid" xs:type="string" readonly="false" other:xPath="/Envelope/Body/contracts/contract@contractid" /> <attr name="description" xs:type="string" readonly="false" other:xPath="/Envelope/Body/contracts/contract@description" /> </api:info> <api:set attr="DataModel" value="RELATIONAL" /> <api:set attr="URI" value="https://my.soap.endpoint/service.asmx?WSDL" /> <api:set attr="PushAttributes" value="true" /> <api:set attr="EnablePaging" value="true" /> <api:set attr="Header:Name#" value="SOAPAction"

Anyone have a suggestion about how do i use this XML to ingest data into ODX? <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <soap:Body> <ExportDocsProjectWithTendersResponse xmlns="http://publicprocurement.com"> <ExportDocsProjectWithTendersResult>{ "ProjectBodies": [ { "ExternalId": "666666", "DefaultEvaluationModel": "LowestPrice", "DocumentNumberingSchema": "Numeric", "SectionNumberingSchema": 0, "RequirementNumberingSchema": "Alphabetic", "Metadata": [ { "Name": "ProjectName", "Value": "Ingesting Data into TX" }, { "Name": "Reference", "Value": "123456" }, { "Name": "ContractType", "Value": "XML" } ], "DataFields": [ { "ExternalId": "1", "Type": "FreeText", "Name": "Prosjct Name", "Category": "C1", "Value": "V1" }, { "ExternalId": "2", "Type": "FreeText", "Name": "Prosjct Name 2", "Category": "C2", "Value": "V2" }, { "Extern

Hi, I have a customer for whom with PoC, we need to connect Oracle Data Source using API. Need help on either documentation Or how to connect the same. Anyone has experience to connect, please share.

I wanted to ask if others have experienced issues with the TimeXtender_Ingest_Service_6823.1. For the second time, I’ve encountered problems with opening the ODX, where it gets stuck during the process. When attempting to restart the Ingest service, it remains in a "stopping" state and fails to restart properly. To resolve this, I’ve had to manually force the TimeXtender_Ingest_Service_6823.1 to stop using the Command Prompt. Once the service has been forced to stop, I can restart it successfully, and afterward, the ODX opens without issue. Has anyone else encountered similar problems? If so, are there any recommendations or fixes to prevent this from occurring again? Looking forward to your insights.

Hello, I'm facing an issue with how TimeXtender handles special Swedish characters (å, ä, ö) when querying data from an Oracle database through the ODBC data source. I have a view that contains a column with the data type (VARCHAR2) in the Oracle DB. When loading the data to TimeXtender the special characters appear as question marks (å), a (ä), and o (ö). However, when I create a Query Table and use CAST(CF$_PLAN AS VARCHAR2(1000)) on the same column the special characters are retrieved correctly to TimXtender. I have queried DUMP from the database to check that the column’s special characters are stored with proper UTF-8 encoded values, and they are. I have also checked the NLS settings for the Oracle database, the TX application server and the ODBC connection. Is there a way for these special characters to be retrieved correctly to TimeXtender without having to use CAST in Query Tables? I use TimeXtender Data Integration 6822.1 and TimeXtender Ingest Service 6823.1. The ODBC Driver

Its my first SOAP ingestion. The XML looks like this <?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <soap:Body> <ListPublishedFilesResponse xmlns="http://something-something.com"> <ListPublishedFilesResult> <idbdata xmlns=""> <originator> <company name="ABC Corp" url="http://www.abc.corp" /> <contact name="ABC Corp" email="post@abc.corp" /> </originator> <generation date="2024-12-09 10:43:09" dateutc="2024-12-09 09:43:09" /> <contract origin="tendsign.com" tendsigncontractid="2649113" name="Protocol" referencename="1 (ABC-01)" startdate="2018-07-01 00:00:00" startdateutc="2018-06-30 22:00:00" enddate="2025-06-30 00:00:00" enddateutc="2025-06-29 22:00:00" objecttypeid="3"> <attachments> <file id="15"> <name>ABC123 - Contract</name> <filename>ABC123-Contract.pdf</filename> <fileurl>https://contract.abc.com/abc.pdf</fileurl> <descri

Dear Sir, We are looking for following. E-mail notifications when an Ingest ODX Data Source Data Transfer Task is failing to load the data from the source application/database. Is this possible in TX version 6766.1 ? Or do we need an upgrade. Regards from Venray. Arthur

Hello, We are using TimeXtender classic ODX server (20.10.51) to ingest data. Some of our data sources are located in Azure in form of Azure Synapse / Azure SQL. Are there any guides on how to setup data ingestion from Azure to on-premises ODX server? I.e. what are prerequisites from Azure side (service principal / managed identity?) to connect and what connectors should be used from the ones available in ODX server? I know this is possible from cloud version of TX, but is it possible to do so from classic version? Thank you

Hi All, I try to add my Fabric LakeHouse as a new source in TimeXtender version 20.10.50.64 but I keep getting an error when I try to read objects from datasource eventhough it says connection is succesfull. Data source settings I copy the SQL connection string from my lakehouse and put it as server name. When I do "Read object from data source” I get the following error. The weird thing is that when I try these exact same stept in SSMS I can see the table from the source with the data in it. Am I missing some steps?

I’m trying the new timextender excel data source but I keep getting errors. I have upgraded to TimeXtender Ingest Service 6823.1 and TimeXtender Data Integration 6822.1. I am trying to load a really basic excel file. First I tried the ‘Infer data types’ option. It succesfully detected the datatypes but I still end up with an error in the last step of the metadata manager. Service request failed: The given value of type String from the data source cannot be converted to type nvarchar of the specified target column. (System.InvalidOperationException) It does not say which column is the issue. After this I tried to disable the ‘infer data types’. It shows all my source columns as text but I still end up with the same error. Lastly I tried to override the data types to varchar(max). Still the same error. Any ideas on what I am doing wrong here?

Hi, Have anyone succeeded with a Soap 1.2 call from ODX? We have a source that only have a Soap interface. I've done a lot of testing but so far very little success. For the moment it complains about my content-type header. Don't know why. I'm using the rest connector. Perhaps I should use a xml connector instead. If anyone could share a working example I would be more than happy. Perhaps it's not possible at all. I'm not sure. Regards Anders Bengtsson

Hi, I have a unity catalog in azure databricks where I want to connect to from Timextender (20.10.44), I installed the Cdata connector for Databricks (2024) and am able to connect via test connection (succesfully connected) but when i try to save TX has issues with the length of the (Protocol ?) version which is empty but also using 1 till 8 which are available in the drop down list all result in the same error What do I need to do in order to get his working? Kind regards,

Hi I want to download the latest version of TDI and Ingest Service which is 6823.1. But when I use the link to download, it still gives 6822.1. Can you please share the link for the same to download. Also can someone share the link to download 6766.1 with Ingest Services.

Hi, We are trying to connect to several CSV files stored in a local folder. While we can successfully synchronize the data source and perform a full load in the ODX, we encounter an error when attempting to add the table to our data area (DSA). The issue lies in the path to the Parquet file stored in Azure. The correct path should be: CSV_DNB/csv_*/DATA_2024_11_28__11_09_50_2219585/DATA/DATA_0000.parquet However, the path Timextender is looking for is: CSV_DNB/csv_^*/DATA_2024_11_28__11_09_50_2219585/DATA/DATA_0000.parquet It seems that Timextender is misinterpreting the automatically generated name and adds a ^ character. I also attempted to use a specific file aggregation pattern, such as; H100.*.csv (all files in folder have the prefix H100 followed by a random number). However, I encountered the same error. Is there a way to specify the name of the table generated in the ODX? It seems like the “File aggregation pattern” is the issue. Do you have any idea how to fix this? -Execute E

Hi, we have an Afas datasource via provider cddata rest 2023. The Afas getconnector has been updated with new columns. When i run the sync task for this Afas datasource i expect timex to detect the new columns but this is not the case. What do i need to do to let timex see this new columns? thank u in advance, Bob

Hi, we have created a new datasource for Azure Active Directory(Entra ID) via “cdata ado.netprovider for azure active directory 2022” de sync task runs ok but the transfer task keeps giving a completed with error signal. I have discussed this error with a consultant and a system/ authorization specialist but we cannot get it right. The error we are getting is(first part of the error): Executing table azuread_users: failed with error: System.Data.CData.AzureAD.AzureADException (0x80004005): [500] Could not execute the specified command: [Authentication_RequestFromUnsupportedUserRole] User is not in the allowed roles. ---> cjo220x.BG: [Authentication_RequestFromUnsupportedUserRole] User is not in the allowed roles. ---> cjo220x.Qt: [Authentication_RequestFromUnsupportedUserRole] User is not in the allowed roles. please advise us how to handle this. thank you in advance, Bob van Ierssel

We are experiencing a small issue with one of the connectors while using managed queries. When I use the query tool, we are utilizing the SQL endpoint from a Fabric Lakehouse to retrieve the data into the ODX. When I query the DBO table, I receive 12 records. For example, when running this query: SELECT [SinkCreatedOn], [SinkModifiedOn], [omoperatingunitnumber], [modifieddatetime], [modifiedby], [createddatetime], [createdby], [dataareaid], [recid], [tableid], [createdon], [modifiedon], [IsDelete] FROM dbo.[omoperatingunit] I also get 12 records. However, when we transfer this managed query, we only receive 11 records. This issue has occurred with multiple tables. We are not applying any filters to this dataset. Do you have any idea why this might be happening? Manually excluding or including all the columns is not manageable on the scale we are working with, so we rely on writing managed queries.

I believe I followed the instructions I found here: But for some reason it wont work on my end, or maybe i’m doing something wrong? I’m using TX version 6745.1 which is one of the latest. I have set the column that gives me the error to convert to text. After that I double checked to see if TX would indeed override the datatype and turn it into text. I synchonize again and try to transfer. But for some reason it keeps throwing me the error: Message: Error obtaining value '25-mei-1991' for column 'Geboorte Datum'. Failed to convert to datatype: 'datetime'. The original datatype of the column is: 'datetime'. Am I missing how this is supposed to work, or am I doing something wrong?

Hello, Sometimes a picture says is all, but to be complete: I set my incremental load rule on my datasource to mach any field containing ‘UPMJ’ (INT) with updates and deletes and most importantly: set the “substract from value”-value to 2. Looking at the picture above this is either not set correctly or not displayed correctly.

Dear Sir, We connect to our Excel files through a Sharepoint site with some Document Libraries. Works fine, but the performance is bad 😑 -5 minutes wait to Select Tables -5 minutes wait to execute Synchronize 5 minutes wait for execute Full Load Is there a way to squeeze some performance out of this ? Thanks in advance for looking into this performance issue. Regards, Arthur

Dear Sir, I want to connect to a PostgreSQL database via ODBC. So I found these posts how to fix this. But I am using TX version 6766.1. Can someone please point me the way how to fix this with the latest and the greatest version of TimeXtender. See Word document in the attachment with my setup. https://legacysupport.timextender.com/hc/en-us/articles/4410466782621-Create-a-ODBC-data-source-in-a-ODX-or-with-a-Any-Source-ADO-Net-provider-in-a-Business-Unit Thanxs in advance. Regards, Arthur

I am trying to load a semicolon csv file with ODX (version 6766.1) The output is just 1 column. What box do I have to tick in the app portal to seperate the collumns on ; (semicolon) ? Regards, Arthur

Hi all, I am currently working with a client who is using TimeXtender version 6766.1 in an Azure environment. We are trying to ingest data from a source that generates JSON files stored in a hierarchical folder structure organized by date and hour. The folder structure is as follows: subject/version/date=YYYY-MM-DD/hr=HH/*.json Example Path: dev/Call/1.2/date=2024-10-30/hr=14/*.json Within each hr=HH (hour) folder, there may be one or more JSON files. Similarly, each date=YYYY-MM-DD (date) folder may contain multiple hour subfolders, though it's rare for all 24 hour subfolders to be present. I have successfully configured the data source connector in TimeXtender to read all JSON files from a specific hour folder, as shown in the example above. However, our goal is to configure TimeXtender to ingest all JSON files across all date and hour subfolders under the main path: dev/Call/1.2/ When I attempt to use wildcards to achieve this—such as: dev/Call/1.2/*/*/*.json I encounter an error st

Hello, I am encountering a challenge with the REST connector when it deals with JSON data that includes empty property names. This issue arises specifically during the conversion of JSON to XML. The REST connector fails when trying to convert JSON data that contains properties with empty names. Here is the error message I receive: Failed to execute endpoint 'authenticate':XmlNodeConverter cannot convert JSON with an empty property name to XML. Path 'TX_Autogenerated_Element.menu.categories.', line 1, position 94530. This error stops the ingestion process because XML does not support tags with empty names, which are present in the JSON structure. This is the problematic part of the JSON structure:{ "categories": { "": { "collapsed": false, "description": "<No Category>", "id": "" }, "BUD": { "collapsed": false, "description": "Budget", "id": "BUD" } // Additional categories }} In this JSON snippet, one of the categories has an empty string as a key, which leads to the mentioned error du