Skip to main content
To homepage To homepage

 

Hi!

A customer I am working for recently did an upgrade to TX Classic 20.10.66.64.

After switching all data sources from ODX to Business Units not all datatypes are set correctly in TimeXtender. Especially the columns containing the datatype “time(7)”. 

When you check the fields in the new datasource the datatype for that field is shown as unknown, while sql recognizes the source as a “time(7)” field. 

We were able to resolve this with the overrule datatype option, but would like to have it investigated to check if this is desirable. 

TimeXtender:

 

 

SSMS:

 

Datasource: Any Source ADO.net

Dataprovider: SQLClient Data Provider (.Net Framework data provider)

​@rbrandsma I have tested with the SQL Server data source in my Business Unit and this correctly identifies the time(7) data type. I am currently checking with the product team if there is anything can be done about the Any Source ADO.net  SQLClient Data Provider (.Net Framework data provider)

 

Hi ​@rbrandsma 

You can convert the data source from any source ado.net to our own SQL without loosing any mappings by synchronizing afterwards. So you can just convert it if you want it to be a time data type.

 

Hi ​@rbrandsma The product team have have informed me that “When using the Any Source ADO.net data source and reading the metadata the SQL Server provider is returning System.TimeSpan as the data type for SQL Time data type. A System.TimeSpan is not guaranteed to fit into a SQL Time data type and therefore it was decided to let it be up to the user to override it.”

Therefore to prevent manual data type overrides please convert to the SQL Server data source, as advised by Thomas above.

Please let us know if you have any issues converting the data source

Thanks for the answer. 

Fortunately we were able to change the datatype in the tables of the staging area. 

Reply


Terms and ConditionsCookie settings