Ingest

TX: 20.10.39ODX: 20.10.37ODX Storage: SQL Server DB on-premDSA/MDW: SQL Server DB on-prem We are successfully able to connect to a DB2 system and synchronize, we can also successfully use the Data Source Explorer to query tables. Every table we try to extract fails with the following error (schema/table/column names obfuscated): Executing table [schema].[table]:failed with error:edo220W.gm: The column [column] does not exist   at edo220W.ai.GetOrdinal(String )   at System.Data.CData.DB2.DB2DataReader.GetOrdinal(String name)   at System.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServerCommon(Int32 columnCount)   at System.Data.SqlClient.SqlBulkCopy.WriteRowSourceToServerAsync(Int32 columnCount, CancellationToken ctoken)   at System.Data.SqlClient.SqlBulkCopy.WriteToServer(IDataReader reader)   at DataStorageEngine.SQL.SQLStorageEngine.TransferWithBulkCopy(SqlCommand destinationCommand, St

Is it possible to connect to an Amazon Timestream database (https://aws.amazon.com/timestream/) with the ODX?

I am trying to get data using REST API Data Source: ODXProvider: CData 2022Authentication: OAuthFormat: JSONOAuth Grant Type: ClientAuthorize OAuth SuccessfulTest Connection getting below error: RSSBus.RSBException.HTTP Protocol error. 400 bad requests    

Dear Support,I'm running into a weird error when I try to load customer data from the customer table of Navision. The error is: The numerical value is too large to fit into a 96 bit decimal.I use a query table to only get the columns I need. In this query table I use a where clause in which I exclude some customernumbers. But now I found out that I also need these numbers in my customer dimension. But when I clear the WHERE clause, the error comes up again.If I execute the same query in SQL Management studio it runs good and I don't see some strange values in one of the columns.Do you have any idea?

Hi I am just testing our V21. I have started with something simple, a 2 column CSV file with an integer key field and a text group code field. There are 18 rows.I can load it into the ODX fine (running on local SQL Server db) and I can preview the contents in the ODX “Select Tables” Pane.I can drag it to a Data Warehouse Data Area and it creates and maps the table fine with appropriate field settings.When I deploy the table in the Data Area that works fine.When Executing I get an error on the transfer which does not tell me what is happening. The error I get returned is as follows: Transfer table failedDetails:Transfer table failedModule: timeXtenderSystem.Exception   at TimeXtender.DataManager.StepTransferExecute.DoDataWarehouse(IStepSetup stepSetup, List`1 mergeODXTransferInfromation, VariableResolveObject dynamicResolveObject)   at TimeXtender.DataManager.StepTransferExecute.DoAbstractSte

Hi community,I have a client attempting to load a postgres database into ODX Server (TX version 20.10.x). The table contains a field with dates that are invalid for SQL but valid in Postgres, for example 20011/01/01. Upon transfer, the task completes with errors that it is unable to parse datetime value. All datetime fields have been converted to VARCHAR(MAX) using Override Datatypes and this is confirmed by looking in the ODX Storage in SQL Server Management studio. Since the error still presents itself, it seems likely that the error is coming a step earlier, during the CDATA conversion. Unfortunately, it seems that there is no way to generate RSD/schema files from the CDATA Postgres provider. Normally I would change the datatype there in these situations, since it seems to be going wrong in CDATA somewhere. How can I load this table? Kind regards,Andrew - E-mergo

When I opened the project today ODX showed this error.Another ODX service has the lock to the project. Please run the configuration tool to take over the lock.What could it be the reason?

We have set up a db2 connector in an installation with the new version of Timextender. The connection is ok.When we make a search to select tables, nothing turns up. Both the schema and table filters are set to <All>.It seems that Timextender searches the schema [sys_tables], but the server uses the schema [systables]. Without the underscore.The schema [sys_tables] exists on the server, but contains no data. I created a Query Table (Select * from [sys_tables]). It was executed succesfully in a Transfer task, but only returned empty columns.Is it possible to change the script so that the query uses the schema systables?I couldn't find anything about it in CData's online manualThe Timextender version is 6143.1, and the CData DB2 version is 22.0.8389.9

Hi Community,I'm trying to connect the database from CBS (in both old and new version of TX). The original request URI gives an error response that the query exceeds 10.000 rows at test connection. This is a well-known issue with data from CBS, so I adapted the URI to include a filter. I tested this new query both in Postman and Qlik Sense Desktop and there the filter works and I retrieve aprox. 2.500 rows, from 2020 until 2022. Using this query in TX does not work unfortunately. The error that normally encounters when testing connection does not pop-up, however, the table still retrieves 10.000 rows. Probably just random from all available years (1995 t/m 2022).I am using below request URI:

At one of our customers we have a separate cloud for testing software / infrastructure changes. We are running 20.10.35 and want to evaluate 20.10.40. I would like to be able to upgrade the ODX Cloud repository for only one of the projects/environments instead of upgrading both to 20.10.40 and needing to risk production issues. Is this possble / can this be requested?

Dear Sir,For one of our customers we need to connect with TX to a Datalake (CSI Cloud).Our customer is able to connect with PowerBI to their Datalake with a JDBC → ODBC Bridge piece of software from ZappySys JDBC Bridge Driver. This works fine.Now we need to connect with TimeXtender without this third party JDBC Bridge Driver software to save our client some ZappySys license money.So I checked with the CData component in TimeXtender, but it seems their is no JDBC → ODBC Bridge Driver available...Question: Is their a way to do this with the best Data Management Platform in the world ?Hope you can shine a light on this.Thanx in advance. Regards from Amsterdam,ArthurFourpoints TimeXtender Partner

Hi community,  I have to design the following issue, every day, I have a new CVS file in the Azure storage account. These file’s name change with a new day, for exampleFormaExtract.net_new_commission_2023-03-01.csvFormaExtract.net_new_commission_2023-03-02.csvFormaExtract.net_new_commission_2023-03-03.csvHow I could create an automatic process to load a new file to the table in DSA? Now I will do it manually adding every day a new file an process the data.ODX DSA Another requirement is to create a new column SourceMainTable in the DSA table with the file’s name. RegardsIgnacio

I'm trying to setup ODX critical error notification. I've used the same settings as the regular TX notifications, but the test email never arrives. I do notice that in the ODX I do not have the option to enable SSL/TLS, which is needed. I'm using smtp.office365.com.

TX: 6143.1 I have a TimeXtender SQL Data Source version 17.0.0.0 that I am trying to upgrade to 17.0.0.1. When I do Manage Data Sources in the ODX Server from the TimeXtender application it tells me there is an update available. When I apply this it tells me to ‘Edit the datasource’ to update the connection string. There does not seem to be an obvious way to do this. The User Portal also does not seem to have a way to update this.What is the process I should apply?

Hi,I am using the ODX server to get data from the SQL server database.After executing the transfer task, I am getting the below error.Any idea how to solve this?“System.Data.SqlClient.SqlException (0x80131904): The datediff function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try to use datediff with a less precise datepart.System.Data.SqlClient.SqlException (0x80131904): The datediff function resulted in an overflow. The number of dateparts separating two date/time instances is too large. Try to use datediff with a less precise datepart.”

Hi Support,We are using an ADO Data Source connection to load data in the ODX into Azure.From there we map the ODX table to the next layer in TimeXtender.This seemed to work.But now we changed the source table with added and removed columns.We sync and transfer it in the ODX and when we use preview in the ODX we are seeing the new table as expected. But when we map it in TimeXtender again to the next layer, the changes are not added. It instead maps to what is used to be. It mappes fields to columns that no longer exist, and it does not map the new added columns.We tried clearing the files in Azure to start fresh but it still mappes to the older version that no longer exist. Why would it still mapp to the old table that no longer exist in the source and no longer exist in Azure?Why would it not mapp to the new table thats in Azure now?Is there some metadata in TimeXender that first has to be cleaned before changes can be

We are planning to use  Export to Azure Data Lake feature in D365 F&OMy question it’s:How can connect to the Data Lake from TX?Or, we can connect to Synapse Analytics?How can we make the data source setup in TX?

We have a SFTP source on which CSV files are stored and which can be authenticated to with a ‘public key’. When using the CData SFTP-connector in ODX Server, we are able to connect with the following settings: The most important setting here is the SSH Auth mode, where we specify that we are using PublicKey authentication. Since I am not familiar with this type of connector, I would not now how to retrieve the data from the CSV files (the only table we get from the source now is the ‘Root’ table that contains the FileNames that can be found in the folder).I would rather use the CData CSV-connector, but that leaves me with a problem when testing the connection: I cannot specify that I

I’ve three excel files in a SharePoint folder:Budget Forecast Price ListWhat it’s the best option to get the files into a TXA DSA?Can you provide me with detailed instructions? 

I have created a CSV source in Timextender NG ODX.  The data explorer shows the data type correctly for my table.However, when I drag the table to the DSA, all fields appear as bigint type. (by the way, I have setQuote Character to “  and Row Scan Depth to 0). Any help on how to resolve this issue, would be appreciated.

Hi!We have had our installation for a while now but as far as I’m aware the application has the latest updates. As we are becoming more people in the project working at the same time I have installed the client on both a new server and on my own laptop. The problem is that when I try to connect to the ODX service running on one of our “old” servers I keep getting the error as in the attached pictures. Why is this? As you can see the application has the same version on both thte “old” and the “new” server.The correct ports are opened between the servers at least so that should not be an issue but I get the same error when trying to connect from my laptop. Anyone who has an input on this?

I am using the 20.10.36.64 desktop version.I am trying to select a provider to connect the SQL server using ODX.I am not seeing any SQL-specific providers here.Which one should I use?  

Trying to connect to DB2 sql server  with 20.10.6.64 but get an error  (NO error message available) that is not documented. Connection is working in another environment. It is not the CDATA connector but DB2 from data source

For one of our clients I need to connect to a database on Amazon Redshift. The IT Vendor who made the system is telling us to use SSL mode Required ( https://docs.aws.amazon.com/redshift/latest/mgmt/connecting-ssl-support.html#connect-using-ssl ). Using this setting in the ODBC connector from Amazon itself works fine but the CData connector only gives a true false dropdown. I've checked if this perhaps was one of those fields where you can overrule the drop down with manual input but that's not the case for this one. Is there any way to get this working in the CData connector or would our only option for now by create DSN and then use the ADO ODBC option the the ODX to connect with the DSN.

I need to be able to call an API using a reference number from the ERP system ( which is already in the ODX) as part of the URL. It looks like the Dynamic parameters as descibed on the old support site could work. However it is stated that this will only work in the old fashioned business unit. Is there a solution that would work in the ODX or would a Power Automate/Logic App be the only solution.